From owner-freebsd-current@FreeBSD.ORG Tue Jan 25 14:31:52 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7834316A4CE; Tue, 25 Jan 2005 14:31:52 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0678043D45; Tue, 25 Jan 2005 14:31:52 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0PEVckM051385; Tue, 25 Jan 2005 07:31:38 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 25 Jan 2005 07:32:58 -0700 (MST) Message-Id: <20050125.073258.94555150.imp@bsdimp.com> To: rwatson@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <20050124.204644.32725683.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: pete@altadena.net Subject: Re: Devd event from GEOM? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 14:31:52 -0000 In message: Robert Watson 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