| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
current implementation of df(1) is does not properly format the output under
certain conditions. Right now -kP and -Pk are not the same thing. Further,
when we set the BLOCKSIZE environment variable, we use "1k" instead of "1024",
making the header display incorrectly.
To quote the specification:
"When both the -k and -P options are specified, the following header line
shall be written (in the POSIX locale):
"Filesystem 1024-blocks Used Available Capacity Mounted on\n"
- If -P has been specified, check to make sure that -k has not already been
specified, if so, simply break instead of clobbering the previous blocksize
- Use 1024 instead of 1k to make the header POSIX compliant
Reported by: Andriy Gapon
Discussed with: bde, ru
MFC after: 1 week
|
| |
|
|
|
|
| |
- Touch manpage's document date.
|
|
|
|
| |
attempt to enter append mode twice in vi(1). :-)
|
|
|
|
|
|
| |
Bikeshedded to death on: hackers
Submitted by:andersonatcenttech.com
MFC in: 1 month
|
|
|
|
|
|
| |
characters can be included in a custom column title string --
that's why it may appear at the end of a keyword list argument
only.
|
|
|
|
|
| |
data that's alreday 0. In another, it saves us from zeroing data that
will be overwritten again.
|
|
|
|
| |
be safe, memset the entire msg to '0'.
|
|
|
|
|
|
|
|
| |
the header title string "bar" extends to the end of the argument
even if it contains commas or spaces, unlike in RELENG_4 or earlier.
The modern syntax agrees with SUSv3.
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This change affects documentation and comments only,
no real code involved.
PR: misc/101245
Submitted by: Darren Pilgrim <darren pilgrim bitfreak org>
Tested by: md5(1)
MFC after: 1 week
|
|
|
|
|
|
|
| |
when reading a word spanning multiple lines.
PR: bin/101094
MFC after: 5 days
|
|
|
|
| |
extend it with an example to clarify the point.
|
|
|
|
|
|
| |
Acknowledge Kenneth Almquist's contribution in AUTHORS.
MFC after: 5 days
|
|
|
|
|
|
|
|
|
| |
"feature" doesn't seem to be in the standards or elsewhere, and
it is against what we are used to in C and sh(1), so put the
paragraph under BUGS.
Pointed out by: dougb
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
| |
Obtained from: NetBSD, Coverity ID 1754
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Utilities option. Its value is printed at the beginning of the line if tracing
(-x) is active. PS4 defaults to the string "+ " which is compatible with the
old behaviour to always print "+ ".
We still need to expand variables in PS1, PS2 and PS4.
PR: 46441 (part of)
Submitted by: schweikh
Obtained from: NetBSD
|
|
|
|
|
|
|
|
|
|
| |
.//dir as /dir. Rather strip it only for the purpose of checking if the
directory path should be printed.
PR: 88813
Submitted by: Josh Elsasser
Patch from: NetBSD (cd.c rev 1.38)
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
MFC after: 1 week
Approved by: kan (mentor)
|
|
|
|
|
|
|
|
|
| |
next read filename overwrite previous one, resulting in acl being
applied only to the last name in the list.
Submitted by: Oleg Lomaka <oleg.lomaka at gmail com>
MFC after: 1 week
Approved by: kan (mentor)
|
|
|
|
|
|
|
|
|
| |
wording makes it look like pax archives > 32256 bytes are not
POSIX-compliant! Correct this to state that pax archives with
block sizes > 32256 are not POSIX compliant...and settle our fears.
PR: docs/97059
Reviewed by: Giorgos Keramidas <keramida>
|
|
|
|
|
|
| |
sorted. Sort the variables before printing.
PR: 96415
|
|
|
|
|
|
|
|
|
| |
own buffer. Interactively typing in long lines (>1023 characters)
previously overflowed the buffer. Unlike the NetBSD people I don't see the
need to subtract 8 from BUFSIZ, so I just used BUFSIZ-1.
Obtained from: NetBSD
PR: 91110
|
| |
|
| |
|
|
|
|
|
|
| |
PR: bin/95292
Submitted by: Charles Hardin
Obtained from: NetBSD via OpenBSD, PR
|
|
|
|
|
|
| |
I would have chosen the EOF markers, but they are no longer available
AFAICS, so output "<<HERE" and "<<XHERE" instead.
(NOTE: These changes only affect DEBUG output.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
demanded by POSIX.
- A redirection error is only fatal (meaning the execution of a shell script is
terminated) for special built-ins. Previously it was fatal for all shell
builtins, causing problems like the one reported in PR 88845.
- Variable assignments remain in effect for special built-ins.
- Option or operand errors are only fatal for special built-ins.
This change also makes errors from 'fc' non-fatal (I could not find any reasons
for this behaviour).
Somewhat independently from the above down-grade the error handling in the
shift built-in if the operand is bigger than $# from an error() call (which is
now fatal) to a return 1. I'm not sure if this should be considered a POSIX
"operand error", however this change is needed for now as we trigger that error
while building libncurses. Comparing with other shells, zsh does the same as
our sh before this change (write a diagnostic, return 1), bash behaves as our
sh after this commit (no diagnostic, return 1) and ksh93 and NetBSD's sh treat
it as a fatal error.
|
|
|
|
|
|
|
|
|
|
|
| |
all column-headers to print in lowercase by default. I was in too
much of a rush in committing 1.75, and didn't notice that the case
had changed. This time I did considerably more testing, and used
'diff' instead of just quickly eyeballing the results...
Apologies. I expect this means the dunce cap is mine for awhile.
If this doesn't work, I'll just drop back to 1.72 and hide under
my desk for awhile.
|
|
|
|
|
|
|
|
| |
the user specifies a keyword which is an alias to some other keyword.
E.g.: stat (for state) or pcpu (for %cpu)..
Submitted by: Kostik Belousov
MFC plans: "soon"
|
|
|
|
|
|
|
| |
is just ". file" according to POSIX, however many other shells allow
arguments to be passed after the file. For compatibility (we even use that
feature in buildworld) additional arguments are not considered to be an
error, even though this shell does not do anything with the arguments at all.
|
|
|
|
|
|
|
|
| |
new member to struct builtincmd and set it to 1 if -s was specified. This
is done because there are cases where special builtins must be treated
differently from other builtins.
Obtained from: NetBSD (builtins.def part)
|
|
|
|
| |
specified wins to make their interaction less confusing.
|
|
|
|
|
|
|
|
|
| |
flag to use a time other than modtime (-c, -u, or -U), the output would
actually be sorted by the specified time rather than size. This does
alter the behavior in the case where both -S and -t are specified. Now,
-S is always preferred. Previously, -t was preferred if one of -c, -u, or
-U was specified, and -S was preferred otherwise. Perhaps -S and -t should
override each other (last one specified wins).
|
| |
|
|
|
|
|
|
|
| |
sorting.
Submitted by: Andrzej Tobola ato at iem dot pw dot edu dot pl
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
| |
http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
The src.conf(5) manpage is to follow in a few days.
Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
|
|
|
|
|
|
|
| |
comment listing the file name, owner, and group.
MFC after: 1 week
Submitted by: Jan Srzednicki <w at expro dot pl>
|
|
|
|
|
|
| |
mdoc(7) according to ru.
Requested by: ru
|
|
|
|
|
|
| |
by pjd.
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
| |
output-format keyword, and the keyword they picked is an alias to
some other keyword. E.g.: ps -o stat=Zustand $$
('stat' is defined as an alias for 'state')
PR: bin/57833
MFC after: 3 weeks
|
|
|
|
| |
Discussed with: ru
|
|
|
|
|
|
| |
Mention that the setting of securelevel may affect one's ability to alter flags.
Xref security.7.
Bump doc date.
|
|
|
|
|
|
| |
up always printing "pts".
Submitted by: Michal Mertl <mime at traveller dot cz>
|