grub errors and read-only

Donal Farrell vmlinuz101 at
Fri Aug 5 08:55:09 PDT 2005

yupe, i tried to put sarge on /dev/hda2 which didn't exist at all when
i just had suse and lfs. the /dev/hda2 was the primary partition i
made for debian, and thought you can't mount this on / as suse is on /
on /dev/hda1 (am I totally wrong here?). therefore i chose to make a
/boot on /dev/hda2 which i take to mean that sarge will be mounted on
/boot on /dev/hda2. the debian installer kicks out but only after it
partitions the drive. As per instructions in lfs, the lfs grub
bootloader takes precedence over all otheres, by which i mean it loads
itself or suse or whatever. this menu.lst is

title LFS 6.0
root (hd0,0)
kernel /boot/lfskernel- root=/dev/hda1

why is root on /dev/hda1 when lfs is on /dev/hda4?? 
also, from the same menu.lst, suse is

title SuSE Linux 9.1 Professional
    kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 vga=0x31a splash=silent
desktop resume=/dev/hda5 showopts
    initrd (hd0,1)/boot/initrd

this shows a swap on /dev/hda5, which i deleted and put on /dev/hda3
and shows root=/dev/hda2 :(

the actual menu.lst in suse's grub is 

title SuSE Linux Professional 9.1
    kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 vga=0x31a splash=silent
desktop resume=/dev/hda3 showopts
    initrd (hd0,0)/boot/initrd

here i can see the valid swap

by the way, i only have suse, FC4 and lfs, along with the swap now. By
right, I should have shared /home and by right i should have extended

do i HAVE to overwrite suse now and reinstall it or is there indeed
some magic i can perform here? what must i do in /etc/fstab in fedora
to allow entries for suse and lfs? by the way, i also have xen, bochs
and vmware on suse and their kernel images are also in /boot

Many thanks,


More information about the blfs-support mailing list