On Fri, February 3, 2006 2:08 pm, Volker Kuhlmann wrote:
>> [EMAIL PROTECTED] ~]$ ls -l /etc/grub.conf
>> lrwxrwxrwx 1 root root 22 Aug 6 2004 /etc/grub.conf ->
>> ../boot/grub/grub.conf
>
>> In all cases, it does need to be under /boot.
>
> Are you sure? I don't think it needs to be anywhere, as grub.conf is
> only read by grub when you install the grub boot loader. Some put it to
> /etc, some to /boot, who cares. At boot time, grub only needs to be able
> to locate the second stage, which contains the kernel and menu.lst. The
> location of the second stage is hardcoded into the boot loader when
> running grub --batch <grub.conf, I expect.
No.
--batch
turn on batch mode for non-interactive use
>From the doc,
"The first action GRUB takes after it is loaded is to look for it's
configuration file. If one is not found, then it drops into the
command-line interface (and stays there). If one is found, the full menu
interface is activated containing whatever entries were found in the file
(the command-line is still available via a command from the menu
interface)."
If it doesn't find the file on the mounted partition, then it won't
automagically boot. (I know - I've corrupted it (: )
Because of this, all file paths in grub.conf/menu.lst are relative to the
/boot partition: ie if you don't have a /boot partition, you'll have
entries like
title Test Debian Linux
root (hd0,0)
kernel /boot/vmlinuz-2.6.15.2 ro root=/dev/hda2
initrd /boot/initrd-2.6.15.2.img
But if you *do* have a separate boot partition, then...
title Test Debian Linux
root (hd0,0)
kernel /vmlinuz-2.6.15.2 ro root=/dev/hda2
initrd /initrd-2.6.15.2.img
(I just wrote them from memory, so there may be errors in them )
>
> With lilo you need to reinstall the boot loader each time your kernel
> image file changes[1]. With grub, you only need to do this when it moves
> to a different filesystem[2].
All the necessary info to boot from lilo is held locally. That's wy you
don't need to run any programs to install a new kernel with grub, just add
an entry in the config file.
>
> Volker
>
> [1] The list of actual disk blocks taken up by the kernel image file is
> hardcoded (ok around 2 corners) into the boot loader.
>
> [2] Grub can locate the file on the filesystem by itself. You need to
> tell it which filesystem though.
And mount it?
>
> --
> Volker Kuhlmann is possibly list0570 with the domain in
> header
> http://volker.dnsalias.net/ Please do not CC list postings to me.
>
