Here's a standard working debian menu.lst:
default 0
timeout 5
title Debian GNU/Linux, kernel 2.6.8-1-k7-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.8-1-k7-smp root=/dev/md0 ro
initrd /boot/initrd.img-2.6.8-1-k7-smp
savedefault
boot
Here's a standard working Centos (RHEL 4.0) grub.conf:
default=0
timeout=5
title CentOS (2.6.9-22.0.1.ELsmp)
root (hd0,0)
kernel /boot/vmlinuz-2.6.9-22.0.1.ELsmp ro root=/dev/md0 rhgb quiet
initrd /boot/initrd-2.6.9-22.0.1.ELsmp.img
Which bits in the grub.conf are you alluding to???
On Fri, February 3, 2006 2:50 pm, Volker Kuhlmann wrote:
>> No no , grub.conf is read on the fly on bootup.
>
> You're talking about menu.lst, and you'd be editing menu.lst to change
> kernel boot options or boot targets.
>
> How does grub find out which partition to find menu.lst on?
Sorry, I thought the situation was as describbed. However, it is just
convention. The location of menu.lst/grub.conf is hardcoded into grub,
same as the boot stages.
This can be manually performed using an approximation of the following
command:
grub> install (hd0,0)/boot/grub/stage1 d (hd0) (hd0,0)/boot/grub/stage2 p
(hd0,0)/boot/grub/menu.lst
This will set up a boot environment for the root partition mounted on
/dev/hda1 without a separate boot partition. You can stuff these files
anywhere, but it'll be a challenge to maintain!
Steve.
--
Work like you don't need the money,
Love like your heart has never been broken and
Dance like no one can see you.
