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 20:31:00 +0000	[thread overview]
Message-ID: <bug-209089-208809-JMTm2II9Hj@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 #11 from Alan Stern (stern@rowland.harvard.edu) ---
All right.  I don't have much time to spend on this, so I'll keep it brief.

Your point of view is too narrow.  As a maintainer, one quickly learns that any
change made to the kernel will affect _all_ users, not just the person who
requested the change.

You ran into a problem in one single situation (a new OS installation).  You
came up with an ad-hoc way to prevent the problem from occurring, but you
didn't think that your solution would _cause_ problems for many other people,
who rely (or have software that relies) on the current naming scheme.

Furthermore, it's a mistake to think that Linux runs only on desktop systems. 
In fact it gets used in everything from giant supercomputers to servers to
tablets to hobby boards to IoT devices to wearables.  Just because you have
never used a USB drive as the primary disk or attached two USB drives
simultaneously to your system doesn't mean nobody else has.

(In fact, one of my servers does have two USB drives attached.  They are used
for rotating backups.)

Furthermore, when presented with a well-known and commonly accepted technique
for avoiding the problem you encountered (using filesystem labels or GUID
labels), you rejected it.  If you don't want to use these things yourself,
that's fine -- but you shouldn't expect everyone else in the world to change
the naming conventions on their systems to suit your preference.

(In your triple-boot document, GUIDs would work perfectly well for everything
except the swap partition, because Windows would overwrite it.  But lack of a
swap partition wouldn't prevent you from booting.)

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

  parent reply	other threads:[~2020-09-01 20:31 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
2020-09-01 16:48 ` bugzilla-daemon
2020-09-01 20:31 ` bugzilla-daemon [this message]
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-JMTm2II9Hj@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.