On Tue, 03 Jul 2012 14:56:01 +0200
maury63ts
GRUB2 after ugrade of kernel at a new release, not refresh the list at the start-up, why?
A comment on this. On one of my machines, I have both 12.1 installed (using legacy grub), and 12.2 installed using grub2. The grub2 menu includes entries for booting either system. (1) After a kernel update for 12.1, the grub2 menu still lists the old kernel for 12.1, so the grub2 menu entries cannot boot 12.1 (2) After a kernel update for 12.2, the grub2 menu was updated for the correct kernel for 12.2. That would probably have also updated the 12.1 entries, except that 12.1 is in an encrypted LVM and not fully visible to 12.2, so the entries were instead dropped. I am not sure, but I suspect that Maury is talking about (1) rather than about (2). In that case, I don't see it as a bug. Personally, I have added an entry to the grub2 menu that chainloads legacy grub to boot 12.1. So the problem in (1) is not a problem for me. Personal opinion: I think grub2 commits the sin of doing too much. It would have been better to chainload to other installs, instead of directly booting the kernels. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org