From c0155c7108d221cb03ff3244d4f34973293b8cb5 Mon Sep 17 00:00:00 2001 From: Matthew Burgess Date: Thu, 15 Jul 2004 19:33:53 +0000 Subject: * Fixed various networking inaccuracies git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3941 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter07/network.xml | 44 ++++++++++++++++++++++++-------------------- 1 file changed, 24 insertions(+), 20 deletions(-) (limited to 'chapter07') diff --git a/chapter07/network.xml b/chapter07/network.xml index 3113aec58..8ccb09318 100644 --- a/chapter07/network.xml +++ b/chapter07/network.xml @@ -27,7 +27,7 @@ run-level directories the files in the /etc/sysconfig/network-devices directory. This directory should contain subdirectories in the form of ifconfig.xyz, where xyz is a network -interface name (such as eth0 or eth0:1) +interface name (such as eth0) If you decide to rename or move this /etc/sysconfig/network-devices directory, @@ -45,25 +45,26 @@ ONBOOT=yes SERVICE=ipv4-static IP=192.168.1.1 GATEWAY=192.168.1.2 -NETMASK=24 +PREFIX=24 BROADCAST=192.168.1.255 EOF -Of course, the values of those variables have to be changed -in every file to match the proper setup. If the ONBOOT variable is set -to yes, the network script will bring up the equivalent NIC (Network Interface Card) - during the booting of the system. -If set to anything but yes, the equivalent NIC will be ignored by the network script -and not brought up. +Of course, the values of those variables have to be changed in every file +to match the proper setup. If the ONBOOT variable is set to yes, +the network script will bring up the equivalent interface during the booting of +the system. If set to anything but yes, the equivalent interface +will be ignored by the network script and not brought up. -The SERVICE entry defines the method of obtaining the IP address. -The LFS bootscripts have a modular IP assignment format, and by creating -additional files in /etc/sysconfig/network-devices/services, you can allow -other IP assignment methods. This would commonly be used if you need DHCP, -which is addressed in the BLFS book. +The SERVICE entry defines the method of obtaining the IP address. The LFS +bootscripts have a modular IP assignment format, and by creating additional +files in +/etc/sysconfig/network-devices/services, +you can allow other IP assignment methods. This would commonly be used if you +need DHCP, which is addressed in the BLFS book. Of course, GATEWAY should contain the IP of your default gateway, if you -have one. If not, then comment out the variable entirely. +have one. If not, then don't include the GATEWAY line in the configuration +file. @@ -73,9 +74,10 @@ have one. If not, then comment out the variable entirely. If you're going to be connected to the Internet then most likely you'll need some means of DNS name resolution to resolve Internet domain names to IP -addresses. This is best achieved by placing the IP address of your DNS, available from your ISP (Internet Service Provider) or network administrator, -into /etc/resolv.conf. Create the file by running the -following: +addresses. This is best achieved by placing the IP address of your assigned DNS +resolver, available from your ISP (Internet Service Provider) or network +administrator, into /etc/resolv.conf. Create the file by +running the following: cat > /etc/resolv.conf << "EOF" # Begin /etc/resolv.conf @@ -86,9 +88,11 @@ nameserver [IP address of your nameserver] # End /etc/resolv.conf EOF -Of course, replace [IP address of your nameserver] with the IP -address of the DNS most appropriate for your setup. There will often be -more than one entry (requirements demand secondary servers for fallback capability). The IP address may even be a router on your local network. +Of course, replace +[IP address of your nameserver] with the IP address +of the DNS resolver assigned for your use. There will often be more than one +entry (requirements demand secondary servers for fallback capability). The IP +address may even be a router on your local network. -- cgit v1.2.3-54-g00ecf