All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209089] USB storage devices appear as SATA devices
Date: Tue, 01 Sep 2020 16:10:43 +0000	[thread overview]
Message-ID: <bug-209089-208809-sAfX4t36jf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209089-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209089

--- Comment #9 from Alan Stern (stern@rowland.harvard.edu) ---
(I bet you could have fixed the fstab contents by booting from the pen drive in
"rescue" mode, with no need to have FreeBSD installed.)

Changing the monikers is only a partial solution.  For example, devices that
show up as uda and udb one day could very well show up as udb and uda the next
day.

Also, suppose your system's primary hard disk was attached by USB rather than
SATA.  Then the pen drive could have been labelled uda and the primary drive
labelled udb, and your fstab would still be messed up.  This is part of the
reason why people recommend using filesystem or GUID labels for fstab entries
rather than drive names and partition numbers.

In short, changing the monikers isn't going to happen, and even if it did
happen it wouldn't fully fix your original problem.

However, there is a way to set up your system to use permanently fixed drive
names that you assign.  All you have to do is write and install an appropriate
udev script.  Then you can make the drive names be anything you want.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-09-01 16:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-209089-208809@https.bugzilla.kernel.org/>
2020-09-01 11:30 ` [Bug 209089] USB storage devices appear as SATA devices bugzilla-daemon
2020-09-01 13:15 ` bugzilla-daemon
2020-09-01 13:28 ` bugzilla-daemon
2020-09-01 13:34 ` bugzilla-daemon
2020-09-01 13:35 ` bugzilla-daemon
2020-09-01 14:51 ` bugzilla-daemon
2020-09-01 15:03 ` bugzilla-daemon
2020-09-01 15:47 ` bugzilla-daemon
2020-09-01 16:10 ` bugzilla-daemon [this message]
2020-09-01 16:48 ` bugzilla-daemon
2020-09-01 20:31 ` bugzilla-daemon
2020-09-01 21:13 ` bugzilla-daemon
2020-09-14 20:42 ` bugzilla-daemon
2020-09-14 20:45 ` bugzilla-daemon
2020-09-15  1:25 ` bugzilla-daemon
2020-09-15 14:27 ` bugzilla-daemon
2020-09-15 14:30 ` bugzilla-daemon
2020-09-16  8:43 ` bugzilla-daemon
2020-09-16  8:56 ` bugzilla-daemon

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=bug-209089-208809-sAfX4t36jf@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.