From owner-freebsd-current@FreeBSD.ORG Mon Jan 24 06:22:29 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 E034116A4CE for ; Mon, 24 Jan 2005 06:22:29 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3751D43D4C for ; Mon, 24 Jan 2005 06:22:29 +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 j0O6MDvf082753; Sun, 23 Jan 2005 23:22:13 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 23 Jan 2005 23:23:32 -0700 (MST) Message-Id: <20050123.232332.48399079.imp@bsdimp.com> To: pete@altadena.net From: "M. Warner Losh" In-Reply-To: <20050124055703.GA40104@users.altadena.net> References: <20050124055703.GA40104@users.altadena.net> 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 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: Mon, 24 Jan 2005 06:22:30 -0000 In message: <20050124055703.GA40104@users.altadena.net> Pete Carah writes: : Geom doesn't feed node-creations to devd in 5.3. This would be VERY useful : for letting ordinary non-programmer users access pen drives, among : other things (floppies come to mind too...). : (or mount e.g. a pen drive as part of an authentication system where no-one is : yet logged in, so can't manually mount...) True. : umass0 comes in to devd, but this isn't useful for use in "mount". One : needs the disk device nodes. I suppose one *could* parse dmesg for : the info (or maybe sysctl) but that smacks of a serious kluge. (not to : mention that the slice table isn't represented in dmesg anyhow, and : practically nothing is in sysctl...) One of the problems is that CAM doesn't use newbus devices, so you don't see da0 devices arrive. Further, it is not possible to trace back, using only newbus methods, what devices are attached to the umass. : Does this yet happen in any later version (RELENG_5 or HEAD)? : If not, is there anyone planning or working on it? I have some patches that export the GEOM events to devd. I'd rather have something that watches /dev and reports those. : Geom is modular enough that this shouldn't be difficult... I have my doubts that GEOM is the right layer to do this. That's one reason I've not committed the fixes. /dev is better, but also has some drawbacks. Warner