| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
since it has been fixed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is a style bug at best. When the variable isn't a flag, it potentially
overflows after a large number of settings. Here the number of settings
is limited by ARG_MAX, but the variable is the exit code so it became
bogus after the second setting and effectively overflowed to 0 after
approx. 128 settings.
Fixed some style bugs involving comments in and near previous commit.
Clarification of previous commit message: df -t didn't give undefined
behaviour, and the behaviour used to conform perfectly with the man
page, since the buggy behaviour is documented in the BUGS section. -t
just worked when no files or file systems were specified, and was just
ignored if a file or file system was specified.
|
|
|
|
|
|
|
|
|
|
| |
-t Only print out statistics for filesystems of the specified types.
Make the behavior of df(1) conform to its man page (behavior is otherwise
undefined).
Submitted by: Rob Braun <bbraun@apple.com>
Obtained from: Apple
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
output buffer, don't insert them at all. This prevents a buffer
*underrun* when the substitution consists completely of newlines
(e.g. `echo`) and the byte before the source buffer to which p
points is a '\n', in which case more characters would be removed
from the output buffer than were inserted.
This fixes certain port builds on sparc64.
Approved by: re (scottl)
Reviewed by: des, tjr
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
| |
Approved by: re (scottl)
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
| |
Approved by: re@ (bmah)
MFC after: 3 days
|
|
|
|
|
| |
PR: 35523
Submitted by: Tomas Svensson <tsn@gbdev.net>
|
|
|
|
| |
Submitted by: Tim Kientzle <kientzle@acm.org> (embellished by me)
|
|
|
|
| |
Tested by: Joe Marcus Clarke <marcus@marcuscom.com>
|
|
|
|
| |
explanation of `collating elements'.
|
|
|
|
|
|
| |
WARNS=6, std=c99 clean.
Tested on: i386, alpha
|
|
|
|
|
| |
solicits a warning when used for the '*' in printf("%*d"). Cast
to u_int for universal use.
|
|
|
|
| |
and lint. This is now WARNS=9, std=c99 clean on i386.
|
| |
|
|
|
|
|
| |
Use return(0) for main() instead of exit(0). Makes it a
wee bit smaller.
|
|
|
|
| |
sized/unsigned comparisons.
|
| |
|
|
|
|
|
|
| |
Due to the use of signed vs. unsigned chars on our various platforms, one gets
"warning: comparison is always true due to limited range of data type"
from GCC 3.3.
|
|
|
|
| |
to properly fix.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
PR: docs/51480 (only a small part)
Submitted by: Diomidis D. Spinellis <dds@aueb.gr>
|
| |
|
|
|
|
|
|
|
| |
scripts parsing ls(1) output can still count columns.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| |
|
|
|
|
|
|
| |
zombie CPU times are valid. Adjust array size in strftime(3).
Submitted by: Bruce
|
|
|
|
|
| |
<sys/param.h>. Include <sys/types.h> instead of of <sys/param.h>
so that further such dependencies don't develop.
|
| |
|
|
|
|
|
|
|
| |
This is what the manual page says ps should do, and what OpenBSD and NetBSD do.
Based on a patch from Ken Stailey.
PR: 27433, 46232
|
|
|
|
| |
traditional BSD behaviour (-n option) and FreeBSD extensions (\c).
|
| |
|
|
|
|
|
|
| |
mutually exclusive. The fact that the most recent one specified on the
command line is the one that takes effect is an implementation detail and
users should not rely on this.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
the nodump flag.
PR: 46912
Reported by: dave@syix.com <dave@syix.com>
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
| |
the child process writing data that the parent should have written.
PR: 50051
MFC after: 2 weeks
|
|
|
|
|
|
| |
specs, so cast to intmax_t where appropriate.
Pointed out by: bde
|
| |
|
|
|
|
|
|
|
| |
This option is present on most uuidgen(1) implementations even
though normal file redirection can be used to achieve the same.
Submitted by: Hiten Pandya <hiten@unixdaemons.com>
|
|
|
|
|
|
| |
-ansi, due to 'long long'.
Reviewed by: green (slightly earlier version)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initial stack_block is staticly allocated and will be aligned
according to the alignment requirements of pointers, which does not
necessarily match the alignment enforced by ALIGN. To solve this a
more involved change is required: remove the static initial stack
and deal with an initial condition of not having a stack at all. This
change is therefore more risky than the previous ones, but unavoidable
(other than not using the platform default alignment).
Discussed with: tjr
Approved and reviewed by: tjr
Tested on: alpha, i386, ia64 and sparc64
|
| |
|