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