On Wed, Aug 12, 2009 at 04:25:09PM +0100, Colin Watson wrote: > I'm having persistent problems with grub.cfg and core.img getting out of > sync. The usual pattern is: > > * Some shiny new feature appears in core.img > * We extend grub-mkconfig to use it > * User runs update-grub but not grub-install (historically a perfectly > sane thing to do, and indeed basically standard practice) > * grub either falls over at boot or does something odd > > This just bit me again today, and if it bites me it's going to bite the > users of the packages I upload too.
Generally, we make grub-mkconfig generate code that is backward compatible. Can you give more details on why it wasn't this time? Also, it's probably a good idea to always run grub-install at the same time as update-grub. Latest version of the Debian package includes a debconf template to run grub-install every time the package is upgraded. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
