From owner-freebsd-arch@FreeBSD.ORG Mon Jun 26 12:22:01 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 29F1316A401 for ; Mon, 26 Jun 2006 12:22:01 +0000 (UTC) (envelope-from fb-arch@psconsult.nl) Received: from ps226.psconsult.nl (ps226.psconsult.nl [213.222.19.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 971EB43D4C for ; Mon, 26 Jun 2006 12:21:58 +0000 (GMT) (envelope-from fb-arch@psconsult.nl) Received: from phuket.psconsult.nl (localhost [127.0.0.1]) by phuket.psconsult.nl (8.13.1/8.13.1) with ESMTP id k5Q8cTpl030825 for ; Mon, 26 Jun 2006 10:38:29 +0200 (CEST) (envelope-from fb-arch@psconsult.nl) Received: (from paul@localhost) by phuket.psconsult.nl (8.13.1/8.13.1/Submit) id k5Q8cTPa030824 for freebsd-arch@freebsd.org; Mon, 26 Jun 2006 10:38:29 +0200 (CEST) (envelope-from fb-arch@psconsult.nl) X-Authentication-Warning: phuket.psconsult.nl: paul set sender to fb-arch@psconsult.nl using -f Date: Mon, 26 Jun 2006 10:38:28 +0200 From: Paul Schenkeveld To: freebsd-arch@freebsd.org Message-ID: <20060626083828.GA18912@psconsult.nl> Mail-Followup-To: freebsd-arch@freebsd.org References: <20060626031636.GK82074@funkthat.com> <33398.1151304697@critter.freebsd.dk> <20060626080038.GA12511@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060626080038.GA12511@garage.freebsd.pl> User-Agent: Mutt/1.5.6i 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 12:22:01 -0000 On Mon, Jun 26, 2006 at 10:00:38AM +0200, Pawel Jakub Dawidek wrote: > 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. And make mounting /tmp, /var, /usr and so on depending on a running devd? Do we need /usr/bin/sed or /usr/bin/awk to mangle the output of diskinfo? I agree with Poul-Henning about the namespace pollution but I've been fighting the devicename shift when changing the hardware configuration so often that I also like the idea of something I could really rely on. Same issue with fxp0 and fxp1 on the motherboard becoming fxp1 and fxp2 when inserting another fxp card. Some things are just a bit too dynamic sometimes, but that's another discussion. I don't want to change the way the world is and certainly not violate POLA but just to add another angle to the discussion, life would be nice if we had something like: /dev/ad/0 /dev/ad/0/whole_disk /dev/ad/0/s1 /dev/ad/0/s1a /dev/ad/0/s1c and /dev/ad/ -> 0 $.02 Regards, Paul Schenkeveld