Re: coreutils-6.0 on BeOS (9)

[Jim Meyering]

Hi Bruno,

Thanks for all of your recent BeOS porting work.
We've received very few reports about BeOS problems, other than yours.
I'm curious: what's your motivation for using it?

Bruno Haible <address@hidden> wrote:
...
> After producing this patch, I noticed that the replacement 'statfs' that I
> put into stat.c would also be useful for "df -i" (because the f_files, f_ffree
> numbers in 'struct statvfs' are only dummies whereas those in 'struct fs_info'
> are real ones).
>
> So, more unification between lib/fsusage.c and src/stat.c seems desirable.
> I propose to create a 'struct gnu_statvfs' that contains the usual POSIX
> fields plus 'char f_fstypename[]', containing the filesystem name, and a few
> minor fields that src/stat.c uses, and to transform the lib/fsusage.c code
> into a gnu_statvfs function that could be used by both "df" and "stat".
> Does this seem worthwhile?

Yes, it does.

> Can the SVR2 code (this is the only code in
> lib/fsusage.c that makes use of the 'disk' argument) be dropped in the 
> process?

I suspect it is dead, but not knowing, it'd be prudent
to add a configure-time AC_MSG_FAILURE message like the
one in ftruncate.m4.