From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Tim Verhoeven <tim.verhoeven.be@gmail.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: LVM and LVM2 support in Grub
Date: Fri, 30 May 2008 15:22:26 +0200 [thread overview]
Message-ID: <20080530132226.GB962@thorin> (raw)
In-Reply-To: <alpine.LRH.1.10.0805301316290.27348@horsea.3ti.be>
On Fri, May 30, 2008 at 01:23:16PM +0200, Dag Wieers wrote:
>
> I asked the question because Alasdair mentioned that the current
> implementation doesn't use the existing LVM framework and he would prefer
> that, instead of having the functionality as a whole included in Grub, it
> relies on the LVM infrastructure that is maintained by the LVM developers.
> And as a result would be a much more complete (and
> maintained) implementation than is currently offered.
>
> To me it looks like it could just compile and link against the LVM API.
> That would certainly provide for a much better implementation than the
> current as it would be maintained by the LVM developers directly.
I agree that it potentially can be a great benefit; but it could also be a
problem. Please could you let us know about:
- Does the LVM framework provide a practical means of linking it
into GRUB (not just the user part, also the freestanding code)?
- Is its license compatible with the GPL (version 3)?
- Will it increase the size of our lvm.mod? Size is critical here, because
it's highly desireable that lvm.mod fits in core.img which fits in
the post-mbr region.
Thanks
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
prev parent reply other threads:[~2008-05-30 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 10:52 LVM and LVM2 support in Grub Dag Wieers
2008-05-30 11:06 ` Robert Millan
2008-05-30 11:23 ` Dag Wieers
2008-05-30 13:22 ` 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=20080530132226.GB962@thorin \
--to=rmh@aybabtu.com \
--cc=agk@redhat.com \
--cc=grub-devel@gnu.org \
--cc=tim.verhoeven.be@gmail.com \
/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.