Re: Bug#294206: stat(1) unclear about block size

[Jeroen van Wolffelaar]

On Wed, Feb 09, 2005 at 02:26:12PM -0800, Paul Eggert wrote:
> Jeroen van Wolffelaar <address@hidden> writes:
> > I think it's a bit betrayal to the user to just copy f_bsize if
> > f_frsize is unavailable,
> 
> There's precedent for this in lib/fsusage.c.  As I understand it, it
> doesn't break anything on standard hosts, and it works around some
> incompatibilities in some nonstandard hosts.  If it breaks something
> on other nonstandard hosts then we can look into the problem at that
> point.

Yeah, probably reasonable, after all, I know pretty much only how Debian
linux systems work, and then even i386 only mostly, and really don't
know how this stuff might be elsewhere.
 
> ftp://alpha.gnu.org/gnu/coreutils/coreutils-5.3.0.tar.gz
> 
> applying the stat.c patch, and running "sh configure; make; make check".

(...)
checking for statvfs... yes
checking for sys/mount.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for nfs/nfs_clnt.h... no
checking for nfs/vfs.h... no
checking for struct statfs.f_basetype... no
checking for struct statvfs.f_basetype... no
checking for struct statfs.f_fstypename... no
checking for struct statfs.f_type... yes
checking for struct statvfs.f_type... no
checking for struct statfs.f_fsid.__val... yes
checking for struct statvfs.f_fsid.__val... no
checking for struct statfs.f_namemax... no
checking for struct statvfs.f_namemax... yes
checking for struct statfs.f_namelen... yes
checking for struct statvfs.f_namelen... no
(...)

It builds fine, tests seem to mostly pass, but I didn't encounter a
'stat' test. Running src/stat works fine, and gives the expected results
(4096 for %s and %S, which seems to be correct with the known size of
disks).

--Jeroen

-- 
Jeroen van Wolffelaar
address@hidden (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl