Author: matthew
Date: 2008-02-07 12:35:36 -0700 (Thu, 07 Feb 2008)
New Revision: 8469

Modified:
   trunk/BOOK/chapter01/changelog.xml
   trunk/BOOK/chapter02/creatingfilesystem.xml
   trunk/BOOK/general.ent
   trunk/BOOK/packages.ent
Log:
Upgrade to E2fsprogs-1.40.5. Fixes #2138.

Modified: trunk/BOOK/chapter01/changelog.xml
===================================================================
--- trunk/BOOK/chapter01/changelog.xml  2008-01-30 19:10:15 UTC (rev 8468)
+++ trunk/BOOK/chapter01/changelog.xml  2008-02-07 19:35:36 UTC (rev 8469)
@@ -37,6 +37,16 @@
 -->
 
     <listitem>
+      <para>2008-02-07</para>
+      <itemizedlist>
+        <listitem>
+          <para>[matthew] - Upgraded to E2fsprogs-1.40.5. Fixes
+          <ulink url="&lfs-ticket-root;2138">#2138</ulink>.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
+    <listitem>
       <para>2008-01-29</para>
       <itemizedlist>
         <listitem>

Modified: trunk/BOOK/chapter02/creatingfilesystem.xml
===================================================================
--- trunk/BOOK/chapter02/creatingfilesystem.xml 2008-01-30 19:10:15 UTC (rev 
8468)
+++ trunk/BOOK/chapter02/creatingfilesystem.xml 2008-02-07 19:35:36 UTC (rev 
8469)
@@ -42,13 +42,13 @@
 <screen role="nodump"><userinput>debugfs -R feature 
/dev/<replaceable>&lt;xxx&gt;</replaceable></userinput></screen>
 
     <para>If the output contains features other than
-    <option>has_journal</option>, <option>dir_index</option>,
-    <option>filetype</option>, <option>large_file</option>,
-    <option>resize_inode</option>, <option>sparse_super</option> or
-    <option>needs_recovery</option>, then your host
-    system may have custom enhancements.  In that case, to avoid later 
problems,
-    you should compile the stock E2fsprogs package and use the resulting 
binaries
-    to re-create the filesystem on your LFS partition:</para>
+    <option>has_journal</option>, <option>ext_attr</option>,
+    <option>resize_inode</option>, <option>dir_index</option>,
+    <option>filetype</option>, <option>sparse_super</option>,
+    <option>large_file</option> or <option>needs_recovery</option>, then your
+    host system may have custom enhancements.  In that case, to avoid later
+    problems, you should compile the stock E2fsprogs package and use the
+    resulting binaries to re-create the filesystem on your LFS 
partition:</para>
 
 <screen role="nodump"><userinput>cd /tmp
 tar -xjvf /path/to/sources/e2fsprogs-&e2fsprogs-version;.tar.bz2

Modified: trunk/BOOK/general.ent
===================================================================
--- trunk/BOOK/general.ent      2008-01-30 19:10:15 UTC (rev 8468)
+++ trunk/BOOK/general.ent      2008-02-07 19:35:36 UTC (rev 8469)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-<!ENTITY version "SVN-20080129">
-<!ENTITY releasedate "January 29, 2007">
+<!ENTITY version "SVN-20080207">
+<!ENTITY releasedate "February 7, 2008">
 <!ENTITY milestone "7.0">
 <!ENTITY generic-version "development"> <!-- Use "development", "testing", or 
"x.y[-pre{x}]" -->
 

Modified: trunk/BOOK/packages.ent
===================================================================
--- trunk/BOOK/packages.ent     2008-01-30 19:10:15 UTC (rev 8468)
+++ trunk/BOOK/packages.ent     2008-02-07 19:35:36 UTC (rev 8469)
@@ -111,10 +111,10 @@
 <!-- NOTE: When updating e2fsprogs, remember to check the list
      of acceptable features that can be shown by debugfs in
      chapter02/creatingfilesystem.xml -->
-<!ENTITY e2fsprogs-version "1.40.4">
+<!ENTITY e2fsprogs-version "1.40.5">
 <!ENTITY e2fsprogs-size "3,954 KB">
 <!ENTITY e2fsprogs-url 
"&sourceforge;e2fsprogs/e2fsprogs-&e2fsprogs-version;.tar.gz">
-<!ENTITY e2fsprogs-md5 "124d744bdf9d443591eb8193c085944b">
+<!ENTITY e2fsprogs-md5 "69e55eaf543acfab8e2eb8ba2883d8cd">
 <!ENTITY e2fsprogs-home "http://e2fsprogs.sourceforge.net/";>
 <!ENTITY e2fsprogs-ch5-du "31.2 MB">
 <!ENTITY e2fsprogs-ch5-sbu "0.4 SBU">

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to