From: Marty Connor <mdc@etherboot.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel <qemu-devel@nongnu.org>,
Gianni Tedesco <gianni.tedesco@citrix.com>,
"gpxe-devel@etherboot.org" <gpxe-devel@etherboot.org>
Subject: Re: [gPXE-devel] [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs
Date: Mon, 02 Aug 2010 16:08:01 -0400 [thread overview]
Message-ID: <4C5725A1.8070402@etherboot.org> (raw)
In-Reply-To: <AANLkTim68=EysWMM3GKEQX1mFzG=nF7poX5YN0nVDf-T@mail.gmail.com>
On 8/2/10 2:14 PM, Stefan Hajnoczi wrote:
> On Mon, Aug 2, 2010 at 5:43 PM, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> Not that it is a big issue, just... weird, and annoying --
>> in Debian for example we (re)build boot ROMs during
>> package build instead of using the ones supplied in
>> the source tarball, and currently gpxe isn't packages
>> in debian, but etherboot behaves somewhat erratically
>> (but works in the end), so I wondered what the issue is.
>
> The issue holding back gPXE from Debian is licensing clarification
> AFAIK. There is nothing there that can't be tackled but the process
> has stalled unfortunately. It would be great to have gPXE in Debian.
>
> Stefan
We definitely have not forgotten about Debian licensing issues,
and in a few weeks after Google Summer of Code is over we'll go
through http://support.etherboot.org/ and deal with licensing
as well as some other issues we haven't gotten to yet.
Thanks for reminding us about this.
/ Marty /
prev parent reply other threads:[~2010-08-02 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 9:44 [Qemu-devel] Netboot happens twice (first fail) when using etherboot ROMs Michael Tokarev
2010-08-01 20:27 ` Stefan Hajnoczi
2010-08-02 16:23 ` Gianni Tedesco
2010-08-02 16:43 ` Michael Tokarev
2010-08-02 18:14 ` Stefan Hajnoczi
2010-08-02 20:08 ` Marty Connor [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=4C5725A1.8070402@etherboot.org \
--to=mdc@etherboot.org \
--cc=gianni.tedesco@citrix.com \
--cc=gpxe-devel@etherboot.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).