Date: Tue, 25 Jan 2005 10:10:21 -0700 (MST) From: Warner Losh <imp@harmony.village.org> To: rwatson@FreeBSD.org Cc: imp@bsdimp.com Subject: Re: Devd event from GEOM? Message-ID: <20050125.101021.41686898.imp@harmony.village.org> In-Reply-To: <Pine.NEB.3.96L.1050125170138.3036H-100000@fledge.watson.org> References: <20050125.095536.104086303.imp@harmony.village.org> <Pine.NEB.3.96L.1050125170138.3036H-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> It depends a bit on where we sit: we probably want a neteventd that knows > about this sort of thing and performs unified network interface > management. In the mean time, I just want dhclient launched, because > dhclient already knows about ssid's, link state, etc. We don't neet yet another daemon around for that. > The idea behind the class information is that the application can use a > combination of the class, name, configuration data, and direct > communication with the object to do useful things. However, to > communicate with an object today, you first need the class information, > which is why you want it early as part of the event notification. Right now we can't even get the class information out of the userland interfaces we have. We should correct that problem, rather than complicate things prematurely because it is expedient to do so today. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050125.101021.41686898.imp>