source: basicnet/djb/daemontools/daemontools-exp.xml@ 8e6d39f1

10.0 10.1 11.0 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 ken/refactor-virt krejzi/svn lazarus nosym perl-modules qt5new systemd-11177 systemd-13485 trunk v1_0 v5_0 v5_0-pre1 v5_1 v5_1-pre1 xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since 8e6d39f1 was 8e6d39f1, checked in by Larry Lawrence <larry@…>, 19 years ago

fix daemontools patch, daemontools-man-config

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

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