Subject: RE: DHCP client, integration with ifconfig, etc.
To: 'Ted Lemon'" , "'Rafal Boni' <firstname.lastname@example.org>
From: Adam Glass <email@example.com>
Date: 02/08/1997 14:32:17
How are you going to support NFS diskless operation with a user land
You could put it all in the kernel but I think that's overkill. I'd put
enough support in the kernel to make the initial request/replies and
interpret only the critical info i.e ip address, subnet mask, etc. Once
you're booted, your dhcp client could make the same request and parse
anything additional. You should get back the same info as the kernel did.
Also, may I presume that your DHCP client will run as a daemon or something
or be spawned by ifconfig?
From: Ted Lemon [SMTP:firstname.lastname@example.org]
Sent: Saturday, February 08, 1997 6:46 AM
To: Rafal Boni
Cc: email@example.com; firstname.lastname@example.org
Subject: Re: DHCP client, integration with ifconfig, etc.
I'm in the middle of hacking on a real DHCP client, which is based on
some Linux-specific code contributed by Elliot Poger. I'm planning to
announce a release sometime next week, assuming that all goes well.
This will be better than duct-tape-and-spit.
I actually would like to propose some kernel changes to support DHCP
clienthood at some point, but I need to think about it a bit first.
The problem is that it should be possible to guarantee that the kernel
stops using an IP address once the lease runs out, and I think this
should be done by having a kernel process or event sitting around
removing addresses when they expire. Any flames about The Right Way
of doing this would be considered with great interest.