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, 15 Sep 2020 14:27:02 +0000	[thread overview]
Message-ID: <bug-209089-208809-Ahezwz46WG@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 #15 from Manish Jain (bourne.identity@hotmail.com) ---
Hi Alan,

Nice to see your response to the reopened PR.

1)
'mount /dev/uda<TAB>' : I think you are missing the point about USB disk
attachments. As I said earlier, there usually there will usually be only one of
those (I never had to attach 2 pen drives simultaneously). So there will
usually be only a /dev/uda in the ud* - or else nothing in the ud* series.

So you can start tabbing at 'd' : mount /dev/ud<TAB>.

So that definitely provides the adavantage of 1 character less to type at a
time when you want to type less.

2)
'it would be one more thing to remember, so worse in that respect'. Sir, my
humble intuition is this would be an advantage. So many changes (eth0 ->
enp9s0) happen with no real benefit to the end user. This one has an advantage:
one character less to type, plus the comfort of the knowledge that USB have
their own series. People will welcome this change, if it were permitted to
happen.

3)
'it would mean changing all the existing shell scripts and /etc/fstab files
that already use the /dev/sdb* names' :

find . -type f -name '*.sh' -exec sed 's/sdb/uda/g' {} \;;

Thanks again for your response.
Manish Jain

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

  parent reply	other threads:[~2020-09-15 23:32 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
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 [this message]
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-Ahezwz46WG@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.