From: Michael Tokarev <mjt@tls.msk.ru>
To: Oliver Neukum <oliver@neukum.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
andrew@walrond.org, linux-kernel@vger.kernel.org
Subject: Re: Scsi cdrom naming confusion; sr or scd?
Date: Sun, 05 Nov 2006 19:38:08 +0300 [thread overview]
Message-ID: <454E1370.5020403@tls.msk.ru> (raw)
In-Reply-To: <200611051541.37283.oliver@neukum.org>
Oliver Neukum wrote:
> Am Sonntag, 5. November 2006 15:06 schrieb Arjan van de Ven:
>> and this is why it's wrong to make naming policy a kernel thing!
>> Userspace is the right place to do this (and there I suspect the name
>> will end up being /dev/cdrom)...... the kernel really shouldn't care at
>> all what the name is.
>
> I have to disagree. This precisely shows that the reverse is true.
> This way the chance of having a default name guaranteed to work
> is lost. If you want an alternate name, use a symlink.
Yes, YES. That's what I always tried to say during similar discussions.
In additional to the "default name" (which is, strictly speaking, is NOT
"default" in many cases, such as when you have USB drives connected or
not and all the sdX and srY renumbering, but that's different story, and
many devices are still has "default name"), there's another reason: kernel
should name the devices *somehow*, and it'd better the name exists in /dev.
Think /proc/partitions for example -- I don't damn want to see device numbers
(major+minor) in there, and all the tools searching the whole /dev to find
the device node for it. By the way, lilo breaks if it can't find device
nodes in /dev listed in /proc/partitions, and I can't blame it.
/mjt
prev parent reply other threads:[~2006-11-05 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 10:09 Scsi cdrom naming confusion; sr or scd? andrew
2006-11-05 11:33 ` Jan Engelhardt
2006-11-05 14:00 ` Alistair John Strachan
2006-11-05 14:06 ` Arjan van de Ven
2006-11-05 14:41 ` Oliver Neukum
2006-11-05 16:38 ` Michael Tokarev [this message]
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=454E1370.5020403@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=andrew@walrond.org \
--cc=arjan@infradead.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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