- Timestamp:
- 09/21/2003 02:07:57 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, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- c4f1401
- Parents:
- 36f9a23
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
connect/dhcp/dhcpcd/dhcpcd-exp.xml
r36f9a23 rb2a9f85 2 2 <title>Command explanations</title> 3 3 4 <para>< userinput>patch -Np1 -i ../dhcpcd-&dhcpcd-version;.patch5 </ userinput> : Dhcpcd unpatched puts all configuration and temporary6 files in <filename>/etc/dhcpc</filename>. This becomes very annoying 7 when dhcpcd tells you it's running and it's not. You look in 8 <filename>/var/run</filename> for the pid file, but it's not there, the 9 pid file that needs deleting is in <filename>/etc/dhcpc</filename>. This 10 patch brings this program into FHS compliance, but more importantly, 11 puts files where you expect them to be.</para>4 <para><command>patch -Np1 -i ../dhcpcd-&dhcpcd-version;.patch 5 </command> : <application>Dhcpcd</application> unpatched puts all configuration 6 and temporary files in <filename>/etc/dhcpc</filename>. This becomes very 7 annoying when <application>dhcpcd</application> tells you it's running and it's 8 not. You look in <filename>/var/run</filename> for the pid file, but it's not 9 there, the pid file that needs deleting is in <filename>/etc/dhcpc</filename>. 10 This patch brings this program into <acronym>FHS</acronym> compliance, but more 11 importantly, puts files where you expect them to be.</para> 12 12 13 <para><userinput>--prefix=""</userinput> : There may be a good reason for 14 abandoning the normal BLFS convention of using --prefix=/usr here. If 15 you are installing DHCP, it is likely that it is required during the 16 boot process and <filename>/usr</filename> may be network mounted in which case, dhcpcd 17 wouldn't be available due to being on the network! Therefore, depending 18 on your situation, you may want it to be installed in <filename>/sbin</filename> or <filename>/usr/sbin</filename>. This command installs to <filename>/sbin</filename>.</para> 13 <para><command>--prefix=""</command> : There may be a good reason for 14 abandoning the normal <acronym>BLFS</acronym> convention of using --prefix=/usr 15 here. If you are installing <acronym>DHCP</acronym>, it is likely that it is 16 required during the boot process and <filename>/usr</filename> may be network 17 mounted in which case, <command>dhcpcd</command> wouldn't be available due to 18 being on the network! Therefore, depending on your situation, you may want it 19 to be installed in <filename>/sbin</filename> or <filename>/usr/sbin 20 </filename>. This command installs to <filename>/sbin</filename>.</para> 19 21 20 <para>< userinput>--sysconfdir=/var/lib</userinput> : This command install22 <para><command>--sysconfdir=/var/lib</command> : This command install 21 23 configuration files in the <filename>/var/lib</filename> 22 24 directory.</para> 23 25 24 <para>< userinput>--mandir=/usr/share/man</userinput> : This command26 <para><command>--mandir=/usr/share/man</command> : This command 25 27 install the man pages to the <filename>/usr/share/man</filename> 26 28 directory.</para>
Note:
See TracChangeset
for help on using the changeset viewer.