Date: Thu, 18 Sep 2003 08:40:25 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: dfr@nlsystems.com Cc: freebsd-arch@freebsd.org Subject: Re: devd limitations / automounting removable storage Message-ID: <20030918.084025.71552256.imp@bsdimp.com> In-Reply-To: <1063881095.12179.5.camel@builder02.qubesoft.com> References: <Pine.NEB.3.96L.1030917161519.51283B-100000@fledge.watson.org> <1063881095.12179.5.camel@builder02.qubesoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <1063881095.12179.5.camel@builder02.qubesoft.com>
Doug Rabson <dfr@nlsystems.com> writes:
: Surely the right thing would be to use the same wheel (newbus) for all
: the probing, driver auction, device attachment jobs in the kernel. That
: would seemlessly allow devd to receive device notification events for
: geom's leaf partitions in exactly the same way that it receives all
: other notification events.
I tend to agree with the CAM/ata controller bit. Both were written
before newbus was well integrated into the tree. It makes no sense
that fdc has an fd newbus child but ata doesn't have an ad child.
However, having said that, I think we do need additional event types
because we're doing with different name spaces. But those events
might be in devd rather than devctl given that we can get those events
in userland in other ways if my investigations are OK.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030918.084025.71552256.imp>