Re: [Cooker] Re: [CHRPM] NAME: kernel VER: 2.2.13 REL: 20mdk
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 LILO, if I recall correctly, but there may >have been other problems too. > >Does Mandrake have the same problem? Not for me since the last successful Panoramix (DrakX) install. The latest lilo.conf just has "vmlinuz" and the install of a new kernel makes all the proper links. I simply re-boot now without changing anything or running lilo and I have my new kernel. Very simple. But, I always keep a complete working kernel just in case the latest fails.
Re: [Cooker] Re: [CHRPM] NAME: kernel VER: 2.2.13 REL: 20mdk
Chmouel Boudjnah wrote: > Humm, and a script who add the entry to /etc/lilo.conf and regenerate > the initrd if needed : [...] I like this. The only problem is LILO is very limited in the number of images it can support, which implies that the kernel upgrade process will break after NN number of upgrades.
Re: [Cooker] Re: [CHRPM] NAME: kernel VER: 2.2.13 REL: 20mdk
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 LILO, if I recall correctly, but there may > > have been other problems too. > > Does Mandrake have the same problem? > > This is what the rpm do : > > if [ -x /sbin/lilo -a -f /etc/lilo.conf ]; then > /sbin/lilo > /dev/null 2>&1 > exit 0 > fi > > but it's assume you have a lilo entry pointing to /boot/vmlinuz. > > I look to make a script who add a entry. That's what I forgot: lilo.conf specifies the kernel version. IMHO rpm needs to update lilo.conf by doing something like if [ -x /sbin/lilo -a -f /etc/lilo.conf ]; then sed -e 's#/boot.*kernel.*mdk#/boot/kernel-2.2.13-20mdk#' \ < lilo.conf > lilo.conf.new if cmp lilo.conf*; then /sbin/lilo fi fi That way lilo isn't run unless it sees an mdk kernel. (note - you don't want to use above script verbatim, because rpm needs to be smart enough to _only_ do s/old-version/new-version/)
Re: [Cooker] Re: [CHRPM] NAME: kernel VER: 2.2.13 REL: 20mdk
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 correctly, but there may > have been other problems too. > > Does Mandrake have the same problem? I don't thing it's been specificly addressed yet. -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
