From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: netboot related projects
Date: Sat, 29 Apr 2006 22:54:28 +0200 [thread overview]
Message-ID: <200604292254.29555.okuji@enbug.org> (raw)
In-Reply-To: <878xpoi1ez.fsf@xs4all.nl>
On Saturday 29 April 2006 22:15, Marco Gerards wrote:
> vincent guffens <v.guffens@imperial.ac.uk> writes:
>
> Hi Vincent,
>
> > I just wanted to let you know that I contacted the maintainer of
> > Etherboot to inform him of my current attempt to port the etherboot
> > drivers to grub2.
>
> Is he willing to cooperate with us so it will be easier to share code?
> I think I once sent him an email about it... But I am not sure
> anymore. :-)
Honestly, I don't like to copy Etherboot's drivers to GRUB any longer. I
rather consider how to use the UNDI interface provided by Etherboot. When I
worked on netboot in GRUB Legacy, Etherboot didn't support UNDI, so I had to
copy the drivers. According to him, the current Etherboot supports UNDI, so
it should be feasible to use Etherboot's drivers via UNDI.
I think the difficulty is the case where GRUB is not loaded by Etherboot, for
example, when GRUB boots from a disk directly. In this case, one way would be
to hack Etherboot so that Etherboot can be invoked by GRUB and give the
control back to GRUB.
From the experience of GRUB Legacy, I know how painful to synchronize code
with an external project, so I'd like to investigate this direction.
Okuji
next prev parent reply other threads:[~2006-04-29 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 15:39 netboot related projects vincent guffens
2006-04-29 20:15 ` Marco Gerards
2006-04-29 20:54 ` Yoshinori K. Okuji [this message]
2006-04-29 22:03 ` vincent guffens
2006-04-29 23:10 ` Yoshinori K. Okuji
2006-04-29 21:00 ` grub-emu state of the art Eric Salomé
2006-04-30 0:31 ` Marco Gerards
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=200604292254.29555.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.