| lists.openwall.net | 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
| ||
|
Message-ID: <4B02D410.4070004@s5r6.in-berlin.de> Date: Tue, 17 Nov 2009 17:49:20 +0100 From: Stefan Richter <stefanr@...6.in-berlin.de> To: "" <jamagallon@....com> CC: Linux-Kernel <linux-kernel@...r.kernel.org> Subject: Re: Out of order kernel messages in sd detection J.A. Magallón wrote: > And, BTW, would sometime the numbering in ataX be made consistent with > SCSI ( ie, ata1 is scsi0....). No. There are several other transports which can register SCSI initiator instances at any time. SAS, USB, 1394, FC, ... Remember: These object numbers don't have any deeper meaning. There is nothing more to them than (a) that they are systemwide unique and (b) persist (only) for the duration of the object's lifetime. Look for persistent and possibly globally unique identifiers (serial numbers) of the actual hardware instead. Udev for example uses them to create useful symlinks to device files. -- Stefan Richter -=====-==--= =-== =---= http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists