From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard drives not detected in repeatable order.
Date: Mon, 3 Oct 2011 11:47:03 -0700 [thread overview]
Message-ID: <CADPrc83sQU5weNA8jZnZqtp0SdWkv1OHQv5pcX6owZ2ahe51Aw@mail.gmail.com> (raw)
In-Reply-To: <j6cvil$172$1@dough.gmane.org>
On Mon, Oct 3, 2011 at 11:40 AM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> Just recently I've run in to problems because my hard drives are not
> detected in a predictable order, so my fstab that mount /dev/sdb1 and
> /dev/sdc1 sometimes result in directory trees in the wrong places
> (/dev/sda seems consistent, but I don't know why).
>
> What's the recommended way to fix this?
You can set labels to all the partitions, and set /etc/fstab to use
them: my fstab looks like:
LABEL=Gentoo / ext4 noatime 0 1
LABEL=Swap none swap sw 0 0
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
tmpfs /tmp tmpfs defaults,nosuid 0 0
I believe this is the recommended way to use fstab in distros like
Fedora and OpenSUSE, because of your use case exactly.
You can set labels to ext[234] partitions with e2label, and for NTFS
partitions you can use ntfslabel, and to swap partitions with mkswap.
I suppose every filesystem in the world has a similar tool to set its
label.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2011-10-03 19:36 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 [this message]
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
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=CADPrc83sQU5weNA8jZnZqtp0SdWkv1OHQv5pcX6owZ2ahe51Aw@mail.gmail.com \
--to=caneko@gmail.com \
--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