Re: Help me understand glabel

2009/4/28 Ivan Voras <ivoras_at_freebsd.org>:
>
> 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".
Understood. I suggest a better explanation on the handbook.

> 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?

Actually only 2
This is the output of my dmesg | grep GEOM
GEOM_LABEL: Label for provider ad4s1 is ntfs/master.
GEOM_LABEL: Label for provider ad4s4a is label/rootamd64.
GEOM_LABEL: Label for provider ad4s4a is ufsid/49e99a08b75f8e02.
GEOM_LABEL: Label for provider ad4s4d is label/varamd64.
GEOM_LABEL: Label for provider ad4s4d is ufsid/49e99a09096f9933.
GEOM_LABEL: Label for provider ad4s4e is label/tmpamd64.
GEOM_LABEL: Label for provider ad4s4e is ufsid/49e99a0807d6e8cc.
GEOM_LABEL: Label for provider ad4s4f is label/usramd64.
GEOM_LABEL: Label for provider ad4s4f is ufsid/49e99a084d314fd2.
GEOM_LABEL: Label for provider ad6s2 is label/homebsd.
GEOM_LABEL: Label for provider ad6s2 is ufsid/47f7a96c87b497e3.
GEOM_LABEL: Label for provider ad6s3 is ntfs/Dat.
GEOM_LABEL: Label for provider ad6s4 is ext2fs/DataShared
...
as you see ntfs and ext2fs volumes are listed once, ufs twice.
I think hal tries to mount all these devices giving me a lot of errors.
Before glabeling disks hal showed ufsid, now, undecided between ufsid
and label, shows a generic disk-XX.

I was looking for a way to get more descriptive labels to avoid
misunderstanding under nautilus or dolphin (e.g. usrbsd instead of
Volume 20GB), but now I'm worse than before.

Cheers
-- 
Diego Depaoli