Paul Eggert [EMAIL PROTECTED] wrote:
OK, thanks, here's a proposed patch to implement BSD-like behavior for
coreutils and BLOCKSIZE. (The hard part is the documentation :-).
2004-02-25 Paul Eggert [EMAIL PROTECTED]
* NEWS: New environment var BLOCKSIZE.
* doc/coreutils.texi
In message [EMAIL PROTECTED], Paul Eggert writes:
[EMAIL PROTECTED] (Peter Seebach) writes:
BLOCKSIZEThe size of the block units used by several commands,
most notably df(1), du(1) and ls(1).
Can you find a complete list of BSD programs that use getbsize,
and
In message [EMAIL PROTECTED], Paul Eggert writes:
As the 1998 change caused the environment variable to have the same
interpretation as the --block-size long option, I thought it more
consistent at the time to spell the environment variable BLOCK_SIZE
rather than BLOCKSIZE.
Makes sense.
It
[EMAIL PROTECTED] (Peter Seebach) writes:
BLOCKSIZEThe size of the block units used by several commands,
most notably df(1), du(1) and ls(1).
Can you find a complete list of BSD programs that use getbsize,
and which contexts they use it in?
Here's why I'd
In message [EMAIL PROTECTED], Jim Meyering writes:
[EMAIL PROTECTED] (Peter Seebach) wrote:
...
This seems wrong. The user setting $BLOCKSIZE presumably intends it to
If you spell it `BLOCK_SIZE', then it should work.
Hmm. When did this spelling change? In old man pages
[EMAIL PROTECTED] (Peter Seebach) wrote:
...
This seems wrong. The user setting $BLOCKSIZE presumably intends it to
If you spell it `BLOCK_SIZE', then it should work.
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
