(CFACT-131) Fix block size calculation for mountpoints fact.

Currently the optimal transfer block size member (f_bsize) was
being used in size calculations instead of the fragment
size member (f_frsize) on Linux and Solaris.

The fix is to use f_frsize instead of f_bsize where appropriate.

Additionally, the Solaris mountpoints fact was not correctly being
populated because it copied a restriction coming from the Linux
implementation.  It was also using a 32-bit version of statvfs,
preventing large file systems from properly reporting their sizes.  The
statvfs64 function should be used instead.

Note: on BSD, the statfs struct has f_bsize as the block size,
as anyone sane would expect.
I don't think we need to worry about a kernel older than 2.6.  FC5 is ancient and it's 2.6+.

I wonder if we should be explicitly calling statfs64 here rather than relying on glibc to "transparently" make statfs 64-bit compatible (also added in 2.6).