I think the semantics for this would create usability issues.  Say you
have the DHCP client running, and you insert a new card.  If
"configure me" isn't a property inherent in the driver, how does the
client know, when it sees the message indicating that a card has been
inserted, that it should configure that card.

What really happens now is that you set up a client configuration file
that lists interfaces that need special treatment, and the client then
configures interfaces as they appear (although right now you have to
signal it to load up new interfaces).   To automate this, I'd think
you'd want the DHCP client to be able to decide right when the
interface came up what to do with it, rather than having a user
process do it.   So your proposed flag doesn't really buy us an
advantage.

BTW, it looks like the latest DHCP code is going to go out under the
BSD license, so we can move up to the 3.0 license, which has the
ability to be told that an interface has appeared or been removed, and
also does DDNS updates and fun stuff like that.

			       _MelloN_