Age | Commit message (Collapse) | Author |
|
Both have the same meaning, but the former is explicitly defined
in this manual page as "the next line" whereas the latter requires
combining various pieces of information for understanding.
Unification suggested and patch OK'ed by martijn@.
|
|
Instead, link to the explanation of octal permission masks in chmod(2)
directly from the description of "umask", and to ksh(1) from SEE ALSO.
Fixing an oddity pointed out by guenther@; OK jmc@ millert@.
|
|
OK guenther@
|
|
OK deraadt@
|
|
fact on the ground in ps everywhere, even on linux, and it is not going
to go away, and denying the existance is pointless. The SYNOPSIS cannot
proscriptively document all the cases without a madness. I also feel
there is very little need to explain the behaviour differences relative
to the sparse POSIX standard for ps, everyone's ps has oodles of
extensions.
|
|
Spotted by maya@netbsd
ok deraadt@
|
|
implementation; it was oversimplified and arguably incorrect.
2. Explicitely compare the behaviour of empty command lists for g,
empty command lists for G, and empty commands because these subtle
differences are quite confusing.
3. Say more precisely what the v and V commands do, avoiding the
fuzzy wording "similar".
All these issues were first pointed out by martijn@.
Feedback and OK martijn@; "diff reads ok" jmc@ on an earlier version.
|
|
the g and G commands, and polish the wording a bit explaining empty
command lists.
Closing a gap in the manual reported by <mazocomp at disroot dot org>.
OK jmc@ martijn@
|
|
* Delete a stray blank from the command line synopsis
and add the missing .Ar markup to it.
* Do not mention the terminating newline for the empty command
since it isn't mentioned for any other command either.
* Make the description of the empty command easier to understand.
Joint work with martijn@ and jmc@.
|
|
thread started by mazocomp; diff from ropers, shortened by me;
ok martijn schwarze
|
|
|
|
- No need for intermediate variables, just build the timespec directly
- Use for-loops so we modify "cp" on a single line in each loop
- Parse subseconds with one loop: less code, easier to read, etc.
- Improve the subsecond parsing comment: make our intent really obvious
ok schwarze@
|
|
|
|
value < 0. errno is only updated in this case. Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
|
|
|
|
ok millert nicm tb, etc
|
|
EOF in case of errors, not any negative number.
EOF corner case spotted while reviewing a much bigger diff by deraadt
OK deraadt, millert
|
|
|
|
Reference the First Edition (1989) of Bolsky/Korn which is about ksh88,
the shell the OpenBSD ksh(1) descends from (via pdksh).
The Second Edition (1995) of the book is about ksh93 which we don't provide.
Pointed out by Andras Farkas on bugs@.
|
|
not arbitrary values < 0.
|
|
|
|
active on each process. So go forth and "ps agux -o pledge" to find pledges
which can be improved.
(I hesitated adding this before because I am afraid of people
enforcing extra-strict pledge in programs without testing all the use
cases -- thereby breaking software).
|
|
you'll see one, or neither.
'u' - process installed unveils, but not yet locked with unveil(0,0)
or pledge w/o "unveil"
'U' - process has installed unveils, and locked.
ok rob
|
|
|
|
Previously they were only recognized in [[ ... ]] expressions. This
changes sh/ksh to be consistent with test(1) as well as shells like
bash and dash. OK jca@ jmc@
|
|
Most of these are correct just as '. A few benefit from Ql or \(aq.
But if in doubt, just use '.
|
|
omission reported by Rudolf Sykora <rsykora at disroot dot org> on misc@;
tweak and OK jmc@
|
|
ok millert@
|
|
Slightly more useful for some, same defaults as bash.
No objection deraadt@ phessler@, ok tb@ kn@ benno@
|
|
|
|
could have, so let's formally expand the buffer to what it needs to be.
|
|
never do substitution (neither parameter, nor command, nor arithmetic,
nor tilde substitution) on the values of any variables encountered
inside the expression, but do recursively perform arithmetical
evaluation of subexpressions as required. This makes behaviour
more consistent, without hindering any behaviour promised in the
manual page.
A quirk originally reported by Andy Chu <andychup at gmail dot com>
was that in the past, when encountering an array index, the shell
would not only do evaluation, but also substitution on the array
index, even though substitution would not be done on the expression
in general.
tobias@ contributed to initial efforts of understanding the quirk.
patch tested in a bulk build by naddy@
"please commit" deraadt@
|
|
|
|
final write to output. GNU dd also has this. It is useful for
write performance measurement or guaranteed writes to reliable
storage.
OK kn@ tedu@ deraadt@
|
|
larger types really is a range reduction...
Almost any cast to (unsigned) is a bug.
ok millert tb benno
|
|
Give the same treatment if /dev doesn't exist. While things will be
real interesting without /dev there is no reason to stop ps(1).
Fix suggested by & OK deraadt
OK millert
|
|
decomposition into major and minor is unsigned, so we should print them
with %u instead of %d.
ok guenther
|
|
Not standard, but supported at least by GNU cp, IllumOS, NetBSD,
FreeBSD, DragonflyBSD. No need to be gratuitously different. This
should also allow us to drop patches in ~10 ports.
Based on an initial diff by benno@ with input from sthen@ and jmc@
ok benno@ danj@ sthen@ martijn@ deraadt@
|
|
|
|
diff from Oscar Endre Edvardsen via misc@ a long time ago.
ok sthen@ dlg@
|
|
|
|
|
|
1. Another off-by-one: if a mail file name ends in an (escaped)
percent sign, do not forget to check whether the next byte is the
percent sign introducing the message (MAILPATH='filename\%%msg').
2. If the message is empty, use the default message rather than
printing a blank line (MAILPATH='filename%').
3. If the file name is empty, don't bother with mballoc(): the
subsequent stat(2) can never succeed. (MAILPATH='%msg').
Found while reviewing the previous commit by tedu@.
OK tedu@.
|
|
ok deraadt schwarze tb
|
|
Now that nanosleep(2) handles the full input range transparently there
is no longer a 100 million second upper bound and we can remove this loop.
ok phessler@ jca@ visa@
|
|
|
|
ok deraadt@
|
|
in "for name in [word ...]; do list; done" can be empty.
In sh(1), clarify what happens in that case.
In ksh(1), clarify how it can happen that the list is never executed.
OK jmc@ tb@
|
|
While the code intended to support both -s NAME and -s SIGNAME, the
tests performed were wrong. Replace convoluted code with less cryptic
conditionals. ok anton@
|
|
and a normal hyphen as "-" rather than "\-"
|