gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 03:39:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

More chapter 7 typo and markup fixes

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@6026 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Matthew Burgess 2005-06-16 20:09:36 +00:00
parent fe3130ace4
commit eb7bcc4791
4 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
chapter01/changelog.xml
View File

@ -88,6 +88,9 @@ First a summary, then a detailed log.</para>
</itemizedlist> </itemizedlist>
</listitem> </listitem>
<listitem><para>June 16th, 2005 [matthew]: Another round of typo and markup
fixes in chapter 7, as reported by Randy McMurchy.</para></listitem>
<listitem><para>June 16th, 2005 [matthew]: Typo and markup fixes in <listitem><para>June 16th, 2005 [matthew]: Typo and markup fixes in
chapter 7, as reported by Randy McMurchy.</para></listitem> chapter 7, as reported by Randy McMurchy.</para></listitem>

2
chapter07/bootscripts.xml
View File

@ -225,7 +225,7 @@ daemons</para>
<varlistentry id="udev-bootscripts"> <varlistentry id="udev-bootscripts">
<term><command>udev</command></term> <term><command>udev</command></term>
<listitem> <listitem>
<para>Sets up udev and create the devices nodes in <filename <para>Sets up udev and create the device nodes in <filename
class="directory">/dev</filename></para> class="directory">/dev</filename></para>
<indexterm zone="ch-scripts-bootscripts udev-bootscripts"><primary sortas="d-udev">udev</primary></indexterm> <indexterm zone="ch-scripts-bootscripts udev-bootscripts"><primary sortas="d-udev">udev</primary></indexterm>
</listitem> </listitem>

8
chapter07/hosts.xml
View File

@ -17,13 +17,13 @@
<primary sortas="d-network">network</primary> <primary sortas="d-network">network</primary>
<secondary>/etc/hosts</secondary></indexterm> <secondary>/etc/hosts</secondary></indexterm>
<para>If a network card is to be configured, decide on the IP-address, <para>If a network card is to be configured, decide on the IP address,
FQDN, and possible aliases for use in the FQDN, and possible aliases for use in the
<filename>/etc/hosts</filename> file. The syntax is:</para> <filename>/etc/hosts</filename> file. The syntax is:</para>
<screen>&lt;IP address&gt; myhost.example.org aliases</screen> <screen>&lt;IP address&gt; myhost.example.org aliases</screen>
<para>Unless the computer is to be visible to the Internet (e.g., <para>Unless the computer is to be visible to the Internet (i.e.,
there is a registered domain and a valid block of assigned IP there is a registered domain and a valid block of assigned IP
addresses&mdash;most users do not have this), make sure that the IP addresses&mdash;most users do not have this), make sure that the IP
address is in the private network IP address range. Valid ranges address is in the private network IP address range. Valid ranges
@ -31,8 +31,8 @@ are:</para>
<screen> Class Networks <screen> Class Networks
A 10.0.0.0 A 10.0.0.0
B 172.16.0.0 through 172.31.0.0 B 172.16.0.0 through 172.31.0.255
C 192.168.0.0 through 192.168.255.0</screen> C 192.168.0.0 through 192.168.255.255</screen>
<para>A valid IP address could be 192.168.1.1. A valid FQDN for this <para>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 IP could be www.linuxfromscratch.org (not recommended because this is

2
chapter07/udev.xml
View File

@ -165,7 +165,7 @@ and make this device available by creating the device node(s) for it.</para>
<title>Problems with Creating Devices</title> <title>Problems with Creating Devices</title>
<para>There are a few known problems when it comes to automatically creating <para>There are a few known problems when it comes to automatically creating
devices nodes:</para> device nodes:</para>
<para>1) A kernel driver may not export its data to <systemitem <para>1) A kernel driver may not export its data to <systemitem
class="filesystem">sysfs</systemitem>.</para> class="filesystem">sysfs</systemitem>.</para>