It's looking good.
I downloaded ftp://alpha.gnu.org/gnu/grub/grub-1.97~beta2.tar.gz on a 64-bit
version of LFS-6.5.
I used
./configure --prefix=/usr --sysconfdir=/etc --disable-largefile \
--disable-grub-emu --disable-grub-emu-usb --disable-grub-fstest
make
sudo make install
The disabled modules are for emulation and testing.
The install creates files in /usr/bin, /usr/sbin/ /usr/lib/grub,
/usr/install/grub, /etc/grub.d, and /usr/share/grub.
The files can be loaded into the boot directory with:
grub-install --grub-setup=/bin/true /dev/sda
The --grub-setup=/bin/true prevents changing the MBR but otherwise loads files
into /boot/grub. The main executable is core.img, but there are several other
.img files. There are also 125 .mod files that are modules that can be loaded
at boot time and a few other misc files.
After the files are loaded, the configuration file has to be created. TO do
that, I ran:
grub-mkconfig -o /boot/grub/grub.cfg
This did not do a great job. It found the Ubuntu kernels (vmlinuz-*), but I
had
to modify /etc/grub.d/10_linux to tell it that /boot/linux* was a valid kernel
too -- mine is named linux-2.6.30.2-lfs65.
The configuration file, /boot/grub/grub.cfg looks like:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=10
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "GNU/Linux, Linux 2.6.30.2-lfs65" {
insmod ext2
set root=(hd0,1)
#search --no-floppy --fs-uuid --set
2ae9c39c-c1ee-4006-80af-5a3d41f1255c
linux /linux-2.6.30.2-lfs65 root=/dev/sda5 ro
}
menuentry "GNU/Linux, Linux 2.6.30.2-lfs65 (recovery mode)" {
insmod ext2
set root=(hd0,1)
#search --no-floppy --fs-uuid --set
2ae9c39c-c1ee-4006-80af-5a3d41f1255c
linux /linux-2.6.30.2-lfs65 root=/dev/sda5 ro single
}
menuentry "GNU/Linux, Linux 2.6.28-11-server" {
insmod ext2
set root=(hd0,1)
#search --no-floppy --fs-uuid --set
915852a7-859e-45a6-9ff0-d3ebfdb5cea2
linux /vmlinuz-2.6.28-11-server
root=UUID=2ae9c39c-c1ee-4006-80af-5a3d41f1255c ro
initrd /initrd.img-2.6.28-11-server
}
menuentry "GNU/Linux, Linux 2.6.28-11-server (recovery mode)" {
insmod ext2
set root=(hd0,1)
#search --no-floppy --fs-uuid --set
915852a7-859e-45a6-9ff0-d3ebfdb5cea2
linux /vmlinuz-2.6.28-11-server
root=UUID=2ae9c39c-c1ee-4006-80af-5a3d41f1255c ro single
initrd /initrd.img-2.6.28-11-server
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
I commented out the search lines because the uuid values were wrong. I see now
that I need to add a root= value for the Ubuntu lines.
Note that in grub2, the partition count starts from 1, not like grub1 that
starts from 0.
----------
In any case, I can use grub1 to enter into grub2:
root (hd0,0)
kernel /grub/core.img
boot
I do have my /boot partition separate as /dev/sda1.
And I then get into the new version. And explore from there. A simple boot is
to just select the proper line and then the enter key.
I haven't done it yet, but finishing the install would just require 'grub-setup'
and it will install boot.img (512 bytes) into the MBR and it would be complete.
----------
I don't know when the next release will be, but beta1 was on Aug 30 and beta2
on
Sep 4, so there has been considerable recent progress. Adding grub2 to the
book
will take care of several long standing issues.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
