All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Feature request: network devices
Date: Fri, 13 Nov 2009 13:13:41 +0100	[thread overview]
Message-ID: <4AFD4D75.2050400@gmail.com> (raw)
In-Reply-To: <8bb81f540911121502j283b5018pcbaa9805ade4e6ca@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2130 bytes --]

mardok45 wrote:
> Before I give you an answer, let me explain what I plan on doing.  If
> you like it, and if I succeed, then I'll give back the changes I
> made.  If not, then I won't waste everybody's time anymore.
>
> I plan on using Macintosh's "Netboot" (which is just like PXE except
> for a few minor details) to boot Grub2 off a DHCP/TFTP server.  Once
> loaded on the client, Grub2 will fetch the grub.cfg from the TFTP server.
>
> The grub.cfg will contain entries that are the same as booting off the
> local disk; except in this case, it fetches the kernel and initrd via
> TFTP.
>
> Adding TFTP support is all I'm going to do, nothing else.  Also, I
> have no problem using Etherboot's code-base.
>
"nothing else" is often a problem. There are dependencies too. I started
importing gpxe and till now it goes well
> On Wed, Nov 11, 2009 at 5:38 PM, Vladimir 'phcoder' Serbinenko
> <phcoder@gmail.com <mailto:phcoder@gmail.com>> wrote:
>
>     mardok45 wrote:
>     > I am interested in it as a learning project for me.  I only have
>     > access to New World Macintosh's, so I can only get TFTP working for
>     > Open Firmware Mac's.  I imagine that won't be of much use to you.
>     >
>     > Remember, I can't make any promises, but I am very interested in
>     > getting TFTP to work (with Open Firmware) since that will make
>     my job
>     > much, much more centralized and convenient.
>     The best long-term and cross-platform approach is to import gpxe into
>     grub-extras. Are you willing to do it?
>
>     --
>     Regards
>     Vladimir 'phcoder' Serbinenko
>
>
>
>     _______________________________________________
>     Grub-devel mailing list
>     Grub-devel@gnu.org <mailto:Grub-devel@gnu.org>
>     http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>   


-- 
Regards
Vladimir 'phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

      reply	other threads:[~2009-11-13 12:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 17:59 Feature request: network devices mardok45
2009-11-06  7:40 ` Vasily Averin
2009-11-11  0:28   ` mardok45
2009-11-11  4:32     ` Seth Goldberg
2009-11-11  5:02       ` Bean
2009-11-11  7:02         ` Vasily Averin
2009-11-11  7:13           ` Bean
2009-11-11  7:45             ` Vasily Averin
2009-11-12  1:08         ` Seth Goldberg
2009-11-12  5:01           ` Bean
2009-11-12  5:56             ` Seth Goldberg
2009-11-11 22:33       ` mardok45
2009-11-11 22:38         ` Vladimir 'phcoder' Serbinenko
2009-11-12 23:02           ` mardok45
2009-11-13 12:13             ` Vladimir 'phcoder' Serbinenko [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=4AFD4D75.2050400@gmail.com \
    --to=phcoder@gmail.com \
    --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.