Serious problem

[Jon S.]

Lilo can actually do that using lilo -R <new image> (leaving your old
kernel as default) and if it fails, it goes back to the the default
image. This is why I prefer lilo over grub right now, as I don't know of
a grub equivalent. I use this all the time on a dedicated machine that I
only have ssh access to; very helpful for kernel upgrades.

-Jon

> -----Original Message-----
> From: lunar-bounces at lunar-linux.org
[mailto:lunar-bounces at lunar-linux.org]
> On Behalf Of Richard Pyne
> Sent: Thursday, November 20, 2003 12:58
> To: lunar at lunar-linux.org
> Subject: Re: Serious problem
> 
> That's what I ended up doing.
> 
> Now what would really be nice is a way to try a new kernel and
> automagically reboot the old kernel if it fails. Of course, this
> needs to be able to be done remotely with nothing more than an ssh
> connection to the box ;-)
> 
> --Richard
> 
> On Thursday 20 November 2003 09:26 am, Jon S. wrote:
> > I've done that before; I just used the Lunar cd, booted with it and
> > ran lilo that way.
> >
> > -Jon
> >
> > > -----Original Message-----
> > > From: lunar-bounces at lunar-linux.org
> >
> > [mailto:lunar-bounces at lunar-linux.org]
> >
> > > On Behalf Of Richard Pyne
> > > Sent: Thursday, November 20, 2003 10:19
> > > To: lunar at lunar-linux.org
> > > Subject: Serious problem
> > >
> > > Lunar update just hosed my machine. Taking the defaults all the
> > > way with the new kernel version, The update built the new kernel,
> > > deleted the old kernel, made no updates to lilo.conf and did not
> > > run lilo.
> > >
> > > Automatically deleting a kernel image is just plain BAD! It
> > > leaves no path for recovery should the new kernel fail to boot or
> > > if something should happen that lilo is either not updated or not
> > > run.
> > >
> > > --Richard
> > > --
> > > Richard B. Pyne
> > > rpyne at kinfolk.org
> --
> Richard B. Pyne
> rpyne at kinfolk.org