diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index 316f896ea..4a115437a 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -88,6 +88,9 @@ First a summary, then a detailed log. +June 16th, 2005 [matthew]: Another round of typo and markup +fixes in chapter 7, as reported by Randy McMurchy. + June 16th, 2005 [matthew]: Typo and markup fixes in chapter 7, as reported by Randy McMurchy. diff --git a/chapter07/bootscripts.xml b/chapter07/bootscripts.xml index 995673409..186e29730 100644 --- a/chapter07/bootscripts.xml +++ b/chapter07/bootscripts.xml @@ -225,7 +225,7 @@ daemons udev -Sets up udev and create the devices nodes in Sets up udev and create the device nodes in /dev udev diff --git a/chapter07/hosts.xml b/chapter07/hosts.xml index b2a77c0c0..30644cd34 100644 --- a/chapter07/hosts.xml +++ b/chapter07/hosts.xml @@ -17,13 +17,13 @@ network /etc/hosts -If a network card is to be configured, decide on the IP-address, +If a network card is to be configured, decide on the IP address, FQDN, and possible aliases for use in the /etc/hosts file. The syntax is: <IP address> myhost.example.org aliases -Unless the computer is to be visible to the Internet (e.g., +Unless the computer is to be visible to the Internet (i.e., there is a registered domain and a valid block of assigned IP addresses—most users do not have this), make sure that the IP address is in the private network IP address range. Valid ranges @@ -31,8 +31,8 @@ are: Class Networks A 10.0.0.0 - B 172.16.0.0 through 172.31.0.0 - C 192.168.0.0 through 192.168.255.0 + B 172.16.0.0 through 172.31.0.255 + C 192.168.0.0 through 192.168.255.255 A valid IP address could be 192.168.1.1. A valid FQDN for this IP could be www.linuxfromscratch.org (not recommended because this is diff --git a/chapter07/udev.xml b/chapter07/udev.xml index ff50e7161..88e5a805b 100644 --- a/chapter07/udev.xml +++ b/chapter07/udev.xml @@ -165,7 +165,7 @@ and make this device available by creating the device node(s) for it. Problems with Creating Devices There are a few known problems when it comes to automatically creating -devices nodes: +device nodes: 1) A kernel driver may not export its data to sysfs.