Date: Tue, 27 Nov 2001 14:47:35 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Warner Losh <imp@harmony.village.org> Cc: arch@FreeBSD.ORG, Dima Dorfman <dima@trit.org> Subject: Re: Anybody working on devd? Message-ID: <XFMail.011127144735.jhb@FreeBSD.org> In-Reply-To: <200111272245.fARMjKM17357@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27-Nov-01 Warner Losh wrote: > In message <200111272243.fARMhbM17326@harmony.village.org> Warner Losh > writes: >: But pccard doesn't deal in terms of dev_t, but rather device_t. The >: pccard bus system has no earthly clue what you just added to the >: system. Plus, unless jlemon has been busy, the network drivers do not >: add dev_t's. >: >: : The advantages of this approach is that it's very simple, doesn't >: : strictly depend on devfs, can probably be used to replace pccardd and >: : usbd (although I haven't looked at the latter much), and if we stick a >: : call to the hypothetical notify_userland() function in make_dev(), it >: : can somewhat be used to control permissions in /dev, although not >: : satisfactorily. >: >: I dislike this approach because it depends on dev_t rather than >: device_t. And there's no way to notify userland that "The bus says >: the plug and play info is XYZ, but no driver attached." so that the >: daemon can load the right driver. > > I'd also point out that devfsd, in my world view, dealt with dev_t, > while devd dealt with device_t. That's a good way of putting it, yes. :) > Warner -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.011127144735.jhb>