Changeset c8010baf for basicnet/djb/daemontools/daemontools-exp.xml
- Timestamp:
- 03/02/2003 03:40:15 PM (21 years ago)
- Branches:
- 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
- Children:
- 8d1f2a55
- Parents:
- a5c73e0
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
basicnet/djb/daemontools/daemontools-exp.xml
ra5c73e0 rc8010baf 4 4 <para>The first thing to understand in installing any package written 5 5 by Daniel J. Bernstein, and 6 this includes Qmail, djbdns and ucspi-tcp in addition to daemontools, is6 this includes qmail, djbdns and ucspi-tcp in addition to daemontools, is 7 7 that he is willing to completely disregard standards if his idea of the 8 8 correct thing to do differs from an particular standard. Professor … … 22 22 compiles the source and puts the binaries in a command directory.</para> 23 23 24 <para>Since we are installing the binaries in /usr/sbin rather than creating 25 a non-standard /command directory, several paths have to be changed:</para> 24 26 <para><screen><userinput>sed 's|command|usr/sbin|' boot.inittab > boot.inittab~</userinput> 25 27 <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> 28 <para>In boot.inittab, /command/svscanboot is changed to /usr/sbin/svscanboot.</para> 30 29 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 the35 /etc/service directory for daemons to run instead of the default36 /service directory.</para>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 > svscanboot~ &&</userinput></screen></para> 33 <para>Here various paths are adjusted in the svscanboot script. In our setup svscan 34 will check the /etc/service directory instead of the /service directory for 35 daemons to run.</para> 37 36 38 37 <para><userinput>cp * /usr/sbin: </userinput>We must manually copy the … … 42 41 <userinput>mv -f /etc/inittab~ /etc/inittab</userinput></screen></para> 43 42 44 <para>These commands append a line to /etc/inittab so that init will launch 45 the svscan program.</para> 43 <para>These commands append a line to /etc/inittab so that init will launch 44 the svscanboot script.</para> 45 46 <para><userinput>mkdir /etc/service: </userinput>This command creates 47 the daemontools control directory, which - even if empty - needs to exist for 48 daemontools to run properly.</para> 46 49 47 50 <para><userinput>telinit Q: </userinput>This command tells the init 48 51 process to re-read its configuration file (inittab) and act upon any 49 changes that have been made. </para>52 changes that have been made. The svscanboot script is started.</para> 50 53 51 <para><userinput>mkdir /etc/service: </userinput>This command creates52 the daemontools control directory, which needs to exist, even if empty53 for daemontools to run properly.</para>54 54 55 55 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.