lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 05 Nov 2006 15:06:39 +0100
From:	Arjan van de Ven <>
To:	Jan Engelhardt <>
Subject: Re: Scsi cdrom naming confusion; sr or scd?

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 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)
Test the interaction between Linux and your BIOS via

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists