source: basicnet/djb/daemontools/daemontools-exp.xml@ c8010baf

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 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 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts krejzi/svn lazarus lxqt nosym perl-modules plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition systemd-11177 systemd-13485 trunk upgradedb v1_0 v5_0 v5_0-pre1 v5_1 v5_1-pre1 xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since c8010baf was c8010baf, checked in by Larry Lawrence <larry@…>, 21 years ago

daemontools inst corrections

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

  • Property mode set to 100644
File size: 2.6 KB
RevLine 
[f45b1953]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
[c8010baf]6this includes qmail, djbdns and ucspi-tcp in addition to daemontools, is
[f45b1953]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 "admin" 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 puts the binaries in a command directory.</para>
23
[c8010baf]24<para>Since we are installing the binaries in /usr/sbin rather than creating
25a non-standard /command directory, several paths have to be changed:</para>
[f45b1953]26<para><screen><userinput>sed 's|command|usr/sbin|' boot.inittab &gt; boot.inittab~</userinput>
27<userinput>mv boot.inittab~ boot.inittab</userinput></screen></para>
[c8010baf]28<para>In boot.inittab, /command/svscanboot is changed to /usr/sbin/svscanboot.</para>
29
30<para><screen><userinput>sed -e 's|/command:/usr/local/bin:/usr/local/sbin:||' \</userinput>
31<userinput> -e 's|command|usr/sbin|' \</userinput>
32<userinput> -e 's|/service|/etc/service|g' svscanboot &gt; svscanboot~ &amp;&amp;</userinput></screen></para>
33<para>Here various paths are adjusted in the svscanboot script. In our setup svscan
34will check the /etc/service directory instead of the /service directory for
35daemons to run.</para>
[f45b1953]36
37<para><userinput>cp * /usr/sbin: </userinput>We must manually copy the
38binaries to the /usr/sbin directory.</para>
39
40<para><screen><userinput>cat /etc/inittab boot.inittab &gt; /etc/inittab~</userinput>
41<userinput>mv -f /etc/inittab~ /etc/inittab</userinput></screen></para>
42
[c8010baf]43<para>These commands append a line to /etc/inittab so that init will launch
44the svscanboot script.</para>
45
46<para><userinput>mkdir /etc/service: </userinput>This command creates
47the daemontools control directory, which - even if empty - needs to exist for
48daemontools to run properly.</para>
[f45b1953]49
50<para><userinput>telinit Q: </userinput>This command tells the init
51process to re-read its configuration file (inittab) and act upon any
[c8010baf]52changes that have been made. The svscanboot script is started.</para>
[f45b1953]53
54
55</sect2>
56
Note: See TracBrowser for help on using the repository browser.