From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Hard drives not detected in repeatable order.
Date: Mon, 3 Oct 2011 22:37:05 +0100 [thread overview]
Message-ID: <20111003223705.4e695381@zaphod.digimed.co.uk> (raw)
In-Reply-To: <CAEH5T2MT7AdsibkdfhVvzvc4BkmROTRMVWMT8RDtSNUJerQ_+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On Mon, 3 Oct 2011 14:28:05 -0500, Paul Hartman wrote:
> > They have the advantage over UUID's in that you can set them and
> > therefore can be human readable.
You can set the UUIDs yourself too, but I think they have to stick to the
standard format.
> Also, if you use a desktop
> > environment, they look nice in file managers.
>
> AFAIK that benefit of labels can also be a danger. If you have
> multiple systems and use the same label naming scheme on all of them
> (for example you call your partitions "root" "home" "swap" etc.) and
> someday you plug the HDD from one system into the other, it could
> cause confusion by potentially choosing the wrong one. But someone can
> correct me if I'm wrong. :)
If you have multiple systems, the sensible approach it to give each
filesystem a unique label, such as hostname-mountpoint, which also has
the benefit of making it clear which box a drive came from when you get
them mixed up.
--
Neil Bothwick
This is as bad as it can get-but don't bet on it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-03 21:38 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 18:40 [gentoo-user] Hard drives not detected in repeatable order Grant Edwards
2011-10-03 18:47 ` Canek Peláez Valdés
2011-10-03 18:48 ` Volker Armin Hemmann
2011-10-03 18:49 ` [gentoo-user] " Grant Edwards
2011-10-03 19:03 ` Canek Peláez Valdés
2011-10-03 19:28 ` Paul Hartman
2011-10-03 19:47 ` Michael Mol
2011-10-03 19:49 ` Canek Peláez Valdés
2011-10-03 21:37 ` Neil Bothwick [this message]
2011-10-04 2:25 ` Walter Dnes
2011-10-04 2:45 ` Canek Peláez Valdés
2011-10-04 15:43 ` bill.longman
2011-10-04 3:15 ` Dale
2011-10-04 4:54 ` Spidey
2011-10-04 5:00 ` Canek Peláez Valdés
2011-10-04 5:02 ` Adam Carter
2011-10-04 5:09 ` Canek Peláez Valdés
2011-10-04 5:29 ` Florian Philipp
2011-10-04 5:36 ` Canek Peláez Valdés
2011-10-04 5:10 ` Paul Hartman
2011-10-04 5:20 ` Canek Peláez Valdés
2011-10-04 5:25 ` Adam Carter
2011-10-04 5:28 ` Canek Peláez Valdés
2011-10-04 14:23 ` Grant Edwards
2011-10-04 14:18 ` Grant Edwards
2011-10-04 15:12 ` Canek Peláez Valdés
2011-10-04 14:02 ` Michael A. Koerber
2011-10-04 14:29 ` Grant Edwards
2011-10-04 14:47 ` Spidey
2011-10-04 15:59 ` Florian Philipp
2011-10-05 5:53 ` Walter Dnes
2011-10-05 13:29 ` Michael A. Koerber
2011-10-05 14:34 ` Florian Philipp
2011-10-05 18:54 ` walt
2011-10-05 19:57 ` pk
2011-10-05 20:31 ` Paul Hartman
2011-10-05 20:33 ` Florian Philipp
2011-10-04 14:48 ` Paul Hartman
2011-10-04 15:01 ` Dale
2011-10-03 18:50 ` [gentoo-user] " Michael Mol
2011-10-03 19:01 ` Florian Philipp
2011-10-03 19:15 ` Bill Longman
2011-10-03 19:34 ` Paul Hartman
2011-10-03 20:13 ` [gentoo-user] " Grant Edwards
2011-10-03 19:38 ` [gentoo-user] " Mick
2011-10-03 20:20 ` [gentoo-user] " Grant Edwards
2011-10-03 19:46 ` [gentoo-user] " Dale
2011-10-03 19:54 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111003223705.4e695381@zaphod.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox