From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub configuration file format change?
Date: Thu, 13 Aug 2009 23:03:21 +0200 [thread overview]
Message-ID: <20090813210321.GR22130@thorin> (raw)
In-Reply-To: <alpine.GSO.2.00.0908131342120.135434@oretfbsg.Jrfg.Fha.PBZ>
On Thu, Aug 13, 2009 at 01:45:17PM -0700, Seth Goldberg wrote:
> Hi,
>
> I know this isn't on the 1.97 roadmap, but I was wondering about the
> status of changing the grub.cfg format. I'm currently trying to plan
> GRUB2 work for Solaris and I'd like to minimize as much code change as I
> can.
We tend to change it very often. I can't garantee there won't be any minor
change before 1.97.
Is this an issue for you? Colin said he was concerned about core.img and
grub.cfg getting out of sync (see the other sub-thread). Does this problem
also affect you?
--
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."
next prev parent reply other threads:[~2009-08-13 21:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 16:10 RFC: 1.97 roadmap Robert Millan
2009-08-10 17:10 ` Vladimir 'phcoder' Serbinenko
2009-08-12 0:43 ` Robert Millan
2009-08-12 8:41 ` Colin Watson
2009-08-12 8:47 ` Colin Watson
2009-08-12 12:26 ` Yves Blusseau
2009-08-13 20:21 ` Robert Millan
2009-08-10 18:20 ` Michal Suchanek
2009-08-10 19:51 ` Vladimir 'phcoder' Serbinenko
2009-08-12 11:56 ` Michal Suchanek
2009-08-12 8:35 ` Colin Watson
2009-08-13 20:31 ` Robert Millan
2009-08-13 20:45 ` grub configuration file format change? Seth Goldberg
2009-08-13 21:03 ` Robert Millan [this message]
2009-08-13 21:12 ` Seth Goldberg
2009-08-17 12:55 ` 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=20090813210321.GR22130@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.