2012/7/5 Neil Rickert
On Tue, 03 Jul 2012 14:56:01 +0200 maury63ts
wrote: 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
Yes.
(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.
Yes.
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.
I agree with you on chainloading is better than directly booting kernel in general, But the problem comes from how to deal with different install scenarios and that's complicated. There's no general rule to know what partition's bootsector is used and we could leverage it in chainloading to desired place. It's a wild open. For example a distribution may install it's loader to extended partition and /boot on logical partiton (/dev/sda5). This is quite common scenario I think. In this case chainloading /dev/sda5 simply fails. Also we cannot predict chainloading that extended partition would lead us to where ... So, directly booting kernel is not perfect but somehow it is predictable by utilities. And manually configure your chainload partitions to satisfy your needs. Don't trust machines, they are always dumb. :) Thanks, Michael
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org