Date: Tue, 28 Apr 2009 23:34:33 +0200 From: Ivan Voras <ivoras@freebsd.org> To: Diego Depaoli <trebestie@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Help me understand glabel Message-ID: <9bbcef730904281434v19a11429kf194f058b083eeee@mail.gmail.com> In-Reply-To: <83e5fb980904281405o6108524dh4cc288facf18891b@mail.gmail.com> References: <83e5fb980904281109k23dac4d3head2e6f65235f5ea@mail.gmail.com> <gt7ko6$o6j$1@ger.gmane.org> <83e5fb980904281405o6108524dh4cc288facf18891b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/4/28 Diego Depaoli <trebestie@gmail.com>: > 2009/4/28 Ivan Voras <ivoras@freebsd.org>: >> 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? > > So, glabel it's not a way to assign a specific volume label? > Reading the handbook it looks like glabel label is an 'alias' for tunefs -L. Glabel is a "read-only" tool (i.e. it only reads existing labels) in all but one case: it can create a special type of labels not related to file systems. It has nothing to do with "tunefs -L". But is that your original problem? If you have all three labels pointing to the same file system (glabel, UFS volume label, UFS ID label), you actually have 4 /dev entries pointing to the same device?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9bbcef730904281434v19a11429kf194f058b083eeee>