From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: netboot/UNDI status
Date: Fri, 25 Jan 2008 22:23:45 +0100 [thread overview]
Message-ID: <200801252223.45714.okuji@enbug.org> (raw)
In-Reply-To: <20080125132515.GA5196@thorin>
On Friday 25 January 2008 14:25, Robert Millan wrote:
> On Fri, Jan 25, 2008 at 10:00:17AM +0100, Marco Gerards wrote:
> > "Yoshinori K. Okuji" <okuji@enbug.org> writes:
> > > On Thursday 24 January 2008 13:42, Robert Millan wrote:
> > >> Well, if we can collaborate by sharing the same driver collection
> > >> that's even better, of course. This was done for GRUB Legacy, right?
> > >
> > > Sure. I had a very short conversation with gpxe developers last year,
> > > and we have agreed that we should share work. In GRUB Legacy, we tried
> > > to keep etherboot drivers as intact as possible, and we contributed
> > > back by providing bug fixes. IMO, this should be continued in GRUB 2 as
> > > well.
> >
> > Please correct me if I am wrong, but aren't some files licensed under
> > the GPL, with an additional demand that you shouldn't use it outside
> > etherboot?
>
> Just one driver is known to do that. Check our BTS.
>
> Besides, it might even be illegal to distribute those drivers, even as part
> of etherboot.
Right. Maybe I should contact gpxe developers, if they still have it.
Okuji
prev parent reply other threads:[~2008-01-25 21:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 19:02 netboot/UNDI status Douglas Ward
2008-01-23 11:38 ` Marco Gerards
2008-01-23 11:57 ` Robert Millan
2008-01-23 15:46 ` Douglas Ward
2008-01-23 17:02 ` Bean
2008-01-23 19:01 ` Marco Gerards
2008-01-23 18:59 ` Marco Gerards
2008-01-24 8:49 ` Yoshinori K. Okuji
2008-01-24 12:42 ` Robert Millan
2008-01-24 21:10 ` Yoshinori K. Okuji
2008-01-25 9:00 ` Marco Gerards
2008-01-25 13:25 ` Robert Millan
2008-01-25 21:23 ` Yoshinori K. Okuji [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=200801252223.45714.okuji@enbug.org \
--to=okuji@enbug.org \
--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.