Greg KH wrote:
[]
> From: Kay Sievers <[EMAIL PROTECTED]>
> Subject: Driver core: convert block from raw kobjects to core devices
>
> This moves the block devices to /sys/class/block. It will create a
> flat list of all block devices, with the disks and partitions in one
> directory. For compatibility /sys/block is created and contains symlinks
> to the disks.
What's the proper way now to figure out which device type it is --
block or char?
Before, I had a function (in my udev-alike userspace app), something akin
sysfs_scan_devices(char *topdir, mode_t type), and called it twice --
sysfs_scan_devices("/block", S_IFBLK);
sysfs_scan_devices("/devices", S_IFCHR);
How it's supposed to work now? (Note that it skips symlinks for obvious
reason, hence it can't find anything in /sys/block, even with the compat
"layer" in place)
(Not complaining, but asking instead)
Thanks.
/mjt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
