Date: Mon, 19 Oct 2009 15:59:43 +0200 From: "Johan Hendriks" <Johan@double-l.nl> To: "PJ" <af.gourmet@videotron.ca> Cc: freebsd-questions@freebsd.org Subject: RE: glabel clarification Message-ID: <57200BF94E69E54880C9BB1AF714BBCBA57086@w2003s01.double-l.local> References: <4ADC6D89.10600@videotron.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
>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?
Switching between machines is not what labels are for.(enlighten me if
it is)
As far as understand, it makes switching the drive in the same machine
easier.
It does not matter if labels are used, that the device is seen as
/dev/ad0 or /dev/ad{x}.
This makes adding and replacing disk much easier.
Sometimes the disk numbers change when removing raid controllers or
other hardware.
Regards,
Johan
=20
No virus found in this outgoing message.
Checked by AVG - www.avg.com=20
Version: 8.5.422 / Virus Database: 270.14.20/2444 - Release Date:
10/18/09 09:04:00
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57200BF94E69E54880C9BB1AF714BBCBA57086>