src/bin/df, branch release/2.2.5_cvs

This commit was manufactured by cvs2svn to create tag

1997-10-21T01:56:05Z

'RELENG_2_2_5_RELEASE'. This commit was manufactured to restore the state of the 2.2.5-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

environmental -> environment

1997-09-19T06:18:21Z

YAMFC

1996-12-13T17:15:11Z

[HISTORY] command appeared in Version 1 AT&T UNIX

1996-08-29T18:06:19Z

Obtained from: A Quarter Century of UNIX, Peter H. Salus, page 41

Partially fixed negative and truncated "Avail" counts in df output.

1996-01-14T18:55:09Z

This fixes PR943. ffs/ffs_vfsops.c: ffs_statfs() multiplied by (100 - minfree) as part of calculating the minfree percentage (complemented in 100%), so with the standard minfree of 8, it was broken for file systems of size >= 1TB/92 = 11GB. Use the standard freespace() macro instead. This also fixes a rounding bug (the "Avail" count was sometimes 1 too small). ffs/* (not fixed): The freespace() macro multiplies by minfree, so with the standard minfree of 8, it is broken for file systems of size >= 1TB/8 = 128GB. This bug is more serious since it affects block allocation. ffs/ffs_alloc.c (not fixed): Ordinary users are sometimes allowed to allocate 1 (partial) block too many so that the "Avail" count goes negative. E.g., if there is 1 fragment available and the file is fairly large, one more full block is allocated. df/df.c: ufs_df() used/uses essentially the same code as ffs_statfs(), so it had/has the same bugs. ufs_df() gratuitously replaced "Avail" counts of < 0 by 0, so it gave different results for non-mounted file systems in this case.

Remove trailing whitespace.

1995-05-30T00:07:29Z

Reviewed by: phk

You will find enclosed some changes to make gcc -Wall more happy in

1995-03-19T13:29:28Z

/usr/src/bin. Note that some patches are still needed in that directory. I (Joerg) finished most of Philippe's cleanup. /bin/sh will still need *allot* of work, however. Submitted by: charnier@lirmm.fr (Philippe Charnier)

Added $Id$

1994-09-24T02:59:15Z

The last commit was bogus...the putenv doesn't affect the parent process,

1994-08-12T10:23:49Z

so the BLOCKSIZE doesn't need to be preserved. Also initialized the flags variables, and used 1k instead of 1024 for BLOCKSIZE.

Implemented the -k flag more properly...don't destroy the user's setting

1994-08-12T07:26:52Z

of the BLOCKSIZE environment variable.