Quoting David Enderson <DEnderson@xxxxxxxxxxxxxx>:
> No, I haven't forgotten about DHCP. :-)
I know that, as I know I'm part of the problem you are bringing up here.
Let's see if I could help more...
> 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.
Agreed.
Give me some days and I'll try to expose in details what I've in mind for DHCP
support for our network stack. I promise.
Otherwise fee free to wake me ;-)
> 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.
Okay, let's move here:
- I promise to give you here on this mailing list soon a detailed specification
of what I've in mind for DHCP implementation and integration in our network
stack
- then, point me/us at what still needs more explanations
> As many specific project requirements as you could give me would be
> helpful. :-)
Yep, I understand, but I'm here like everyone, balancing small amount of free
times and a tall todo tasks list. I acknowledge that I'm currently focusing
away of networking kit ATM, and unfortunatly even Haiku as a whole...
I will try to improve that issue.
- Philippe
