| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
| |
Giulio Eulisse reported that on OSX, bad free space numbers were being
shown. It thought he had negative free space.
While the documentation is not clear, especially across OS's, it seems
likely that statfs uses unsigned long. It doesn't make sense for any
numbers to be negative.
|
|
|
|
|
|
| |
Tested on Debian kfreebsd-amd64. The BSD #includes worked. Both statfs64
and statfs worked. Using statfs to keep the same as general freebsd, and
because I didn't try it on 32 bit.
|
|
|
|
|
|
| |
http://git-annex.branchable.com/bugs/Makefile_is_missing_dependancies/#comment-3196b43b7d745ab206435d0a69686815
indicates statfs64 works on apple. Probably on freebsd too, but I
have not tested it and so will stick with the old code there.
|
|
|
|
|
|
| |
This reverts commit 4440ecf4a74b85341d5ecc1ecb1a9349b6fc5d3b.
Turns out that it is reporting a block size of 0 and so all bogus.
|
|
|
|
|
|
| |
At least on OSX 10.6.6 it appears to have the same defintions as
FreeBSD. The build process doesn't complain and the code is enabled,
this needs to be tested and checked more.
|
|
|
|
|
|
|
|
| |
Todo later: use POSIX statvfs
Note: Re OSX, see http://code.google.com/p/xmobar/issues/detail?id=28
Apparently xmobar's code will work on OSX, probably __FreeBSD__ is defined
there.
|
|
|