Re: devd limitations / automounting removable storage

From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 09/18/03

  • Next message: M. Warner Losh: "Re: devd limitations / automounting removable storage" 
    To: Doug Rabson <dfr@nlsystems.com>
Date: Thu, 18 Sep 2003 13:43:45 +0200

    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.
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: M. Warner Losh: "Re: devd limitations / automounting removable storage"