On 2013-05-08 01:57 (GMT+0200) Carlos E. R. composed:
On Monday, 2013-05-06 at 23:40 -0400, Felix Miata wrote:
For the OP's changes, grub2-mkconfig triggered by the new kernel and/or zypper dup must have saved him the grief of failed attempting to reboot without having first made the required bootloader config changes without which Grub Legacy would have failed him.
Remember that grub stores code in the starting sectors of the partition, outside of the filesystem.,,,
These data sectors, if they were on the old /boot partition, are probably still there. If the partition is formatted or removed, it could be a problem.
That's what http://lists.opensuse.org/opensuse/2013-05/msg00182.html 28 hours ago was about. What I wrote that Carlos replied to here was speculation about how the OP was able to be running a kernel which was installed after the /boot files "relocation" (copy actually) and at least one subsequent reboot. Without some manual intervention with Grub configuration, I can't imagine any reason other than Grub2 automagic to explain the OP's failure to fail (aka running the new kernel). -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org