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