From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: netboot related projects
Date: Sun, 30 Apr 2006 01:10:51 +0200 [thread overview]
Message-ID: <200604300110.52157.okuji@enbug.org> (raw)
In-Reply-To: <4453E2A1.4000706@imperial.ac.uk>
On Sunday 30 April 2006 00:03, vincent guffens wrote:
> true, but this is why the idea here is to use the drivers without
> modification or at least with as few modifications as possible.
GRUB Legacy did the same, and failed in keeping the code up-to-date. Because:
- you still have to check all updated files every time.
- you depend on the internal API of Etherboot, so you need to develop glue
code again and again.
I would say that this is not desirable, unless Etherboot developers make the
internal API quite stable, and this is unlikely to happen. They have good
reasons to change it from time to time.
IMHO, the only feasible approach is to depend on only the external API of
Etherboot. This is the UNDI interface. Fortunately, if we use UNDI, we can
provide the same feature for PXE ROMs as well, and UNDI is a standard. So I
prefer to develop a network device based on UNDI rather than copying
Etherboot drivers.
Okuji
next prev parent reply other threads:[~2006-04-29 23:10 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
2006-04-29 22:03 ` vincent guffens
2006-04-29 23:10 ` Yoshinori K. Okuji [this message]
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=200604300110.52157.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.