summaryrefslogtreecommitdiffstats
path: root/bin/df
Commit message (Collapse)AuthorAgeFilesLines
* Style police: keep a variable list in alphabetical order, and addjoerg1997-10-131-5/+5
| | | | | | pointless paren's to return statements. Nitpicked by: bde :)
* Make df(1) exit with non-success status if something went wrong.joerg1997-10-121-11/+18
| | | | PR: bin/4415
* environmental -> environment.charnier1997-09-181-2/+2
|
* Add Bruce's _NEW_VFSCONF flag to make this compile cleanly andsteve1997-08-072-6/+9
| | | | sccsid -> rcsid.
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-281-2/+2
| | | | posix standard on the topic.
* Merged from Lite2. The -t option is now handled better. The only visiblebde1997-03-131-104/+37
| | | | change should be that the usage message now actually matches the man page.
* Merged from Lite2. The man page no longer attempts to list all thebde1997-03-131-21/+28
| | | | | | vfs types. Fixed ordering of FreeBSD `k' option in synopsis.
* Merge from Lite2. Straightforward changes.bde1997-03-131-2/+7
|
* This is a funny one: df for a device that was not mounted used to failguido1997-03-101-2/+2
| | | | for root only.
* Revert $FreeBSD$ to $Id$peter1997-02-223-3/+3
|
* Include <ufs/ufs/ufsmount.h>.jkh1997-02-171-0/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-143-3/+3
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Sort cross references.wosch1997-01-131-2/+2
|
* Merge Lite2 mods, cleanup man page, and -Wall cleaning.steve1996-12-142-9/+9
|
* The manual page of df called cd9660 file systems by the namejkh1996-12-112-4/+9
| | | | | | | | | | | isofs while the df command itself used the name iso9660fs or cdfs. Both of these were inconsistent with the name cd9660 which is used by the mount command. I modified df to recognize all of the names cd9660, cdfs, isofs, and iso9660fs, and take them all to refer to the same thing. Naturally I added a note of this behaviour in the manual page too. Submitted-By: Jukka Ukkonen <jau@jau.csc.fi>
* [HISTORY] command appeared in Version 1 AT&T UNIXwosch1996-08-291-2/+2
| | | | Obtained from: A Quarter Century of UNIX, Peter H. Salus, page 41
* Partially fixed negative and truncated "Avail" counts in df output.bde1996-01-141-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.rgrimes1995-05-301-4/+4
| | | | Reviewed by: phk
* You will find enclosed some changes to make gcc -Wall more happy injoerg1995-03-191-21/+23
| | | | | | | | | /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$dg1994-09-243-0/+4
|
* The last commit was bogus...the putenv doesn't affect the parent process,dg1994-08-121-10/+3
| | | | | | 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 settingdg1994-08-121-2/+11
| | | | of the BLOCKSIZE environment variable.
* Gimme back my `-k' option!wollman1994-08-102-3/+12
| | | | Also document `-t' option in the usage message.
* BSD 4.4 Lite bin Sourcesrgrimes1994-05-263-0/+543
OpenPOWER on IntegriCloud