Date: Sat, 13 Sep 2003 15:36:58 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: DougB@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: devd/devctl Message-ID: <20030913.153658.43409469.imp@bsdimp.com> In-Reply-To: <20030913142107.V85817@12-234-22-23.pyvrag.nggov.pbz> References: <20030912212606.3d04f3ed.refugee@vt.edu> <20030913.003350.98343503.imp@bsdimp.com> <20030913142107.V85817@12-234-22-23.pyvrag.nggov.pbz>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20030913142107.V85817@12-234-22-23.pyvrag.nggov.pbz>
Doug Barton <DougB@freebsd.org> writes:
: 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. :)
You can't do it in devd. You must be able to either (a) tell a
running dhclient about arrival/departures of interfaces or (b) run
multiple dhclients. Make dhclient do one or the other. devd can't
help you here until one or the other of these work.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030913.153658.43409469.imp>