All of lore.kernel.org
 help / color / mirror / Atom feed
From: vincent guffens <v.guffens@imperial.ac.uk>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB2 netboot development
Date: Tue, 09 May 2006 10:23:19 +0100	[thread overview]
Message-ID: <44605F87.4060703@imperial.ac.uk> (raw)
In-Reply-To: <63DA313E79D4B947ABC7AE6DDC9CC309040EA2@srv2003.bladefusion.com>

Rudy Attias wrote:
> 
> Netboot is taking a different direction? I'm curious about that, can you
> give some details?  


yes, grub legacy also used the drivers from Etherboot and it was
reported not be easily manageable. When Etherboot developpers decide to
change something, the glue code written in grub might have to change too
and so grub developper must constantly track these changes. Also, this
messy glue code is not particularly elegant and is not very funny to
program. It does not seem to me that it would happen too often but it
will happen and I don't have the experience that developpers from grub
legacy have.

So now the idea is to have a unique UNDI driver or maybe to find a way
to call into etherboot and come back into grub if the PXE/UNDI is not
supported. For the moment it is not clear for anyone I think how calling
into etherboot would be done.




  reply	other threads:[~2006-05-09  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09  7:25 GRUB2 netboot development Rudy Attias
2006-05-09  9:23 ` vincent guffens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-07 21:44 Guffens, Vincent
2006-05-07 14:24 Rudy Attias
2006-05-04 13:17 Rudy Attias
2006-05-04 13:49 ` vincent guffens

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=44605F87.4060703@imperial.ac.uk \
    --to=v.guffens@imperial.ac.uk \
    --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.