| Age | Commit message (Collapse) | Author |
|---|
|
the POSIX-standard st_*tim members.
ok millert@
|
|
|
|
ok miod@ millert@
|
|
ok claudio@ cheloha@ krw@ deraadt@ miod@ millert@
|
|
part of a larger diff: i'm committing this separately
as i changed statuses to status;
|
|
getopt(3) returns '?' when it encounters a flag not present in the in
the optstring or if a flag is missing its option argument. We can
handle this case with the "default" failure case with no loss of
legibility. Hence, remove all the redundant "case '?':" lines.
Prompted by dlg@. With help from dlg@ and millert@.
Link: https://marc.info/?l=openbsd-tech&m=167011979726449&w=2
ok naddy@ millert@ dlg@
|
|
jmc@ dislikes a comma before "then" in a conditional, so leave those
untouched.
ok jmc@
|
|
3rd (variadic) mode_t parameter is irrelevant. Many developers in the past
have passed mode_t (0, 044, 0644, or such), which might lead future people
to copy this broken idiom, and perhaps even believe this parameter has some
meaning or implication or application. Delete them all.
This comes out of a conversation where tb@ noticed that a strange (but
intentional) pledge behaviour is to always knock-out high-bits from
mode_t on a number of system calls as a safety factor, and his bewilderment
that this appeared to be happening against valid modes (at least visually),
but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef.
ok millert
|
|
|
|
only if immediately following a '{}' placeholder. Slightly modify the
error message to indicate so.
Brought up by and discussed with Paul de Weerd, thanks!
ok millert@
|
|
requires (int) for a '*' modifier
ok millert
|
|
confirmed by naddy and deraadt
|
|
Already done by xargs(1). Pointed out by espie@, ok millert@
|
|
Using ARG_MAX directly doesn't fly when ARG_MAX gets bumped and the
kernel and userland are not in sync, effectively breaking find -exec +.
Use sysconf(3) as already done in xargs(1).
Spotted by sthen@, ok deraadt@ millert@ sthen@
|
|
getcap->cgetent. pwcache->user_from_uid. And then repair references.
ok jmc
|
|
-delete is part of POSIX since 2001 and tedu added support for it in 2012,
-print0 however never made it into any standard, so replace this less
portable idiom with its more concise built-in counterpart.
Both -print0 as well as xargs(1) -0 explain and reference each other and
CAVEATS goes into detail with problematic file names, so no information
is lost by replacing this particular example.
While here, make the -exec example rm(1) multiple files at once.
Feedback from claudio tb
Input and OK millert
|
|
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.
|
|
decomposition into major and minor is unsigned, so we should print them
with %u instead of %d.
ok guenther
|
|
ok millert
|
|
do repeated lookups. OK tb@
|
|
ok tb
while here, knock out a useless Tn;
|
|
the primaries that do not imply -print. From Kris Katterjohn, thanks!
ok jmc
|
|
From Kris Katterjohn, thanks.
ok jmc
|
|
provides retry on short-write file descriptors.
ok florian, previous versions seen by millert
|
|
to its other promises. Previously, find ran unpledged if the -exec{,dir}
or -ok primaries were specified: the tame(2) calls for find(1) were added
a few days before the "exec" promise was implemented and these code paths
were never revisited.
ok millert
|
|
|
|
lots of files without the arcane -exec or error prone xargs.
code from freebsd.
ok millert
|
|
|
|
|
|
enter the fork+execve codepath. That allows use of "stdio getpw rpath"!
Use of -exec methods have been discouraged for years anyways, with
-print0/xargs -0 now considered safer practice.
ok guenther millert
|
|
|
|
Noted by tedu@
|
|
|
|
points into the new store, not the old one. From Gregor Best.
|
|
handling along the way.
Reviews by Brendan MacDonell, Jeremy Devenport, florian, doug, millert
|
|
What's worse, the tzfile.h that gets installed is over 20 years old
and doesn't match the real tzfile.h in libc/time. This makes the
tree safe for /usr/include/tzfile.h removal. The TM_YEAR_BASE
define has been moved to time.h temporarily until its usage is
replaced by 1900 in the tree. Actual removal of tzfile.h is pending
a ports build. Based on a diff from deraadt@
|
|
Predefined strings are not very portable across troff implementations,
and they make the source much harder to read. Usually the intended
character can be written directly.
No output changes, except for two instances where the incorrect escape
was used in the first place.
tweaks + ok schwarze@
|
|
superflous '*' after '/*' and adding blank after terminating '$'.
Also eases parsing of the lines by simple awk scripts.
Aesthetic approval from tedu@.
|
|
possible. Annotate <sys/param.h> lines with their current reasons. Switch
to PATH_MAX, NGROUPS_MAX, HOST_NAME_MAX+1, LOGIN_NAME_MAX, etc. Change
MIN() and MAX() to local definitions of MINIMUM() and MAXIMUM() where
sensible to avoid pulling in the pollution. These are the files confirmed
through binary verification.
ok guenther, millert, doug (helped with the verification protocol)
|
|
i had to tweak their descriptions a little to make the text read nicely
while here, fix some minor issues:
- kill some unneeded Xo/Xc
- kill some unneeded Tn
- replace "\*Gt" with ">"
|
|
FTS_ERR. From Piotr Durlej.
|
|
okay chl@, tedu@
|
|
- tweak STANDARDS to make the note about -and and -or a little clearer
- remove some gnu clutter
ok millert sobrado
|
|
|
|
strftime() instead of parsing ctime()'s output.
ok millert@
|
|
|
|
|
|
|
|
range of i_num correctly, and now handles files > 4GB in size on 32-bit
machines.
ok otto millert
|
|
second occurance pointed out by Jeremie Courreges-Anglas, thanks!
ok guenther@ on the first occurance
|
