[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Possible bug in 'df' v5.2.1 (--portability switch)
From: |
Torkel Bjørnson |
Subject: |
Possible bug in 'df' v5.2.1 (--portability switch) |
Date: |
Mon, 06 Sep 2004 20:02:30 +0200 |
User-agent: |
Mozilla Thunderbird 0.6+ (X11/20040811) |
Hello!
I would like to report a bug in the df program in the
GNU coreutils package.
Here is a proof by example:
$ df --version
df (coreutils) 5.2.1
$ df --portability /
Filesystem 512-blocks Used Available Capacity Mounted on
/dev/sda1 361278 225408 116596 66% /
$ setenv BLOCK_SIZE human-readable
$ df --portability /
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 177M 111M 57M 66% /
I think the last output is wrong. Since I request an output
format in compability/POSIX mode, it should ignore the
BLOCK_SIZE environment variable and display the blocksize
in whatever blocksize POSIX define.
Another thing I noticed in the info page for 'df'
`POSIXLY_CORRECT'
If neither the `COMMAND_BLOCK_SIZE' nor the `BLOCK_SIZE' variables
are set, but this variable is set, the block size defaults to 512.
Shouldn't the semantic be that when POSIXLY_CORRECT is set, this should
override conflicting switches and/or other env. var. and make all supported
programs behave correctly according to the POSIX standard?
Just my taught on the subject.
Thank you very much for making GREAT software to the world!!!
Best regards,
Torkel Bjørnson
--
I would rather say that a desire to drive fast sports cars is what sets man
apart from the animals.
- Possible bug in 'df' v5.2.1 (--portability switch),
Torkel Bjørnson <=