| 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 "admin" 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 puts the binaries in a command directory.</para>
|
|---|
| 23 |
|
|---|
| 24 | <para><screen><userinput>sed 's|command|usr/sbin|' boot.inittab > boot.inittab~</userinput>
|
|---|
| 25 | <userinput>mv boot.inittab~ boot.inittab</userinput></screen></para>
|
|---|
| 26 | <para>These two commands are necessary to get the
|
|---|
| 27 | binaries installed in /usr/sbin rather than
|
|---|
| 28 | creating a non-standard /command directory and installing them there.
|
|---|
| 29 | </para>
|
|---|
| 30 |
|
|---|
| 31 | <para><screen><userinput>sed 's|/command:/usr/local/bin:/usr/local/sbin:||' svscanboot > svscanboot~</userinput>
|
|---|
| 32 | <userinput>sed 's|/service|/etc/service|g' svscanboot~ > svscanboot</userinput>
|
|---|
| 33 | <userinput>rm svscanboot~</userinput></screen></para>
|
|---|
| 34 | <para>This changes the svscanboot script so that it checks the
|
|---|
| 35 | /etc/service directory for daemons to run instead of the default
|
|---|
| 36 | /service directory.</para>
|
|---|
| 37 |
|
|---|
| 38 | <para><userinput>cp * /usr/sbin: </userinput>We must manually copy the
|
|---|
| 39 | binaries to the /usr/sbin directory.</para>
|
|---|
| 40 |
|
|---|
| 41 | <para><screen><userinput>cat /etc/inittab boot.inittab > /etc/inittab~</userinput>
|
|---|
| 42 | <userinput>mv -f /etc/inittab~ /etc/inittab</userinput></screen></para>
|
|---|
| 43 |
|
|---|
| 44 | <para>These commands append a line to /etc/inittab so that init will launch
|
|---|
| 45 | the svscan program.</para>
|
|---|
| 46 |
|
|---|
| 47 | <para><userinput>telinit Q: </userinput>This command tells the init
|
|---|
| 48 | process to re-read its configuration file (inittab) and act upon any
|
|---|
| 49 | changes that have been made.</para>
|
|---|
| 50 |
|
|---|
| 51 | <para><userinput>mkdir /etc/service: </userinput>This command creates
|
|---|
| 52 | the daemontools control directory, which needs to exist, even if empty
|
|---|
| 53 | for daemontools to run properly.</para>
|
|---|
| 54 |
|
|---|
| 55 | </sect2>
|
|---|
| 56 |
|
|---|
