| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
renameat is in unistd.h. Bump date.
|
|
|
|
the *at system calls on November 18th of last year. Reasons to revert
it include:
- it is incorrect in a whole variety of ways (but fortunately, one
of them is that the missing and improper permission checks have
no net effect);
- it was committed without review or discussion;
- core ruled that all the new O_* flags pertaining to the *at calls
needed to wait until their semantics could be clarified.
manu was asked to revert it on these grounds but has ignored the request.
I have left O_SEARCH defined and visible and made open() explicitly
ignore it. This way, most code that tries to use it will continue to
build and run. I've also arranged lib/libc/c063/t_o_search.c so that
the tests that make use of the O_SEARCH semantics will disappear until
O_SEARCH comes back, and fixed some mistakes and/or incorrect hacks
that were causing some of these to succeed despite the broken O_SEARCH
implementation.
|
|
Sort errors while here.
|
|
|
|
faccessat(2), fchmodat(2), fchownat(2), fstatat(2), mkdirat(2), mkfifoat(2),
mknodat(2), linkat(2), readlinkat(2), symlinkat(2), renameat(2), unlinkat(2),
utimensat(2), openat(2).
Also implement O_SEARCH for openat(2)
Still missing:
- some flags for openat(2)
- fexecve(2) implementation
|
|
and PATH_MAX.
|
|
as discussed on tech-kern some time back.
|
|
|
|
Patches provided by Joel Baker in PR 22280, verified by myself.
|
|
.In header.h
instead of
.Fd #include \*[Lt]header.h\*[Gt]
Much easier to read and write, and supported by groff for ages.
Okayed by ross.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(where applicable).
|
|
libraries contain stubs only (with minor exceptions a la pipe(2)), the purpose
of this section is to provide linkage information.
|
|
so we shouldn't override it with versions in the manpages. Wheee!
|
|
arguments; ensure that each is correct with respect to the
implementation, rather than being correct as per english.
|
|
interface.
|
|
|
|
high-order bit set", as this error is obsolete.
Eventually we may want to add code to some of the "optional" filesystems
(msdosfs, etc.) that checks for illegal characters. At that time it would
be appropriate to reintroduce this error with appropriate text. Perhaps
"The pathname contains a character that is not valid for filesystem type".
|
|
description of ENAMETOOLONG error.
|
|
the formatting is consistant.
|
|
Use .Fn rather than .Nm macro in HISTORY and STANDARDS sections.
Use .At and .St macros instead of spelling out "Version 6 UNIX",
"IEEE 1003.1-1988 (POSIX)", etc.
|
|
|
|
|