From owner-freebsd-arch@FreeBSD.ORG Mon Jun 26 09:16:45 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 59F4E16A589; Mon, 26 Jun 2006 09:16:45 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 601DD43DC6; Mon, 26 Jun 2006 08:43:21 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 585FE1703F; Mon, 26 Jun 2006 08:43:17 +0000 (UTC) To: Pawel Jakub Dawidek From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 26 Jun 2006 10:00:38 +0200." <20060626080038.GA12511@garage.freebsd.pl> Date: Mon, 26 Jun 2006 08:43:14 +0000 Message-ID: <44838.1151311394@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: John-Mark Gurney , 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 09:16:45 -0000 In message <20060626080038.GA12511@garage.freebsd.pl>, Pawel Jakub Dawidek writ es: There is a not at all subtle difference between names which relate to the contents of the disk (as for g_label) or names which relate to a specific physical position (as for ATA_STATIC_ID) and what you propose where the name binds to a specific drive mechanism. The former two allows you to do offline copy/recovery and replacement of a disk drive, the latter does not. >Glabel(8) currently supports labeling any GEOM provider, but it steals >the last sector, which is not always acceptable. When is it not acceptable ? And is this the only reason why you think we need serial numbers for names ? >[...], but we need to have a general >mechanism inside the kernel for getting such informations. This is a very broad statement, and I don't agree (yet). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.