From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rename /dev/nvme0n1 to /dev/sda
Date: Sun, 3 Sep 2017 21:38:23 -0400 [thread overview]
Message-ID: <CAGfcS_kABZZVNCWo1pCt3UTaXUUqR0bp+ZAFadNW-OMj160rvA@mail.gmail.com> (raw)
In-Reply-To: <CAJ0EP40Yh2KXx2Jinimf5NYAxEVGF6AUU1Osx-fw_65YkHvSfg@mail.gmail.com>
On Sun, Sep 3, 2017 at 9:26 PM, Mike Gilbert <floppym@gentoo.org> wrote:
>
> I would suggest you utilize the existing symlinks in one of the
> /dev/disk/ sub-directories, or create some udev rules to create your
> own symlinks based on whatever metadata you wish. I would also suggest
> you read the udev(7) manual page.
>
++
Labels are the most obvious solution to this sort of problem
(especially if you want a generic system image that you can install in
multiple places and not have to tweak). UUIDs are the other obvious
solution, but that does need to be tailored to each install.
I have used extra symlinks with udev in other situations. For
example, I used to control two tuners via pl2303 serial ports and I
used a rule to add a symlink based on the physical USB port each was
plugged into, since otherwise I couldn't rely on the two devices being
enumerated consistently.
--
Rich
next prev parent reply other threads:[~2017-09-04 1:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 16:10 [gentoo-user] Rename /dev/nvme0n1 to /dev/sda Grant
2017-09-02 2:58 ` R0b0t1
2017-09-02 6:48 ` Andrew Savchenko
2017-09-02 13:14 ` Canek Peláez Valdés
2017-09-03 17:59 ` Grant
2017-09-03 18:11 ` Canek Peláez Valdés
2017-09-04 4:26 ` J. Roeleveld
2017-09-04 5:08 ` Canek Peláez Valdés
2017-09-02 14:35 ` Mike Gilbert
2017-09-03 18:11 ` Grant
2017-09-03 22:24 ` Mike Gilbert
2017-09-03 22:41 ` Grant
2017-09-04 1:26 ` Mike Gilbert
2017-09-04 1:38 ` Rich Freeman [this message]
2017-09-04 14:58 ` Grant
2017-09-04 15:00 ` Grant
2017-09-04 15:33 ` J. Roeleveld
2017-09-04 15:40 ` Mike Gilbert
2017-09-04 19:22 ` Grant
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=CAGfcS_kABZZVNCWo1pCt3UTaXUUqR0bp+ZAFadNW-OMj160rvA@mail.gmail.com \
--to=rich0@gentoo.org \
--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