devd limitations / automounting removable storage

[Doug Rabson]

On Thu, 2003-09-18 at 11:43, Poul-Henning Kamp wrote:
> In message <1063881095.12179.5.camel at 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.

Well in this case, its a size which seems to fit virtually everything
else in the system pretty well. I remember what it was like before when
every different kind of driver (pci, eisa, isa, whatever) was written in
a completely different incompatible undocumented style and I happen to
think that the new way works pretty well. I really doubt that the
partition to driver matching system of geom or the device to driver
matching system in ATA does anything very different from any other part
of the device tree.