Changeset 36f9a23 for connect/dhcp/bootscripts.xml
- Timestamp:
- 09/21/2003 03:11:22 AM (21 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 12.2, 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, gimp3, 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/for-12.3, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/spidermonkey128, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- b2a9f85
- Parents:
- 110ec35a
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
connect/dhcp/bootscripts.xml
r110ec35a r36f9a23 1 1 <sect1 id="dhcpclient" xreflabel="Configuring the LFS bootscripts to support DHCP clients"> 2 2 <?dbhtml filename="configdhcp.html" dir="connect"?> 3 <title>Configuring the LFS bootscripts to support DHCPclients</title>3 <title>Configuring the <acronym>LFS</acronym> bootscripts to support <acronym>DHCP</acronym> clients</title> 4 4 5 5 <sect2><title>Config files</title> … … 13 13 14 14 <para>Note that on this and the following pages, we 15 use < userinput>eth0</userinput> as the example interface.15 use <emphasis role="strong">eth0</emphasis> as the example interface. 16 16 If you want to configure a different (or more than one) interface, simply 17 replace <userinput>eth0</userinput> with the interface you wish to use.</para> 17 replace <emphasis role="strong">eth0</emphasis> with the interface you wish to 18 use.</para> 18 19 19 <para>These instructions will convert the configuration files from LFS 20 (a static configuration) to a configuration using the DHCP protocol. 21 Note that static and DHCP-based interfaces can co-exist on a LFS system. To 22 do this, you should only make the alterations to those interfaces which 23 need to support DHCP. All of the instructions on this page are applicable 24 no matter which DHCP client you intend to use.</para> 20 <para>These instructions will convert the configuration files from 21 <acronym>LFS</acronym> (a static configuration) to a configuration using the 22 <acronym>DHCP</acronym> protocol. Note that static and 23 <acronym>DHCP</acronym>-based interfaces can co-exist on a 24 <acronym>LFS</acronym> system. To do this, you should only make the 25 alterations to those interfaces which need to support 26 <acronym>DHCP</acronym>. All of the instructions on this page are applicable 27 no matter which <acronym>DHCP</acronym> client you intend to use.</para> 25 28 26 29 <para>If the interface you intend to use as your default gateway is going to 27 use DHCP, the first step is to remove the <envar>GATEWAY</envar> and28 < envar>GATEWAY_IF</envar> variables30 use <acronym>DHCP</acronym>, the first step is to remove the <envar>GATEWAY 31 </envar> and <envar>GATEWAY_IF</envar> variables 29 32 from <filename>/etc/sysconfig/network</filename>. This will only need to be 30 33 done once.</para> 31 34 32 < para><screen><userinput>cd /etc/sysconfig &&35 <screen><userinput><command>cd /etc/sysconfig && 33 36 cp network network.bak && 34 sed "s/GATEWAY/# GATEWAY/" network.bak > network</ userinput></screen></para>37 sed "s/GATEWAY/# GATEWAY/" network.bak > network</command></userinput></screen> 35 38 36 39 <para>You then need to create scripts which will override the default 37 network scripts and provide DHCP support. These two scripts are generic and38 so for use with both DHCP clients. First, the 39 <filename>ifup-eth0</filename> script:</para>40 network scripts and provide <acronym>DHCP</acronym> support. These two scripts 41 are generic and so for use with both <acronym>DHCP</acronym> clients. First, 42 the <filename>ifup-eth0</filename> script:</para> 40 43 41 < para><screen><userinput>cat > /etc/sysconfig/network-devices/ifup-eth0 << "EOF" </userinput>44 <screen><userinput><command>cat > /etc/sysconfig/network-devices/ifup-eth0 << "EOF" </command> 42 45 #!/bin/sh 43 46 … … 49 52 modprobe eth0 50 53 loadproc $DHCP_PROG $DHCP_START 51 < userinput>EOF</userinput></screen></para>54 <command>EOF</command></userinput></screen> 52 55 53 56 <para>Then the <filename>ifdown-eth0</filename> script:</para> 54 57 55 < para><screen><userinput>cat > /etc/sysconfig/network-devices/ifdown-eth0 << "EOF" </userinput>58 <screen><userinput><command>cat > /etc/sysconfig/network-devices/ifdown-eth0 << "EOF" </command> 56 59 #!/bin/sh 57 60 … … 63 66 $DHCP_PROG $DHCP_STOP 64 67 evaluate_retval 65 < userinput>EOF</userinput></screen></para>68 <command>EOF</command></userinput></screen> 66 69 67 70 <para>Finally, we need to make these scripts executable:</para> 68 71 69 < para><screen><userinput>chmod 755 /etc/sysconfig/network-devices/ifup-eth0 &&70 chmod 755 /etc/sysconfig/network-devices/ifdown-eth0</ userinput></screen></para>72 <screen><userinput><command>chmod 755 /etc/sysconfig/network-devices/ifup-eth0 && 73 chmod 755 /etc/sysconfig/network-devices/ifdown-eth0</command></userinput></screen> 71 74 72 75 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.