From owner-freebsd-current@FreeBSD.ORG Wed Apr 29 06:05:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FA871065672 for ; Wed, 29 Apr 2009 06:05:08 +0000 (UTC) (envelope-from mel.flynn+fbsd.current@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 4B32C8FC08 for ; Wed, 29 Apr 2009 06:05:07 +0000 (UTC) (envelope-from mel.flynn+fbsd.current@mailing.thruhere.net) Received: from sarevok.dnr.servegame.org (mailhub.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id A21707E837; Tue, 28 Apr 2009 22:05:06 -0800 (AKDT) From: Mel Flynn To: freebsd-current@freebsd.org Date: Wed, 29 Apr 2009 08:05:04 +0200 User-Agent: KMail/1.11.2 (FreeBSD/8.0-CURRENT; KDE/4.2.2; i386; ; ) References: <83e5fb980904281109k23dac4d3head2e6f65235f5ea@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904290805.04842.mel.flynn+fbsd.current@mailing.thruhere.net> Cc: Ivan Voras Subject: Re: Help me understand glabel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 29 Apr 2009 06:05:08 -0000 On Tuesday 28 April 2009 21:17:07 Ivan Voras wrote: > Diego Depaoli wrote: > > Now glabel list shows each entry twice under /dev/label and under > > /dev/ufsid so hal is a bit confused. > > It is normal or I were wrong? > > Your problem is that hal cannot figure out that two labels point to the > same device? So how was it dealing with it before, when you had the > device/partition itself (i.e. /dev/ad0s1a) and its specific volume label? Hal will propagate both and you'll get two notifications from whatever mount app you're using. My workaround is to ignore the "filesystem based labels" (/dev/ufs/*) in an fdi. -- Mel