Re: updating kernel using up2date

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Excerpt of message (sent 17 March 2003) by Aaron Konstam:
> On Mon, Mar 17, 2003 at 11:39:44AM -0500, christian@xxxxxxxxxx wrote:
> > how would you "use" such an older kernel?
> > 
> > Lilo complained because /boot was wiped empty.

> The answer to the first question is to have a clause in lilo.conf for
> every kernel you want to boot. Then run lilo.

Great.  Thanks Aaron; I'll try this.
 
> I do not understand your statement that /boot was wiped empty.

Running 'ls /boot' gives just one file:

   kernel.h

while I (and Lilo!) expect more files, like

   System.map            initrd-2.4.18-14.img  module-info-2.4.18-14
   System.map-2.4.18-14  kernel.h              os2_d.b
   boot.0300             lost+found            vmlinux-2.4.18-14
   boot.b                map                   vmlinuz
   chain.b               message               vmlinuz-2.4.18-14
   config-2.4.18-14      message.ja
   grub                  module-info

> Also you can't boot from the rescue disk. Do you meant you are
> booting from a boot disk you made during or after installation?
> It is the kernel on that disk that you are running if that is what
> you did.

Yes, at the end of the upgrade, the dialog strongly suggested that I
create a boot diskette.  Which I did, and I've been very glad.
Booting off the floppy gives me (a) the kernel I want, (b) RedHat 8.0
works great, and (c) the stuff in /boot reappears.

Maybe upgrading to RedHat 8 simply disabled mounting /boot.

Thanks again

  Christian



-- 
Psyche-list mailing list
Psyche-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/psyche-list

[Index of Archives]     [Fedora General Discussion]     [Red Hat General Discussion]     [Centos]     [Kernel]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux