In fact, this error had been pointed out by splotz90 in
http://wiki.linuxfromscratch.org/lfs/ticket/2698
and
http://wiki.linuxfromscratch.org/lfs/ticket/2699
but unfortunately all two tickets have been closed.
so i decide to start a new thread.
the page below explains what the search command does:
http://grub.enbug.org/search
There are some typos. For example , "HD" should be "no",
"bg" should be "by", "te" should be "to".
So the search command has nothing to do with initrd image.
For instance, this menuentry in my grub.cfg file:
*menuentry "GNU/Linux, with Linux 2.6.34" --class gnu-linux --class gnu
--class os {
insmod ext2
set root='(hd0,15)'
search --no-floppy --fs-uuid --set
ab00fa9d-6571-4c2a-bca2-f8d219a1ab91
echo Loading Linux 2.6.34 ...
linux /boot/vmlinuz-2.6.34 root=/dev/sda7
}*
At first, the set command set "root" variable to partition (hd0,15)
which does not exist in my system. then grub uses search command to find
which partition has uuid "ab00fa9d-6571-4c2a-bca2-f8d219a1ab91", then
grub found that (hd0,7) has uuid "ab00fa9d-6571-4c2a-bca2-f8d219a1ab91",
so grub set "root" variable to (hd0,7)
now*
linux /boot/vmlinuz-2.6.34 root=/dev/sda7
*is equivalent to*
linux (hd0,7)/boot/vmlinuz-2.6.34 root=/dev/sda7
*system boots successful.*
*so the sentence* "*The /search/ lines are not meaningful for LFS
systems as that command needs an initrd image for processing" is wrong.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
