Date: Thu, 18 Sep 2003 13:43:45 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Doug Rabson <dfr@nlsystems.com> Cc: freebsd-arch@freebsd.org Subject: Re: devd limitations / automounting removable storage Message-ID: <2559.1063885425@critter.freebsd.dk> In-Reply-To: Your message of "18 Sep 2003 11:31:36 BST." <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 write s: >I've thought for a long time now that the right way to do this is to >extend the newbus device tree much further down the hierarchy than it currently does. Currently the tree stops at the CAM/ATA controller. Both >of those systems then use their own custom hand-crafted wheels to probe >for and attach their attached drives. After finding the drives, we hand >them over to yet another custom hand-crafted wheel (geom) to find the >partitions. > >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'm sorry Doug, I don't belive in "one size fits all" because it invariably means that it fits nobody at all. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2559.1063885425>