Update to util-linix-ng-2.18

 Exapand and reformat notes concerning grub.cfg

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9330 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 40 insertions, 8 deletions

diff --git a/chapter08/grub.xml b/chapter08/grub.xml
index 08ba1c4e5..cf0b4fbe4 100644
--- a/chapter08/grub.xml
+++ b/chapter08/grub.xml
@@ -109,7 +109,7 @@ set timeout=5
 ### END /etc/grub.d/00_header ###
 
 ### BEGIN /etc/grub.d/10_linux ###
-menuentry "GNU/Linux, Linux 2.6.30.2-lfs65" {
+menuentry "GNU/Linux, Linux 2.6.34-lfs" {
         insmod ext2
         set root=(hd0,2)
         search --no-floppy --fs-uuid --set 915852a7-859e-45a6-9ff0-d3ebfdb5cea2
@@ -147,13 +147,45 @@ menuentry "GNU/Linux, Linux 2.6.28-11-server (recovery mode)" {
 ### END /etc/grub.d/40_custom ###
 </computeroutput></screen>
 
-  <para>Note that even though there is a warning not to edit the file, you can
-  do so as long as you do not re-run <command>grub-mkconfig</command>.  The
-  <emphasis>search</emphasis> lines are not meaningful for LFS systems as that
-  command needs an initrd image for processing. If installing on a separate
-  partition the linux and initrd lines will not have the /boot on the file
-  names.  In this example the kernel files for a Ubuntu installation are
-  also found in <filename class="directory">/boot</filename>.</para>
+  <note>
+  <itemizedlist>
+      <listitem><para>Even though there is a warning not to edit the file, you
+      can do so as long as you do not re-run
+      <command>grub-mkconfig</command>.</para></listitem>
+
+      <listitem><para>The <emphasis>search</emphasis> lines are generally not
+      useful for LFS systems as that command only sets an internal GRUB
+      variable used to find the kernel image.  The <emphasis>set root</emphasis> 
+      command provides the same capability without the overhead of 
+      searching.</para></listitem>
+  
+      <listitem><para>The <emphasis>set root</emphasis> and 
+      <emphasis>insmod ext2</emphasis> commands can be moved out of the  
+      <emphasis>menuentry</emphasis> sections to apply to all sections of the file.
+      This leads to a simple section like:</para></listitem>
+
+      </itemizedlist>
+<screen><computeroutput>menuentry "Linux &linux-version;-lfs-&version;" {
+linux   /boot/vmlinux-&linux-version;-lfs-&version; root=/dev/sda2 ro
+}
+</computeroutput></screen>
+  
+  <itemizedlist>
+
+      <listitem><para>Passing a UUID to the kernel requires an initial ram disk
+      (initrd) not built by LFS.</para></listitem>
+  
+      <listitem><para>If the <filename>/boot</filename> partition is installed
+      on a separate partition, the linux and initrd lines should not have the
+      string <emphasis>/boot</emphasis> prefixed to the file
+      names.</para></listitem> 
+  
+      <listitem><para>In this example the kernel files for a Ubuntu
+      installation are also found in <filename
+      class="directory">/boot</filename>.</para></listitem>
+
+   </itemizedlist>
+   </note>
 
   </sect2>