From owner-freebsd-arch@FreeBSD.ORG Mon Jun 26 15:36:17 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B81A516A407; Mon, 26 Jun 2006 15:36:17 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B9C945434; Mon, 26 Jun 2006 15:36:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [IPv6:::1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k5QFYNhZ000449; Mon, 26 Jun 2006 09:34:23 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 26 Jun 2006 09:34:25 -0600 (MDT) Message-Id: <20060626.093425.1649769642.imp@bsdimp.com> To: pjd@freebsd.org From: "M. Warner Losh" In-Reply-To: <20060626080038.GA12511@garage.freebsd.pl> References: <20060626031636.GK82074@funkthat.com> <33398.1151304697@critter.freebsd.dk> <20060626080038.GA12511@garage.freebsd.pl> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: phk@phk.freebsd.dk, gurney_j@resnet.uoregon.edu, freebsd-arch@freebsd.org Subject: Re: Accessing disks via their serial numbers. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2006 15:36:17 -0000 In message: <20060626080038.GA12511@garage.freebsd.pl> Pawel Jakub Dawidek writes: : > I'm against until somebody have explained what the use is, and if : > use is proven, it should be done with devfs device-on-demand(/cloning) : > instead of g_label. : : I don't really care how we will make it visible for the user. This could : be devd(8) using some tool (diskinfo(8)?) to fetch serial number and : create a symlink to newly attached disk, but we need to have a general : mechanism inside the kernel for getting such informations. devd could do this. We'd need to bring in Robert's geom publishes to devctl patches, but that is doable. The only snag, alas, is that this won't be available very early in the boot process... Warner