From: Max Nikulin <manikulin@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] docs: admin: devices: /dev/sr<N> for SCSI CD-ROM
Date: Sat, 29 Nov 2025 22:01:41 +0700 [thread overview]
Message-ID: <c5bb2474-b66d-47e5-b392-b12c4db979df@gmail.com> (raw)
In-Reply-To: <aSqPHMSgtHN7ty8-@archie.me>
On 29/11/2025 13:13, Bagas Sanjaya wrote:
> On Sat, Nov 29, 2025 at 12:12:32AM +0700, Max Nikulin wrote:
>> +Usage of ``/dev/scd?`` as alternate SCSI CD-ROM names for ``sr?`` devices
>> +ended around year 2011.
>
> What about "Support for /dev/scd? as alternative names for /dev/sr? has been
> removed in 2011"?
If others support your suggestion then I do not mind. Feel free to
commit preferred variant ignoring my patch.
I would be more verbose however by adding that it was removed namely
from udev:
Creation of ``/dev/scd?`` alternative names for ``sr?`` CD-ROM and other
optical drives (using SCSI commands) was removed in ``udev-174``
(released in 2011).
Perhaps I am biased by my confusion. Noticed that wodim tries to access
currently absent /dev/scd0 for kernels >= X.6, I tried git blame game in
kernel repository to find kernel version when scd<N> were renamed to
sr<N>. It took some time for me to realize that it is impossible to
determine scd vs. sr from kernel version. That is why I would consider
adding explicit mention of udev. Otherwise for me it sounds like that
scd? names were removed from kernel. I am not a native English speaker,
so I do not insist on my variant.
How long I should wait for comments before submitting another revision
of the patch? I hope, pending changes are not an obstacle for those who
are tempting to review the whole devices.rst file.
next prev parent reply other threads:[~2025-11-29 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 17:12 [PATCH] docs: admin: devices: /dev/sr<N> for SCSI CD-ROM Max Nikulin
2025-11-29 6:13 ` Bagas Sanjaya
2025-11-29 15:01 ` Max Nikulin [this message]
2025-11-30 1:54 ` Bagas Sanjaya
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=c5bb2474-b66d-47e5-b392-b12c4db979df@gmail.com \
--to=manikulin@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).