| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Approved by: jkh
|
|
|
|
|
| |
PR: 18465
Reported by: Kazu TAKAMUNE <takamune@avrl.mei.co.jp>
|
|
|
|
|
|
|
| |
cases and broke the world in some cases.
Fixed some style bugs (the usual ones for DPADD and LDADD, misplacement
of DPADD and LDADD, and misplacement of $FreeBSD$).
|
|
|
|
|
|
|
|
|
|
| |
Obtained from: parts of human readable code from OpenBSD
Reviewed by: obrien
add POSIX, byte and megabyte block size ouput flags
PR: 13579 (POSIX flag)
Submitted by: Mike Meyer <mwm@phone.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
be ignored by default by the df(1) program. This is used mostly to
avoid stat()-ing entries that do not represent "real" disk mount
points (such as those made by an automounter such as amd.) It is
also useful not to have to stat() these entries because it takes
longer to report them that for other file systems, being that these
mount points are served by a user-level file server and resulting in
several context switches. Worse, if the automounter is down
unexpectedly, a causal df(1) will hang in an interruptible way.
PR: kern/9764
Submitted by: Erez Zadok <ezk@cs.columbia.edu>
|
| |
|
|
|
|
|
|
| |
are available; suggest lsvfs(1) instead.
Reported by: Neil Blakey-Milner <nbm@rucus.ru.ac.za>
|
| |
|
|
|
|
| |
use mkdtemp() rather than mktemp() and fix a trivial memory leak.
|
|
|
|
|
|
| |
PR: 6599
Reviewed by: phk
Submitted by: Josh Gilliam <josh@quick.net>
|
| |
|
|
|
|
| |
the default.
|
|
|
|
|
|
| |
pointless paren's to return statements.
Nitpicked by: bde :)
|
|
|
|
| |
PR: bin/4415
|
| |
|
|
|
|
| |
sccsid -> rcsid.
|
|
|
|
| |
posix standard on the topic.
|
|
|
|
| |
change should be that the usage message now actually matches the man page.
|
|
|
|
|
|
| |
vfs types.
Fixed ordering of FreeBSD `k' option in synopsis.
|
| |
|
|
|
|
| |
for root only.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Obtained from: A Quarter Century of UNIX, Peter H. Salus, page 41
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Reviewed by: phk
|
|
|
|
|
|
|
|
|
| |
/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)
|
| |
|
|
|
|
|
|
| |
so the BLOCKSIZE doesn't need to be preserved.
Also initialized the flags variables, and used 1k instead of 1024 for
BLOCKSIZE.
|
|
|
|
| |
of the BLOCKSIZE environment variable.
|
|
|
|
| |
Also document `-t' option in the usage message.
|
|
|