On Tue, Feb 08, 2005 at 05:19:37PM -0500, Michael Stone wrote:
> On Tue, Feb 08, 2005 at 01:56:00PM -0800, Paul Eggert wrote:
> >OK, thanks, I installed this (revised) patch into coreutils, which I
> >hope addresses that problem.
>
> No, if you're going to use the statvfs block size you need to pu
On Tue, Feb 08, 2005 at 01:56:00PM -0800, Paul Eggert wrote:
OK, thanks, I installed this (revised) patch into coreutils, which I
hope addresses that problem.
No, if you're going to use the statvfs block size you need to pull the
other numbers from statvfs also. IOW, just add another flag (-F?) to
Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes:
> On Tue, Feb 08, 2005 at 05:43:08PM +0100, Jim Meyering wrote:
>> Does stat's --file-system (-f) option do what you want?
>>
>> $ stat -f /
>> File: "/"
>> ID: 0Namelen: 255 Type: ext2/ext3
>> Blocks: Total: 1032
Hum ... that probably may disorganise my portage tree. Unfortunately
version 5.3.0 isn't even available marked "testing" in the protage tree...
Maybe they'll put it in citeing you and asking for it.
May I cite you at the gentoo bug site?
Anyway, thank you for the fast reply.
~ Attila
Paul Eggert
Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes:
> See http://bugs.debian.org/294206#msg17 for more information, bottom
> line is that statvfs returns a superset of values compared to statfs,
> and one of the extra values is f_frsize required for getting the free
> disk space in bytes.
O
Attila <[EMAIL PROTECTED]> writes:
> I don't know which output you need.
> I added some to the gentoo bug site
> http://bugs.gentoo.org/show_bug.cgi?id=80908#c6 .
> Hopefully that helps - if not, please tell me what to look for.
Thanks; apparently the chgrp/posix-H test failed. This test has bee
On Tue, Feb 08, 2005 at 05:43:08PM +0100, Jim Meyering wrote:
> Does stat's --file-system (-f) option do what you want?
>
> $ stat -f /
> File: "/"
> ID: 0Namelen: 255 Type: ext2/ext3
> Blocks: Total: 1032080Free: 887328 Available: 834894 Size:
> 4096
On Tue, Feb 08, 2005 at 11:22:24AM -0500, Michael Stone wrote:
> On Tue, Feb 08, 2005 at 03:39:05PM +, James Youngman wrote:
> >No.The POSIX standard (in a non-normative section) says :-
> >
> >| The unit for the st_blocks member of the stat structure is not defined
> >| within IEEE Std 100
Jeroen van Wolffelaar <[EMAIL PROTECTED]> wrote:
> I've done a bit more reading and googling, and I found statvfs(2):
>
> struct statvfs {
>unsigned long f_bsize;/* file system block size */
>unsigned long f_frsize; /* fragment size */
>fsblkcnt_
On Tue, Feb 08, 2005 at 03:39:05PM +, James Youngman wrote:
No.The POSIX standard (in a non-normative section) says :-
| The unit for the st_blocks member of the stat structure is not defined
| within IEEE Std 1003.1-2001. In some implementations it is 512
| bytes. It may differ on a file s
On Tue, Feb 08, 2005 at 03:39:05PM +, James Youngman wrote:
> No.The POSIX standard (in a non-normative section) says :-
>
> | The unit for the st_blocks member of the stat structure is not defined
> | within IEEE Std 1003.1-2001. In some implementations it is 512
> | bytes. It may differ
On Tue, Feb 08, 2005 at 03:39:05PM +, James Youngman wrote:
> On Tue, Feb 08, 2005 at 02:42:09PM +0100, Jeroen van Wolffelaar wrote:
> > Package: coreutils
> > Version: 5.2.1-2
> >
> > %s Optimal transfer block size
> > $
> >
> > 'Optimal transfer block size', I have the suspection that %
On Tue, Feb 08, 2005 at 02:42:09PM +0100, Jeroen van Wolffelaar wrote:
> Package: coreutils
> Version: 5.2.1-2
>
> %s Optimal transfer block size
> $
>
> 'Optimal transfer block size', I have the suspection that %s IS the
> blocksize of the filesystem, which should be used in a number of othe
Package: coreutils
Version: 5.2.1-2
I'm looking into using stat for determining available diskspace,
however, this proves difficult or badly documented.
$ stat --help
(...)
Valid format sequences for file systems:
%a Free blocks available to non-superuser
(...)
%s Optimal transfer block s
14 matches
Mail list logo
