le mar 27-11-2001 � 13:56, Borsenkow Andrej a �crit : > > > le mar 27-11-2001 � 12:48, Borsenkow Andrej a �crit : > > > > true. I think it's impossible for a script to guess the old kernel > > > real > > > > filenames, > > > > > > readlink(vmlinuz) as long as it follows conventions. If not, break > and > > > create explicit name ... hey, but then it does create explicit name > > > currently ... so, final suggestion - when installing new kernel > check if > > > explicit entry for current kernel exists if not create it as backup. > > > > we can have several ... > > [root@bastard root]# rpm -q kernel > > kernel-2.4.13-6mdk > > kernel-2.4.13-10mdk > > kernel-2.4.13-12mdk > > > > So where is the problem? I speak only about default link vmlinuz -> > vmlinuz-actual-version. > > Ahh, I understand. I do not care about people installing multiple cooker > versions.
so see my point. > I do care about normal people installing security updates. > Currently they are left without backup entry in boot menu. I already > reported it. > > Cooker folks know how to correct it if evil things happen. Average users > do not. So installkernel should (actually, must) be polite and give them > (average users) possibility to revert to old known good if anything with > new kernel goes wrong. yes > O.K.? ok, but ... picture it. I'm a lame new user. I upgrade one time for a first kernel security upgrade. I don't touch anything and just used to boot the new kernel entry ( I don't know where to change this even if it's easy to find ). There's a second kernel security update and maybe a fourth ( mt or linus are very tired ). So we arrive in the casewhere as for cooker users he installs several kernels ... Yes we have to think that people can be very lame ! :( To my mind the simplest solution is to used in the boot loader config file SINCE the beginning ( install ) the true filenames even if the symlinks exists in /boot. Imagine I have 3 kernel : 2.4.8-26mdk installed at install time by DrakX, 2.4.13-6mdk and 2.4.13-12 mdk cooker/security kernels update ). My /boot/grub/menu.lst will look like this : [...] title linux kernel (hd2,0)/vmlinuz hdc=ide-scsi quiet vga=788 initrd (hd2,0)/initrd.img WRONG [...] title linux-2413-6mdk kernel (hd2,0)/vmlinuz-2.4.13-6mdk hdc=ide-scsi root=/dev/sdb6 apm=realmode_power_off initrd (hd2,0)/initrd-2.4.13-6mdk.img title 2413-12 kernel (hd2,0)/vmlinuz-2.4.13-12mdk devfs=mount hdc=ide-scsi quiet vga=788 apm=realmode_power_off root=/dev/sdb6 initrd (hd2,0)/initrd-2.4.13-12mdk.img it should be ( I suppose I have the original install kernel names here 2.4.8-26mdk ) : title linux kernel (hd2,0)/vmlinuz-2.4.8-26mdk hdc=ide-scsi quiet vga=788 initrd (hd2,0)/initrd.-24.8-26mdkimg GOOD title linux-2413-6mdk kernel (hd2,0)/vmlinuz-2.4.13-6mdk hdc=ide-scsi root=/dev/sdb6 apm=realmode_power_off initrd (hd2,0)/initrd-2.4.13-6mdk.img title 2413-12 kernel (hd2,0)/vmlinuz-2.4.13-12mdk devfs=mount hdc=ide-scsi quiet vga=788 apm=realmode_power_off root=/dev/sdb6 initrd (hd2,0)/initrd-2.4.13-12mdk.img and in /boot we have : vmlinuz-2.4.8-26mdk vmlinuz-2.4.13-6mdk vmlinuz-2.4.13-12mdk vmlinuz -> vmlinuz-2.4.13-12mdk the same for initrd. In this case there's nothing to change in %postin kernel script. Just the %inst need to be modified to use the real name. -- http://perso.wanadoo.fr/linux_wizard/index.html - Je suis assis sous un chene qui est un peu plie
