From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: etherboot-developers@lists.sourceforge.net
Subject: Re: gPXE and GRUB2
Date: Sat, 14 Nov 2009 16:44:32 +0100 [thread overview]
Message-ID: <20091114154432.GC7084@thorin> (raw)
In-Reply-To: <4AFDEB81.7050507@gmail.com>
On Sat, Nov 14, 2009 at 12:28:01AM +0100, Vladimir 'phcoder' Serbinenko wrote:
> 3) Add a secondary target to gPXE to produce series of GRUB modules. Due
> to big differences between build systems this may be problematic and
> result in frequent breakage
From a distributor POV, option 3 is difficult to manage. GRUB doesn't have
a stable ABI and ensuring coherency between two separate packages can be
problematic. I wouldn't recommend this option.
--
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-11-14 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 23:28 gPXE and GRUB2 Vladimir 'phcoder' Serbinenko
2009-11-14 15:44 ` Robert Millan [this message]
[not found] ` <422fdd8a0911140615n5e16d736l7462dfcf968e2f23@mail.gmail.com>
2009-11-14 15:57 ` [Etherboot-developers] " Vladimir 'phcoder' Serbinenko
2009-11-14 17:38 ` Robert Millan
[not found] ` <422fdd8a0911141003j3839662dm30489e08e87da90e@mail.gmail.com>
2009-11-14 18:46 ` Robert Millan
2009-11-19 9:10 ` Arends, R.R.
[not found] ` <4B0517EC.7FDC.0010.0@hro.nl>
[not found] ` <422fdd8a0911190153qa7c58bcle4780880401b1720@mail.gmail.com>
2009-11-19 10:00 ` Arends, R.R.
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=20091114154432.GC7084@thorin \
--to=rmh@aybabtu.com \
--cc=etherboot-developers@lists.sourceforge.net \
--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.