On Mon, 2009-02-02 at 21:25 -0500, Chris Knadle wrote: > On Sunday 01 February 2009, Allen Weiner wrote: > > On my multiboot desktop PC the primary grub, which is "owned" by > > Fedora, is in the MBR of SDA. (I mainly run Fedora). There is a > > secondary grub in the boot sector of my Ubuntu partition, SDB8. > > (I'm running Ubuntu 8.10). If I select Ubuntu on the primary grub > > menu, grub chainloads to the secondary grub. > > Okay, I understand that. > > > I've had this grub configuration since November 2008 and it has > > worked without problem. This past week, Ubuntu updates from kernel > > 2.6.27-7 to 2.6.27-11 were installed on my PC. This is the first > > Ubuntu kernel update with my chainloading grub configuration. My > > Ubuntu /boot/grub/menu.lst did not get automatically updated to > > include 2.6.27-11. I expected that it would get updated and I have > > no idea why it didn't. > > I had a look at the the /boot/grub/menu.lst you sent, which I assume > is the one in /dev/sda8 where the secondary grub you're chainloading > to for Ubuntu resides. Please note that the "# kopt=root=" line > LOOKS like a comment, except that update-grub USES that line as a > SETTING for where the root partition for the OS is. Ubuntu these > days usually uses "# kopt=root=UUID=<long_UUID_ID>" in order to find > the listed filesystem UUID inside of the initrd image init script, > rather than using a hard-coded partition. If the "# kopt=root=" line > is incorrect, then when the GRUB menu is updated by 'update-grub' > when a new kernel is installed, the command-line options passed to > all the kernels in the boot menu list will be set incorrectly. > > Also, there's a file that needs to exist, /etc/kernel-img.conf which > tells the system what to do when a new kernel .deb is installed. > This is where 'update-grub' is specified to run as either the > postinst_hook, postrm_hook, or both. Here's the default > kernel-img.conf file from Ubuntu Jaunty Jackelope: > > # Kernel image management overrides > # See kernel-img.conf(5) for details > do_symlinks = yes > relative_links = yes > do_bootloader = no > do_bootfloppy = no > do_initrd = yes > link_in_boot = no > postinst_hook = update-grub > postrm_hook = update-grub >
Thanks very much for your reply. I think you nailed it! I have a /etc/kernel-img.conf but it does not include the postinst_hook and postrm_hook. I suspect the reason for this is that I installed my secondary grub into the boot sector of my Ubuntu partition by using a Knoppix CD. (I followed a procedure from the book "Knoppix Hacks"). I'd like to make a correction to my original post. I stated that the Ubuntu kernel update was from 2.6.27-7 to 2.6.27-11. After that post I discovered that there was also a 2.6.27-9 kernel that had been installed via update. _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Feb 4 - Ruby on Rails Mar 4 - TBD Apr 1 - TBD
