Update of bug #45780 (project findutils):
Assigned to: None => jay
_______________________________________________________
Follow-up Comment #5:
I just made an implementation of my suggestion in #3 and I'm not sure I like
it because the resulting field is very wide and mostly blank. On my
development system this results in a 20-character field for the inode number
(since, I assume, ino_t is a 64-bit type).
I agree though that a filesystem which supports only a million files would be
small by today's standards.
It's tempting to use statfs to examine the filesystem and use statfs.f_files
but this only tells us the maximum number of files - the inodes may not be
allocated in any particular way (e.g. not contiguously).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?45780>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
