Age | Commit message (Collapse) | Author |
|
"rm -rfv nonexistent". problem spotted by Alfred Morgan
ok millert
|
|
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
|
|
getcap->cgetent. pwcache->user_from_uid. And then repair references.
ok jmc
|
|
requested by deraadt@ after repeated questions on bugs@ and tech@,
e.g. from Gregoire Jadi and Craig Skinner.
|
|
|
|
|
|
and present on several other systems. some ok, some less ok.
from Job Snijders
|
|
noticed by Jan Stary <hans at stare dot cz>;
return from main while here;
feedback and OK tb@, OK martijn@
|
|
|
|
ok benno deraadt
|
|
posix uses the language "resolves to the root directory" in this case.
ok millert
|
|
from Edgar Pettijohn <edgar at pettijohn-web.com>
fix another similar space in line 127. (pointed out by/OK jung@)
OK tb@ jung@
|
|
a user_from_uid(3) call...
|
|
rm -f ""
|
|
Patch from Theo Buehler who was inspired by watching Bryan Cantrill
in BSD Now 103.
Minor tweak from me to turn the complained variables into flags instead
of counters.
"i think it's ok" tedu@
"this isn't 1980 anymore" deraadt@
ok millert@
|
|
|
|
the remaining code paths can use tame "stdio rpath cpath". One again,
the "cpath" request says a path-based system call will be used to
"change" filesystem pathname layout, for instance any of O_CREAT, symlink,
rename, unlink...
|
|
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)
|
|
is plain wrong: remove it. the note in posix spec is misleading, to be fair
- most of the rest of notes in STANDARDS are really historical notes (admittedly
caused by the standards i guess) so move them into HISTORY. debatable, yes, but leaves
STANDARDS consistent. HISTORY is a hodge podge anyway, by neccesity.
- while there, fix a sentence splice in BUGS
sobrado agrees with the removal of the rmdir note; millert oks the diff
|
|
ok jca@ krw@
|
|
|
|
random at all
ok tedu@
|
|
|
|
|
|
directory entry then use the struct stat from that instead of doing
it again, and skip the rm_overwrite() call if fts_read() indicated
that the entry couldn't be a regular file.
ok millert@
|
|
that the file we have opened is the one we expected. Also open in
non-blocking mode to avoid a potential hang with FIFOs. Reported
by Radoslaw A. Zarzynski. Fix adapted from NetBSD. OK guenther@
|
|
- remove a stray .Pp
|
|
|
|
unmaintainable). these days, people use source. these id's do not provide
any benefit, and do hurt the small install media
(the 33,000 line diff is essentially mechanical)
ok with the idea millert, ok dms
|
|
updates to follow;
|
|
EACCES. From Tim van der Molen; ok millert@ ray@
|
|
of just warning and skipping the file.
OK millert and jmc.
|
|
|
|
- note which options are extensions to POSIX
discussed w/ deraadt otto millert
|
|
|
|
simpler (clearer), and matches cp(1), mv(1), posix, and even usage();
|
|
|
|
jaredy@
|
|
from nikolay kalev; ok deraadt@
|
|
|
|
ok millert@ tedu@
|
|
ok beck@ otto@
|
|
also, put example description before the example, and indent example;
|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
|
|
|
|
with hard links, and document it. In consultation with dynamo and
approved by millert.
|
|
|
|
|
|
hand editing to make comments line up correctly. Another pass is forthcoming that handles the cases that could not be done automatically.
|