Re: kernel panic

[Cloudmaster <sauer@cloudmaster.com>]

On Tue, 16 May 2000, Jordan Bettis wrote:
> On Tue, 16 May 2000, Charles Menzes wrote:
> > i am still really in the need of figuring out a way to boot, and get a
> > workable kernel into my /boot. using what was suggested before, typing
[...]

> If you have another Linux box sitting around, you could drop your hard
> drive into it's slave IDE slot (plug?) and then edit your /boot and
> /etc/lilo.conf from there, perhaps replacing the troubled vmlinuz with
> it's (the working box's) vmlinuz. Then drop it back into the box that
> isn't working and see what happens there. Of course, you won't be able to
> run lilo on it but if you name the new kernel the same thing you named the
> last kernel, lilo shouldn't have any trouble finding it. 
[...]

Couldn't you just "chroot /mnt lilo", or use "lilo -r /mnt" (they do the
same thing, I think)?

--Danny, asking rhetorical questions...


--
To unsubscribe, send email to majordomo@luci.org with
"unsubscribe luci-discuss" in the body.