greg.newton at optusnet.com.au
Mon Jan 24 21:41:09 PST 2005
My apologies, my mind went 1-based when it should have been 0-based.
The grub manual says it searches /boot/grub and /grub for the
grub images. I don't think you can have your menu.lst in (hd0,0)/
but you should be able to have it in (hd0,0)/boot/grub or in
(hd0,0)/grub, unless you specify otherwise in the setup command
HTH (more than last time)
>--- Original Message ---
>From: "Bluesheet" <bluesheet at doramail.com>
>To: lfs-support at linuxfromscratch.org
>Date: 1/25/05 1:50:19 PM
Dear all , thanks for all to discuess my question. ^_^.
>Reference to Greg.
>if hda1 = /boot and hda2 = /
>but in GRUB, hda1 => hd0,0 and hda2 => hd0,1
>grub>root (hd0,1) # tells grub where to find menu.lst <<=it
will tell grub
the menu.lst will be on partition hda2, but the menu.lst is existed
why. it set to (hd0,1) not (hd0,0)??
grub>kernel (hd0,1)/boot/vmlinuz-2.6.7 root=/dev/hda2 <<= it
will tell grub
to find the kernel in hda2/boot/vmlinuz-xxx and the / is in hda2
but i try it. if...
grub>root (hd0,0) #set the menu.lst location
>grub>setup(hd0) # install it into MBR
>grub>kernel /vmlinuz-xxx ro root=/dev/hda2 # tell GRUB the kernel
>hd0,0(hda1) and the / is in hda2
>then the system can startup properly, but the GRUB can't show
the menu. This
>method I reference a GRUB howto. Thanks.
>>I beg to differ.
>>When /boot and / are in separate partitions, your kernel should
>>have the root argument pointing to the "/" partition, and GRUB
>>should have ITS root argument pointing at the "/boot" partition.
>>Keeping it simple, with two partitions on hda. hda1 = /boot,
>>hda2 = /
>>root (hd0,1) # tells grub where to find menu.lst
>>setup (hd0) # installs grub in MBR of hda
>>Note: doing 'setup' without the 'root' command will not achieve
>>the desired result.
>>title xxxxxx 2.6.7 - hda2
>>kernel (hd0,1)/boot/vmlinuz-2.6.7 root=/dev/hda2
>>and of course in fstab
>Unsubscribe: See the above information pag
More information about the lfs-support