All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Patch for export IP addresses from PXE into grub2 enviroment variables
Date: Thu, 15 Oct 2009 10:05:40 +0200	[thread overview]
Message-ID: <1255593940.3243.6.camel@fz.local> (raw)
In-Reply-To: <alpine.GSO.2.00.0910150050380.10234@oretfbsg.Jrfg.Fha.PBZ>

Am Donnerstag, den 15.10.2009, 00:51 -0700 schrieb Seth Goldberg:
> 
> Quoting Felix Zielcke, who wrote the following on Thu, 15 Oct 2009:
> 
> > Am Mittwoch, den 14.10.2009, 23:53 -0700 schrieb Seth Goldberg:
> >> Hi,
> >>
> >>    That's actually not sufficient -- we need the entire DHCPACK to be passed
> >> (somehow) to the loading kernel.  I've discussed this a bit with phcoder, and
> >> he suggested adding another member to the multiboot structure off of which we
> >> can hang the DHCPACK packet.  The environment variables may also have value,
> >> for other OSes that don't use multiboot.
> >>
> >>   --S
> >>
> >> Quoting Aleš Kapica, who wrote the following on Thu, 15 Oct 2009:
> >>
> >>> Could I ask you for apply patch from attachment on pxecmd.c in grub2, please?
> >>> It's adding an option -s to the command pxe, which do make possible set IP
> >>> addresses of the server and the client machine, got from PXE, among grub2
> >>> enviroment variables.
> >>> DHCP gives IP according to MAC address, and we use it to identify the client
> >>> station by IP address.
> >>>
> >>> Thanks a lot, with regards Aleš Kapica
> >>>
> >
> > Having the Client IP avaible inside grub.cfg might be useful for some.
> > Then you could have one grub.cfg for all your machines and if one or a
> > small number of it needs some special stuff, you could just check for
> > the IP inside the grub.cfg. Then you don't need to use a seperate one
> > for them.
> 
>   Please, no.  That's terribly non-scalable for a large number of clients 
> (enterprise deployments).  We definitely need a solution that includes the 
> configuration file to use as a DHCP option.

Both methods should coexist fine.
I didn't meant to implement only this and not the option-150.
I just thought that this method might have an advantage for some people
over the other.

As I said as last sentence
>But maybe this isn't that useful if option-150 gets implemented which
>Yoann requested.


-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer




      parent reply	other threads:[~2009-10-15  8:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15  6:52 Patch for export IP addresses from PXE into grub2 enviroment variables Aleš Kapica
2009-10-15  6:53 ` Seth Goldberg
2009-10-15  7:38   ` Felix Zielcke
2009-10-15  7:51     ` Seth Goldberg
2009-10-15  8:00       ` Vladimir 'phcoder' Serbinenko
2009-10-15  8:04         ` Seth Goldberg
2009-10-15  8:07         ` Yoann Moulin
2009-10-15  8:05       ` Felix Zielcke [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=1255593940.3243.6.camel@fz.local \
    --to=fzielcke@z-51.de \
    --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.