source: basicnet/djb/daemontools/daemontools-exp.xml@ 29f033a

10.0 10.1 11.0 11.1 11.2 6.0 6.1 6.2 6.2.0 6.2.0-rc1 6.2.0-rc2 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 krejzi/svn lazarus nosym perl-modules qt5new systemd-11177 systemd-13485 trunk upgradedb v5_0 v5_0-pre1 v5_1 v5_1-pre1 xry111/intltool xry111/soup3 xry111/test-20220226
Last change on this file since 29f033a was 29f033a, checked in by Larry Lawrence <larry@…>, 19 years ago

chapter 21

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1196 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 2.9 KB
Line 
1<sect2>
2<title>Command explanations</title>
3
4<para>The first thing to understand in installing any package written
5by Daniel J. Bernstein, and
6this includes <application>qmail</application>, <application>djbdns
7</application> and <application>ucspi-tcp</application> in addition to
8<application>daemontools</application>, is that he is willing to completely
9disregard standards if his idea of the correct thing to do differs from an
10particular standard. Professor Bernstein is a standards body unto himself when
11it comes to his own software. </para>
12
13<para>It is therefore necessary to make quite a few changes to the
14installation commands for his packages to get them to install in a manner
15that is compliant with the Filesystem Hierarchy Standard
16(<acronym>FHS</acronym>). Most of the following commands are due to this
17difficulty.</para>
18
19<para><command>cd admin/daemontools-0.76</command> : First off, the package is
20unpacked in an <filename>admin</filename> directory. You will find the actual
21packages two directory levels below this.</para>
22
23<para><command>package/compile</command> : This command actually
24compiles the source and prepares the binaries.</para>
25
26<para>Since we are installing the binaries in <filename>/usr/sbin</filename>
27rather than creating a non-standard <filename>/command</filename> directory,
28several paths have to be changed:</para>
29<screen><command>sed 's|command|usr/sbin|' boot.inittab &gt; boot.inittab~
30mv boot.inittab~ boot.inittab</command></screen>
31<para>In <filename>boot.inittab</filename>,
32<filename>/command/svscanboot</filename> is changed to
33<filename>/usr/sbin/svscanboot</filename>.</para>
34
35<screen><command>sed -e 's|/command:/usr/local/bin:/usr/local/sbin:||' \
36 -e 's|command|usr/sbin|' \
37 -e 's|/service|/etc/service|g' svscanboot &gt; svscanboot~ &amp;&amp;</command></screen>
38<para>Here various paths are adjusted in the svscanboot script. In our setup
39svscan will check the <filename>/etc/service</filename> directory instead of
40the <filename>/service</filename> directory for daemons to run.</para>
41
42<para><command>cp * /usr/sbin</command> : We must manually copy the
43binaries to the <filename>/usr/sbin</filename> directory.</para>
44
45<para><screen><command>cat /etc/inittab boot.inittab &gt; /etc/inittab~
46mv -f /etc/inittab~ /etc/inittab</command></screen>
47These commands append a line to <filename>/etc/inittab</filename> so that
48<command>init</command> will launch the <command>svscanboot</command> script.
49</para>
50
51<para><command>mkdir /etc/service</command> : This command creates
52the daemontools control directory, which - even if empty - needs to exist for
53<application>daemontools</application> to run properly.</para>
54
55<para><command>telinit Q</command> : This command tells the <command>init
56</command> process to re-read its configuration file
57(<filename>inittab</filename>) and act upon any changes that have been made.
58The <command>svscanboot</command> script is started.</para>
59
60
61</sect2>
62
Note: See TracBrowser for help on using the repository browser.