From: Arjan van de Ven <arjan@infradead.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: andrew@walrond.org, linux-kernel@vger.kernel.org
Subject: Re: Scsi cdrom naming confusion; sr or scd?
Date: Sun, 05 Nov 2006 15:06:39 +0100 [thread overview]
Message-ID: <1162735599.3160.91.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0611051232580.12727@yvahk01.tjqt.qr>
On Sun, 2006-11-05 at 12:33 +0100, Jan Engelhardt wrote:
> > "The prefix /dev/sr (instead of /dev/scd) has been deprecated"
> >
> >but booting 2.6.18.2 from a scsi CD only works if I pass the kernel
> >parameter root=/dev/sr0 and fails with root=/dev/scd0
> >
> >I guess the kernel ought to be taught about the scd* names aswell?
>
> brw-r----- 1 root disk 11, 0 Mar 19 2005 /dev/scd0
> brw-r----- 1 root disk 11, 0 Mar 19 2005 /dev/sr0
>
> Plus I see sr0 being far more commonly used than scd0.
> So I guess the doc is wrong.
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 know for root= it currently has to if you don't have an initrd but..
well... that's sort of a nasty interface anyway; what if you have a usb
cdrom drive connected for example.. suddenly all your names changed)
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-11-05 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 10:09 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 [this message]
2006-11-05 14:41 ` Oliver Neukum
2006-11-05 16:38 ` Michael Tokarev
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=1162735599.3160.91.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=andrew@walrond.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®