>> IMHO, this can only be considered in if /sbin/installkernel (or whatever
>> replaces it) ensures that on the first kernel update, an entry for the
>> original kernel is retained. Otherwise, automatic kernel update plus
>> unintentional reboot (ie power failure) = unhappy user/administrator (as
>> would happen at present).
last time I asked Chmouel said he had some problems doing it. I do not know
more details
> installkernel is a bit broken anyways (has problems with kernel-mm and
> kernel-benh (see cooker-ppc)), I will see if i can make it a bit more
> robust
good, that is really needed. current behaviour is broken - you get two entries
for new kernel and none for the old.
if you also make it run lilo/grub when updating existing kernel - even better.
Currently when I recompile kernel and reinstall it I have to run lilo
manually ("lilo entry already exists"). Not a big deal for normal users
probably.
