Date: Sat, 13 Sep 2003 14:26:29 -0700 (PDT) From: Doug Barton <DougB@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: devd/devctl Message-ID: <20030913142107.V85817@12-234-22-23.pyvrag.nggov.pbz> In-Reply-To: <20030913.003350.98343503.imp@bsdimp.com> References: <20030912212606.3d04f3ed.refugee@vt.edu> <20030913.003350.98343503.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 13 Sep 2003, M. Warner Losh wrote:
> Yes. that has been the plan for some time now. However, dhclient is
> really lame in a lot of ways. Martin Blapp has made it a lot better
> of lates. In geral, I tend to believe that I shouldn't fix bugs in
> dhclient with devd things. However, a more general trend to more
> event types would be good because a device arriving isn't quite the
> same as a network interface arriving...
In dhclient's defense, it's really designed to provide functionality on
a wide variety of platforms, with a wide variety of dhcpd's, so it has
"issues." I think Martin did a good job of defining an improvement that
applies to all/most platforms (only try to broadcast if we have link).
That functionality is being ported back to the vendor, if it hasn't been
already. If we want really cool whizbang features that are more specific
to us, we _should_ be looking at stuff like devd. The trick is definig
which problem space we're addressing at any given moment. :)
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030913142107.V85817>