From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub.cfg and core.img getting out of sync
Date: Thu, 13 Aug 2009 22:41:12 +0200 [thread overview]
Message-ID: <20090813204112.GI22130@thorin> (raw)
In-Reply-To: <20090812152508.GZ11691@riva.ucam.org>
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."
prev parent reply other threads:[~2009-08-13 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 15:25 grub.cfg and core.img getting out of sync Colin Watson
2009-08-13 6:54 ` Pavel Roskin
2009-08-13 8:22 ` Colin Watson
2009-08-13 20:44 ` Robert Millan
2009-08-13 20:41 ` Robert Millan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090813204112.GI22130@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.