Changeset 0d1379a for basicnet/djb/daemontools/daemontools-exp.xml
- Timestamp:
- 04/12/2003 01:58:10 AM (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:
- 8e6d39f1
- Parents:
- 262ffc5d
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
basicnet/djb/daemontools/daemontools-exp.xml
r262ffc5d r0d1379a 16 16 17 17 <para><userinput>cd admin/daemontools-0.76</userinput> : First off, the 18 package is unpacked in an "admin"directory. You will find the actual18 package is unpacked in an <filename>admin</filename> directory. You will find the actual 19 19 packages two directory levels below this.</para> 20 20 … … 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 24 <para>Since we are installing the binaries in 25 <filename>/usr/sbin</filename> rather than creating 25 26 a non-standard /command directory, several paths have to be changed:</para> 26 27 <para><screen><userinput>sed 's|command|usr/sbin|' boot.inittab > boot.inittab~</userinput> 27 28 <userinput>mv boot.inittab~ boot.inittab</userinput></screen></para> 28 <para>In boot.inittab, /command/svscanboot is changed to /usr/sbin/svscanboot.</para> 29 <para>In <filename>boot.inittab</filename>, 30 <filename>/command/svscanboot</filename> is changed to 31 <filename>/usr/sbin/svscanboot</filename>.</para> 29 32 30 33 <para><screen><userinput>sed -e 's|/command:/usr/local/bin:/usr/local/sbin:||' \</userinput> … … 32 35 <userinput> -e 's|/service|/etc/service|g' svscanboot > svscanboot~ &&</userinput></screen></para> 33 36 <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 37 will check the <filename>/etc/service</filename> directory instead of 38 the <filename>/service</filename> directory for 35 39 daemons to run.</para> 36 40 37 41 <para><userinput>cp * /usr/sbin</userinput> : We must manually copy the 38 binaries to the /usr/sbindirectory.</para>42 binaries to the <filename>/usr/sbin</filename> directory.</para> 39 43 40 44 <para><screen><userinput>cat /etc/inittab boot.inittab > /etc/inittab~</userinput> 41 45 <userinput>mv -f /etc/inittab~ /etc/inittab</userinput></screen> 42 These commands append a line to /etc/inittabso that init will launch46 These commands append a line to <filename>/etc/inittab</filename> so that init will launch 43 47 the svscanboot script.</para> 44 48
Note:
See TracChangeset
for help on using the changeset viewer.