Re: GRUB problem
On Monday 30 June 2003 14:40, Kevin McKinley wrote:
> On Sun, 29 Jun 2003 14:44:46 +1200
>
> cr <cr@orcon.net.nz> wrote:
> > Well, in my system, /vmlinuz is a symlink thus:
> > lrwxrwxrwx 1 root root 26 Jun 12 08:25 vmlinuz ->
> > boot/vmlinuz-2.2.20-idepci
> >
> > and /boot/vmlinuz is:
> > -rw-r--r-- 1 root root 665509 Jun 21 23:05
> > vmlinuz-2.2.20-idepci
> >
> >
> > As I read it, my menu.lst which is as follows:
> >
> > title Debian GNU/Linux, kernel 2.2.20-idepci
> > root (hd0,0)
> > kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro
> > savedefault
> >
> > first sets root to (hd0,0) (i.e. /dev/hda1 or /boot)
> > then tries to load vmlinuz-2.2.20-idepci , passing it the parameters
> > of "root=/dev/hda1"
>
> That's not the case.
>
> You can refer to your kernel either by the symlink name of "/vmlinuz" or by
> its actual name which is "/boot/vmlinuz-2.2.20-idepci". You're trying to
> mix the two together, and it won't work.
>
> Kevin
Errrm, *I* didn't produce that line
kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro
- grub-install did.
In fact, if I read GRUB terminology aright, it's looking for
(hd0,0)/vmlinuz-2.2.20-idepci.
Or, as Linux sees it, /dev/hda/vmlinuz-2.2.20-idepci
aka /boot/vmlinuz-2.2.20-idepci.
And it's there, and also in
/boot/boot/vmlinuz-2.2.20-idepci
(because I copied it there just to make sure).
cr
Reply to: