Date: Tue, 25 Jan 2005 07:32:58 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: rwatson@freebsd.org Cc: pete@altadena.net Subject: Re: Devd event from GEOM? Message-ID: <20050125.073258.94555150.imp@bsdimp.com> In-Reply-To: <Pine.NEB.3.96L.1050125093919.75661H-100000@fledge.watson.org> References: <20050124.204644.32725683.imp@bsdimp.com> <Pine.NEB.3.96L.1050125093919.75661H-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <Pine.NEB.3.96L.1050125093919.75661H-100000@fledge.watson.org>
Robert Watson <rwatson@freebsd.org> writes:
:
: On Mon, 24 Jan 2005, M. Warner Losh wrote:
:
: > : Since they constitute different "things" with quite different management
: > : properties. This also provides additional contextual information: rather
: > : than devd having to guess what type of object a device node is using name
: > : matching, by learning about it through geom or the network stack, it knows
: > : what kind it is up front in a strong way.
: >
: > While I tend to agree, I do think that GEOM is the wrong layer to
: > announce things from. The more correct layer would be /dev, since you
: > are again assuming that a GEOM that's created with name foo is
: > accessible via /dev/foo.
:
: So suppose I'm listening to a devd socket to try and identify storage
: devices arriving that I can automount. How do I know which device
: announcements are for storage devices?
Hmmmm, once upon a time I'd have said 'stat the device, and you know'
since those would be block devices.... The trouble is that we don't
know at that level either, yet when the GEOM even happens, how can we
be sure that we win that race?
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050125.073258.94555150.imp>