From owner-freebsd-questions@FreeBSD.ORG Mon Oct 19 13:45:56 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 908701065694 for ; Mon, 19 Oct 2009 13:45:56 +0000 (UTC) (envelope-from af.gourmet@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id 6BF458FC25 for ; Mon, 19 Oct 2009 13:45:56 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=UTF-8 Received: from [192.168.0.51] ([96.21.103.185]) by VL-MO-MR002.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-4.01 (built Aug 3 2007; 32bit)) with ESMTP id <0KRR00FNSKW4GVB0@VL-MO-MR002.ip.videotron.ca> for freebsd-questions@freebsd.org; Mon, 19 Oct 2009 09:45:40 -0400 (EDT) Message-id: <4ADC6D89.10600@videotron.ca> Date: Mon, 19 Oct 2009 09:45:45 -0400 From: PJ User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: "freebsd-questions@freebsd.org" Subject: glabel clarification X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2009 13:45:56 -0000 I understood that labeling a disk with glabel would permit the disk to be switched to another system and booting from that disk would not require other manupulations than adjusting network configuration, samba, rc.conf and a few others.. But what if there is already a disk on the system with the identical labels in /dev/label/ ? I understood that whatever the actual disk might be (ad4, ad12, ad1...)would be irrelevant? It would appear that the actual booting goes according to the label; so, if there are duplicate labels the boot will not necessarily be from the newly installed disk if there is another disk with duplicate glabel labels? So doing a glabel seems superfluous... What then is the real purpose of glabel, since the boot process seems to need a unique identifier?