Ignore:
Timestamp:
09/21/2003 03:11:22 AM (21 years ago)
Author:
Larry Lawrence <larry@…>
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:
b2a9f85
Parents:
110ec35a
Message:

update intro to ppp

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • connect/dhcp/bootscripts.xml

    r110ec35a r36f9a23  
    11<sect1 id="dhcpclient" xreflabel="Configuring the LFS bootscripts to support DHCP clients">
    22<?dbhtml filename="configdhcp.html" dir="connect"?>
    3 <title>Configuring the LFS bootscripts to support DHCP clients</title>
     3<title>Configuring the <acronym>LFS</acronym> bootscripts to support <acronym>DHCP</acronym> clients</title>
    44
    55<sect2><title>Config files</title>
     
    1313
    1414<para>Note that on this and the following pages, we
    15 use <userinput>eth0</userinput> as the example interface.
     15use <emphasis role="strong">eth0</emphasis> as the example interface.
    1616If 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>
     17replace <emphasis role="strong">eth0</emphasis> with the interface you wish to
     18use.</para>
    1819
    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
     25alterations to those interfaces which need to support
     26<acronym>DHCP</acronym>.  All of the instructions on this page are applicable
     27no matter which <acronym>DHCP</acronym> client you intend to use.</para>
    2528
    2629<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> and
    28 <envar>GATEWAY_IF</envar> variables
     30use <acronym>DHCP</acronym>, the first step is to remove the <envar>GATEWAY
     31</envar> and <envar>GATEWAY_IF</envar> variables
    2932from <filename>/etc/sysconfig/network</filename>.  This will only need to be
    3033done once.</para>
    3134
    32 <para><screen><userinput>cd /etc/sysconfig &amp;&amp;
     35<screen><userinput><command>cd /etc/sysconfig &amp;&amp;
    3336cp network network.bak &amp;&amp;
    34 sed "s/GATEWAY/# GATEWAY/" network.bak > network</userinput></screen></para>
     37sed "s/GATEWAY/# GATEWAY/" network.bak > network</command></userinput></screen>
    3538
    3639<para>You then need to create scripts which will override the default
    37 network scripts and provide DHCP support.  These two scripts are generic and
    38 so for use with both DHCP clients.  First, the
    39 <filename>ifup-eth0</filename> script:</para>
     40network scripts and provide <acronym>DHCP</acronym> support.  These two scripts
     41are generic and so for use with both <acronym>DHCP</acronym> clients.  First,
     42the <filename>ifup-eth0</filename> script:</para>
    4043
    41 <para><screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifup-eth0 &lt;&lt; "EOF" </userinput>
     44<screen><userinput><command>cat &gt; /etc/sysconfig/network-devices/ifup-eth0 &lt;&lt; "EOF" </command>
    4245#!/bin/sh
    4346
     
    4952modprobe eth0
    5053loadproc $DHCP_PROG $DHCP_START
    51 <userinput>EOF</userinput></screen></para>
     54<command>EOF</command></userinput></screen>
    5255
    5356<para>Then the <filename>ifdown-eth0</filename> script:</para>
    5457
    55 <para><screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifdown-eth0 &lt;&lt; "EOF" </userinput>
     58<screen><userinput><command>cat &gt; /etc/sysconfig/network-devices/ifdown-eth0 &lt;&lt; "EOF" </command>
    5659#!/bin/sh
    5760
     
    6366$DHCP_PROG $DHCP_STOP
    6467evaluate_retval
    65 <userinput>EOF</userinput></screen></para>
     68<command>EOF</command></userinput></screen>
    6669
    6770<para>Finally, we need to make these scripts executable:</para>
    6871
    69 <para><screen><userinput>chmod 755 /etc/sysconfig/network-devices/ifup-eth0 &amp;&amp;
    70 chmod 755 /etc/sysconfig/network-devices/ifdown-eth0</userinput></screen></para>
     72<screen><userinput><command>chmod 755 /etc/sysconfig/network-devices/ifup-eth0 &amp;&amp;
     73chmod 755 /etc/sysconfig/network-devices/ifdown-eth0</command></userinput></screen>
    7174
    7275</sect2>
Note: See TracChangeset for help on using the changeset viewer.