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
| ||
|
Date: Sat, 19 Aug 2006 02:15:23 +0200 From: Gabor Gombas <gombasg@...aki.hu> To: Bill Davidsen <davidsen@....com> Cc: Seewer Philippe <philippe.seewer@....ch>, Jeff Garzik <jeff@...zik.org>, Adrian Bunk <bunk@...sta.de>, Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org Subject: Re: /dev/sd* On Fri, Aug 18, 2006 at 08:45:38AM -0400, Bill Davidsen wrote: > For discussion I suggest /proc/ata/devices, a single flat file matching > a name meaningful to open() with a vendor string and whatever other info > is handy, like serial number and the like. Why just ATA? Let it contain all disk-like devices in the system, and add an extra field showing the transport method (IDE/USB/SCSI/SATA/whatever) the device is currently using. Hmm, /sys/block already contains all the kernel-internal device names, /sys/block/*/device already gives the physical location. We might just need a couple additional attributes (like "serial") for user convenience, and a little shell script that walks /sys/block and emits an unified device list? Alternatively, the shell scipt could use blktool to collect the data not already present under /sys/block, so there would be no need to modify the kernel at all. blktool could be modified to accept a path name under /sys/block as well as a device node, and print some more data the serial number when using the "id" command, but I think that's doable. Gabor -- --------------------------------------------------------- MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences --------------------------------------------------------- - 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