Re: fs_info struct

"Axel Dörfler" <[email protected]> wrote:
 ...
> Even if we change the limit, I don't think that the 
> device names will get much longer. Why should
> a firewire disk need a longer filename than 
> an IDE disk? What kind of names are you imaging? :-)

Stuff like this, but longer. ;)
/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1

Or multiple levels of GUID-looking gibberish, 
but perhaps the /dev future isn't as bad as I thought.

The Linux udev introduction flashed a few horrible looking /dev paths, 
probably to sell people on the "user friendly" dev symlink feature, 
("persistent device names"), which I never really got the usefulness 
of. I'd much rather use an API similar to that of BVolumeRoster (for 
all classes of devices) than do manual lookups in /dev. I don't mind if 
/dev paths change as long as the API lets me track which printer is 
which, which USB flash device is which, etc.

Possibly quite irrelevant links:
http://www.ussg.iu.edu/hypermail/linux/kernel/0401.3/0574.html
http://kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ

/Jonas Sundström.                 www.kirilla.com










-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl