Re: [Cooker] Re: [CHRPM] NAME: kernel VER: 2.2.13 REL: 20mdk

1999-10-20 Thread Terrapin
On Wed, 20 Oct 1999 01:33:36 -0400, Jeff Garzik [EMAIL PROTECTED] wrote: One thing I was wondering -- RedHat has always had the problem where a kernel upgrade via RPM was not complete, ie. I could not do rpm -U kernel*.rpm reboot and get a new kernel. Basically it did not re-run

Re[2]: [Cooker] Re: [CHRPM] NAME: kernel VER: 2.2.13 REL: 20mdk

1999-10-20 Thread tracer
Thursday, October 21, 1999 Hello Terrapin, Wednesday, Wednesday, October 20, 1999, you wrote: Terrapin On Wed, 20 Oct 1999 01:33:36 -0400, Jeff Garzik Terrapin [EMAIL PROTECTED] wrote: One thing I was wondering -- RedHat has always had the problem where a kernel upgrade via RPM was not

[Cooker] Re: [CHRPM] NAME: kernel VER: 2.2.13 REL: 20mdk

1999-10-19 Thread Jeff Garzik
One thing I was wondering -- RedHat has always had the problem where a kernel upgrade via RPM was not complete, ie. I could not do rpm -U kernel*.rpm reboot and get a new kernel. Basically it did not re-run LILO, if I recall correctly, but there may have been other problems

Re: [Cooker] Re: [CHRPM] NAME: kernel VER: 2.2.13 REL: 20mdk

1999-10-19 Thread Axalon Bloodstone
On Wed, 20 Oct 1999, Jeff Garzik wrote: One thing I was wondering -- RedHat has always had the problem where a kernel upgrade via RPM was not complete, ie. I could not do rpm -U kernel*.rpm reboot and get a new kernel. Basically it did not re-run LILO, if I recall

Re: [Cooker] Re: [CHRPM] NAME: kernel VER: 2.2.13 REL: 20mdk

1999-10-19 Thread Jeff Garzik
Chmouel Boudjnah wrote: Jeff Garzik [EMAIL PROTECTED] writes: One thing I was wondering -- RedHat has always had the problem where a kernel upgrade via RPM was not complete, ie. I could not do rpm -U kernel*.rpm reboot and get a new kernel. Basically it did not re-run