Re: kernel panic---operator panic too

[Gary Turner <kk5st@swbell.net>]

On Thu, 07 Feb 2002 14:47:14 -0500, Thomas R. Shemanske wrote:

>I think your initrd line is misplaced.  Since some kernels do not need 
>the line, you probably want it with each lilo entry
>
>For example from http://rute.sourceforge.net/node34.html, we see a lilo 
>entry of the form:
>
>
>boot=/dev/sda
>prompt
>timeout = 50
>compact
>vga = extended
>linear
>image = /boot/vmlinuz-2.2.17
>         initrd = /boot/initrd-2.2.17
>         label = linux
>         root = /dev/sda1
>         read-only
>
>
>
>
>so I would change your lilo entry to from
>
> > image=/vmlinuz
> > 	label=Linux
> > 	read-only
> > #	restricted
> > #	alias=1
>
>to
>
>image=/vmlinuz
>         label=Linux
>	initrd = /initrd.img
>         root=/dev/hda3
>         read-only
>
>in which each entry specifies the root (so you can eliminate the append 
>statement), and if needed the initrd entry.  THen you can get rid of the 
>initrd lines at the bottom of your file.
>
>Then of course after changing the file, don't forget to rerun lilo
>
>
>Luck
 ^^^^ Don't need it if I get good advice :-)
>TRS

Thank you, Thomas.  I knew it had to be something simple.  I can boot
now.  I'm not going to test it (leave well enough alone), but the initrd
change seems logical from a standpoint of assigning the global var after
the section that uses it.  The install specifically said to add the
initrd line.  I am not versed enough yet to have known where.  Of course
I should have known to at least put a global up top even if it's wrong.

gt
Yes I fear I am living beyond my mental means--Nash