Booting a machine over the network without pxe.

[omestre]

On Sun, 14 Sep 2003, John-Mark Gurney wrote:

 Well, i would be very happy with my patch in FreeBSD project!
 That without say that a "real" programmer would take care of the patch
:), and i will just use the features in my servers.... :))
 I don't know what should i do. I did think that after i submit a PR, the
devel men will fix any problems to fit the FreeBSD project needs. Sorry,
but is my first PR... Shall i fix it?? Well, shall i change the
boot.netif.hostname to kern.hostname? Because if so, it's very simple in
my patch, because is JUST a variable. For my patch do not cares the
variable name. Do you know what i mean? I've just put that name because i
did think that i was making a good thing. :))
 Or maybe you can do that? Tell me what i must to do, and i will make the
changes. I don't know how to make a new "OPTION" in FreeBSD kernel to my
patch, you can help me?
 Thanks again, sorry about the newbie questions, but i really don't know
the procedures.

 Leal

> Date: Sun, 14 Sep 2003 22:55:31 -0700
> From: John-Mark Gurney <gurney_j at efn.org>
> To: omestre <omestre at freeshell.org>
> Subject: Re: Booting a machine over the network without pxe.
>
> omestre wrote this message on Thu, Sep 11, 2003 at 14:26 +0000:
> > On Tue, 9 Sep 2003, John-Mark Gurney wrote:
> >
> > > boot.netif.hostname already exists as kern.hostname.  Why create yet
> > > another knob for the same value?
> >  I have used the structures that already exists.. for bootp or
> > pxe purposes...
>
> No, I did not misunderstand.
>
> >  Maybe you did not understand my patch (terrible english :), but I'm using
> > the loader.conf file to set that variables, and that ones (for bootp/pxe)
> > have a pattern, i think that follow it is nice. The variables are (i
>
>
> I understood your patch fine, and just so you know, your english isn't
> terrible.. I know many native english speakers who write more
> incomprehensible messages than this...
>
> > guess) for autoconfiguration task (in boot)... So boot.netif.hostname is
> > not the same as kern.hostname.
> >  But this decision for me is irrelevant, the devel man will decide what is
> > better. :))
>
> Well, I am a developer, and would like to not see this patch go in till
> it is fixed.  The reason I say this is that soon, we'll have another
> subsystem that sets the hostname for some reason, and they'll say, oh,
> the bootp subsystem has it's own copy of the hostname, and soon, we might
> have 5+ copies in the system, and then people won't know what one to us
> or which one is the most up to date or "real" hostname of the system.
>
> Ok, can you answer me what uses this variable?  Is this just storage
> of information obtained from bootp/PXE?  Do you end up setting kern.hostname
> from it?
>
> Is there a good technical reason in your opinion for keeing it in the
> "bootp" tree.
>
> --
>   John-Mark Gurney				Voice: +1 415 225 5579
>
>      "All that I will do, has been done, All that I have, has not."
>

omestre at sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org