Author: jhuntwork
Date: 2007-08-08 12:51:02 -0600 (Wed, 08 Aug 2007)
New Revision: 8303
Modified:
branches/jh/BOOK/chapter01/changelog.xml
branches/jh/BOOK/chapter06/bash.xml
branches/jh/BOOK/chapter06/pkgmgt.xml
branches/jh/BOOK/chapter07/network.xml
Log:
Merge r8294-r8297, r8299 and r8302 from trunk
Modified: branches/jh/BOOK/chapter01/changelog.xml
===================================================================
--- branches/jh/BOOK/chapter01/changelog.xml 2007-08-08 18:48:50 UTC (rev
8302)
+++ branches/jh/BOOK/chapter01/changelog.xml 2007-08-08 18:51:02 UTC (rev
8303)
@@ -70,7 +70,27 @@
<listitem>
<para>[jhuntwork] - Since we're using HJL Binutils, add m4, bison
and flex
back to chatper 5.</para>
+ </listitem>
+ <listitem>
+ <para>[dnicholson] - Clarify the description of the Udev persistent
+ network rules file.</para>
</listitem>
+ <listitem>
+ <para>[dnicholson] - Redirected <filename
+ class="devicefile">/dev/tty</filename> to standard input when
+ running the Bash testsuite to prevent errors with terminal
+ permissions.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>2007-08-07</para>
+ <itemizedlist>
+ <listitem>
+ <para>[dnicholson] - Added the
<parameter>--disable-werror</parameter>
+ parameter to Binutils Pass 1.</para>
+ </listitem>
<listitem>
<para>[jhuntwork] - Upgraded to GCC 4.2.1</para>
</listitem>
Modified: branches/jh/BOOK/chapter06/bash.xml
===================================================================
--- branches/jh/BOOK/chapter06/bash.xml 2007-08-08 18:48:50 UTC (rev 8302)
+++ branches/jh/BOOK/chapter06/bash.xml 2007-08-08 18:51:02 UTC (rev 8303)
@@ -81,9 +81,10 @@
chown -Rv nobody ./</userinput></screen>
<para>Now, run the tests as the <systemitem
- class="username">nobody</systemitem> user:</para>
+ class="username">nobody</systemitem> user, ensuring that the standard
+ input device is readable:</para>
-<screen><userinput>su-tools nobody -s /bin/bash -c "make
tests"</userinput></screen>
+<screen><userinput>su-tools nobody -s /bin/bash -c "make tests"
</dev/tty</userinput></screen>
<para>Install the package:</para>
Modified: branches/jh/BOOK/chapter06/pkgmgt.xml
===================================================================
--- branches/jh/BOOK/chapter06/pkgmgt.xml 2007-08-08 18:48:50 UTC (rev
8302)
+++ branches/jh/BOOK/chapter06/pkgmgt.xml 2007-08-08 18:51:02 UTC (rev
8303)
@@ -36,7 +36,7 @@
</itemizedlist>
<para>There are some hints written on the topic of package management. Visit
- the <ulink url="&hints-root;">Hints subproject</ulink> and see if one of them
+ the <ulink url="&hints-index;">Hints Project</ulink> and see if one of them
fits your need.</para>
<sect2>
@@ -221,7 +221,7 @@
<title>User Based Management</title>
<para>This scheme, unique to LFS, was devised by Matthias Benkmann, and
is
- available from the <ulink url="&hints-root;">Hints Project</ulink>. In
+ available from the <ulink url="&hints-index;">Hints Project</ulink>. In
this scheme, each package is installed as a separate user into the
standard locations. Files belonging to a package are easily identified by
checking the user ID. The features and shortcomings of this approach are
Modified: branches/jh/BOOK/chapter07/network.xml
===================================================================
--- branches/jh/BOOK/chapter07/network.xml 2007-08-08 18:48:50 UTC (rev
8302)
+++ branches/jh/BOOK/chapter07/network.xml 2007-08-08 18:51:02 UTC (rev
8303)
@@ -46,10 +46,10 @@
<screen><userinput>cat
/etc/udev/rules.d/70-persistent-net.rules</userinput></screen>
- <para>Each NIC takes up two lines in the file. The first line is a
- description of the NIC itself, showing its hardware IDs (e.g. its PCI
- vendor and device IDs, if it's a PCI card), along with its driver in
- parentheses, if the driver can be found. This line is a comment; neither
+ <para>The file begins with a comment block followed by two lines for each
+ NIC. The first line for each NIC is a commented description showing its
+ hardware IDs (e.g. its PC vendor and device IDs, if it's a PCI card),
+ along with its driver in parentheses, if the driver can be found. Neither
the hardware ID nor the driver is used to determine which name to give an
interface. The second line is the Udev rule that matches this NIC and
actually assigns it a name.</para>
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
