
|
[openbeosnetteam]
||
[Date Prev]
[09-2005 Date Index]
[Date Next]
||
[Thread Prev]
[09-2005 Thread Index]
[Thread Next]
[openbeosnetteam] Re: DHCP Project Specs Needed
- From: "David Enderson" <DEnderson@xxxxxxxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Thu, 22 Sep 2005 13:08:11 -0500
I mentioned a while back on this list that eventually a way will be needed to
provide for expired DHCP leases, which means something like a background
process or cron script. The solaris implementation solves the lease issue by
having the DHCP client be a daemon.
> -----Original Message-----
> From: openbeosnetteam-bounce@xxxxxxxxxxxxx
> [mailto:openbeosnetteam-bounce@xxxxxxxxxxxxx] On Behalf Of
> Jérôme Duval
> Sent: Thursday, September 22, 2005 11:20
> To: openbeosnetteam@xxxxxxxxxxxxx
> Subject: [openbeosnetteam] Re: DHCP Project Specs Needed
>
> Maybe have a look at what other OS do, ie Solaris :
>
> http://docs.sun.com/app/docs/doc/806-4075/6jd69oaab?a=view
>
> Selon David Enderson <DEnderson@xxxxxxxxxxxxxx>:
>
> > Philippe,
> >
> > > I don't consider this as urgent as reaching beta stage of
> OpenGL Kit
> > > and the network stack missing features: DHCP,
> > > 802.11 support.
> > > Maybe that's because I never used socketpair() so far ;-)
> > >
> >
> > No, I haven't forgotten about DHCP. :-)
> >
> > I upgraded my BeOS machine which I was developing on to 1.5
> GB of RAM
> > because I really needed it with my dual boot Windows, and
> of course, I
> > experienced the well known RAM problem. I applied one of the
> > experimental fixes floating around for allowing more RAM, and all I
> > did was make it so BeOS won't boot, and oddly enough,
> neither will by
> > 5.0.3 install CD (even when I take out the extra RAM).
> >
> > Anyway, the point is that I've been struggling to figure out how to
> > keep developing for Haiku. My thought was that if I followed
> > DarkWyrm's instructions to build and install Haiku, that I
> could just
> > finish the development for DHCP on Haiku itself. Is that
> what you recommend?
> >
> > PROJECT SPECS
> >
> > A major frustration for me with trying to work on DHCP is that I've
> > never had a clear project specification with clear objectives. The
> > only thing I've received is a vague, "Make a standalone
> binary to do
> > DHCP and then we'll figure out how to integrate it." Much more
> > specific project specs would be nice.
> >
> > For example, I have no idea how you want me to actually set
> the IP.
> > Do I parse the network config file myself, change the IP, and then
> > restart networking? Is there another way you want me to do it? I
> > asked about parsing config files in the past and got vague and
> > ultimately unhelpful advice on this list. This has been
> the case with
> > about every question I've asked.
> >
> > As many specific project requirements as you could give me would be
> > helpful. :-)
> >
> > Thanks,
> > David
> >
> >
>
>
>
>
|

|