Re: fs_info struct

"Jonas Sundström" <[email protected]> wrote:
> In 'df', for BFS images the filename is listed as Device. It would be 
> great having the entire path, if it wasn't for the 128 byte limit of 
> the device_name member of the fs_info struct. 

BeOS doesn't know which image a file system is using. "df" just shows 
whatever was specified in the "mount" application. Haiku does not 
suffer from this restriction, though, as the mount process in done 
differently.
I don't know yet, what we'll do about the 128 byte limit - at least, 
you definitely can use the new disk device API to get to this 
information.

> 128 bytes may be enough for the regular volumes, like /boot, which 
> only 
> lists its /dev/disk/ide/..., but how about future USB and Firewire 
> disk 
> /dev entries?

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? :-)

Bye,
   Axel.



-------------------------------------------------------
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