Ignore:
Timestamp:
07/15/2004 07:33:53 PM (20 years ago)
Author:
Matthew Burgess <matthew@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
715f65f
Parents:
a088964
Message:
  • Fixed various networking inaccuracies

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3941 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter07/network.xml

    ra088964 rc0155c7  
    2828directory should contain subdirectories in the form of
    2929<filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a network
    30 interface name (such as eth0 or eth0:1)</para>
     30interface name (such as eth0)</para>
    3131
    3232<para>If you decide to rename or move this
    … …  
    4646IP=192.168.1.1
    4747GATEWAY=192.168.1.2
    48 NETMASK=24
     48PREFIX=24
    4949BROADCAST=192.168.1.255
    5050EOF</userinput></screen>
    5151
    52 <para>Of course, the values of those variables have to be changed
    53 in every file to match the proper setup. If the ONBOOT variable is set
    54 to <quote>yes</quote>, the network script will bring up the equivalent NIC (Network Interface Card)
    55  during the booting of the system.
    56 If set to anything but <quote>yes</quote>, the equivalent NIC will be ignored by the network script
    57 and not brought up.</para>
     52<para>Of course, the values of those variables have to be changed in every file
     53to match the proper setup. If the ONBOOT variable is set to <quote>yes</quote>,
     54the network script will bring up the equivalent interface during the booting of
     55the system.  If set to anything but <quote>yes</quote>, the equivalent interface
     56will be ignored by the network script and not brought up.</para>
    5857
    59 <para>The SERVICE entry defines the method of obtaining the IP address.
    60 The LFS bootscripts have a modular IP assignment format, and by creating
    61 additional files in <filename class="directory">/etc/sysconfig/network-devices/services</filename>, you can allow
    62 other IP assignment methods.  This would commonly be used if you need DHCP,
    63 which is addressed in the BLFS book.</para>
     58<para>The SERVICE entry defines the method of obtaining the IP address.  The LFS
     59bootscripts have a modular IP assignment format, and by creating additional
     60files in
     61<filename class="directory">/etc/sysconfig/network-devices/services</filename>,
     62you can allow other IP assignment methods.  This would commonly be used if you
     63need DHCP, which is addressed in the BLFS book.</para>
    6464
    6565<para>Of course, GATEWAY should contain the IP of your default gateway, if you
    66 have one. If not, then comment out the variable entirely.</para>
     66have one. If not, then don't include the GATEWAY line in the configuration
     67file.</para>
    6768
    6869</sect2>
    … …  
    7475<para>If you're going to be connected to the Internet then most likely you'll
    7576need some means of DNS name resolution to resolve Internet domain names to IP
    76 addresses. This is best achieved by placing the IP address of your DNS, available from your ISP (Internet Service Provider) or network administrator,
    77 into <filename>/etc/resolv.conf</filename>. Create the file by running the
    78 following:</para>
     77addresses. This is best achieved by placing the IP address of your assigned DNS
     78resolver, available from your ISP (Internet Service Provider) or network
     79administrator, into <filename>/etc/resolv.conf</filename>. Create the file by
     80running the following:</para>
    7981
    8082<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
    … …  
    8789EOF</userinput></screen>
    8890
    89 <para>Of course, replace <replaceable>[IP address of your nameserver]</replaceable> with the IP
    90 address of the DNS most appropriate for your setup. There will often be
    91 more than one entry (requirements demand secondary servers for fallback capability). The IP address may even be a router on your local network.</para>
     91<para>Of course, replace
     92<replaceable>[IP address of your nameserver]</replaceable> with the IP address
     93of the DNS resolver assigned for your use. There will often be more than one
     94entry (requirements demand secondary servers for fallback capability). The IP
     95address may even be a router on your local network.</para>
    9296
    9397</sect2>
Note: See TracChangeset for help on using the changeset viewer.