All of lore.kernel.org
 help / color / mirror / Atom feed
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:44:25 +0200	[thread overview]
Message-ID: <20090813204425.GJ22130@thorin> (raw)
In-Reply-To: <20090813082214.GF11691@riva.ucam.org>

On Thu, Aug 13, 2009 at 09:22:14AM +0100, Colin Watson wrote:
> > > 
> > > What do people think about this general approach?
> > 
> > There is already a version hardcoded into the uncompressed part of
> > core.img.  See kern/i386/pc/startup.S.  Unfortunately, there is no
> > policy when the version should be updated.
> > 
> > But I'm fine with a separate file in /boot/grub if we decide that the
> > existing version in core.img cannot be used for that and we cannot keep
> > grub.cfg backward compatible.
> 
> The version in core.img would be fine if there were a way to extract it
> from userspace. It seems rather ugly to me to extract this using dd or
> od directly - also, presumably grub-mkconfig ought to be at least
> somewhat architecture-independent. Does this need a new tool?

This seems overengineered.  I'd rather integrate grub-install with
grub-mkconfig to ensure they're always run together, than have to deal
with a version number that has to be constantly upgraded.

Maintaining an ABI version number is a significant burden in the long
run.  We should think carefully before committing to it.

-- 
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."



  reply	other threads:[~2009-08-13 20:44 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 [this message]
2009-08-13 20:41 ` Robert Millan

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=20090813204425.GJ22130@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.