| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Alphabet taught to Green by: obrien
|
|
|
|
| |
Use _mktemp internally
|
|
|
|
|
|
| |
next try over chroot (descriptor closed). getgrnam() used already handles
endgrent() properly and honors _gr_stayopen. Automatically call
setgroupent(1) when _pw_stayopen is set (for YP/NIS code).
|
|
|
|
| |
PR: 14201
|
| |
|
|
|
|
|
|
| |
visible from userland any more.
Reviewed by: luoqi
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
setjmp() gets the jmp_buf pointer from the wrong place (the place
where the return address is) in the shlib case, and uses it (only)
to fetch the current signal mask to address (return_address + 28).
This address is normally read-only (I hope), so the sigprocmask()
call has no effect except to return an error code.
\end{quote}
Submitted by: bde
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
the code, which seems to implement the POSIX requirements, and
have described the behavior here. Basically, it behaves the same
as select(2).
Noticed by: John Polstra
|
|
|
|
|
|
|
|
|
| |
to call osigaction(). But that's wrong because it causes the
handler to receive a struct osigcontext instead of the expected
struct sigcontext. Use sigaction() instead, copying the compatible
portion of the signal mask.
Reviewed by: marcel
|
|
|
|
|
|
|
| |
o Remove bitrotted #undef directives
o Actually set errno now and order the functions
Submitted by: bde
|
|
|
|
|
|
|
| |
o Fix formatting
o Return the error if sigprocmask fails instead of undefined data.
Submitted by: bde
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-----------------------------
Most of the userland changes are in libc. For both the alpha
and the i386 setjmp has been changed to accomodate for the
new sigset_t. Internally, libc is mostly rewritten to use the
new syscalls. The exception is in compat-43/sigcompat.c
The POSIX thread library has also been rewritten to use the
new sigset_t. Except, that it currently only handles NSIG
signals instead of the maximum _SIG_MAXSIG. This should not
be a problem because current applications don't use any
signals higher than NSIG.
There are version bumps for the following libraries:
libdialog
libreadline
libc
libc_r
libedit
libftpio
libss
These libraries either a) have one of the modified structures
visible in the interface, or b) use sigset_t internally and
may cause breakage if new binaries are used against libraries
that don't have the sigset_t change. This not an immediate
issue, but will be as soon as applications start using the
new range to its fullest.
NOTE: libncurses already had an version bump and has not been
given one now.
NOTE: doscmd is a real casualty and has been disconnected for
the moment. Reconnection will eventually happen after
doscmd has been fixed. I'm aware that being the last one
to touch it, I'm automaticly promoted to being maintainer.
According to good taste this means that I will receive a
badge which either will be glued or mechanically stapled,
drilled or otherwise violently forced onto me :-)
NOTE: pcvt/vttest cannot be compiled with -traditional. The
change cause sys/types to be included along the way which
contains the const and volatile modifiers. I don't consider
this a solution, but more a workaround.
|
|
|
|
|
|
| |
required to be "announced" by a new bit in sa_flags to indicate the
program is aware of and has taken care of them. eg: SA_SIGINFO means
the program has used the sa_siginfo field (versus sa_handler).
|
|
|
|
|
|
|
|
|
| |
sigaction, used to describe an action to be taken, is defined in the
header <signal.h> to include at least the following members:"
^^^^^^^^
A sigaction defined on stack with essentially random contents may have
just about anything underneath fields that the program doesn't know about.
It is not safe to delete the bzero.
|
|
|
|
| |
initialization of sa_flags allows us to lose the bzero.
|
|
|
|
|
|
| |
initialization of sa_flags allows us to lose the bzero.
$FreeBSD$ tag added.
|
|
|
|
| |
Inspired by: NetBSD commit message describing this.
|
| |
|
| |
|
|
|
|
|
|
| |
This function was removed by jdp in rev.1.5 of dlopen.3
Forgoten by: jdp
|
|
|
|
|
| |
PR: docs/13658
Submitted by: Zahemszky Gabor <zgabor@code.hu>
|
|
|
|
|
| |
PR: docs/13222
Submitted by: Ben Smithurst <ben@scientia.demos.co.uk>
|
|
|
|
|
|
| |
manual page states. `chmod +s foo' and `chmod +t foodir' now work.
PR: 13889
|
|
|
|
| |
Reviewed by: mpp
|
|
|
|
| |
Spotted by: John Polstra <jdp@polstra.com> (again)
|
|
|
|
|
|
|
| |
Also spelled out the return values and conditions a little
better.
Noticed by: John Polstra <jdp@polstra.com>
|
|
|
|
|
|
| |
PR: docs/13702
Submitted by: Stephen J. Roznowski <sjr@home.com>
Reviewed by: mpp
|
|
|
|
|
| |
PR: docs/13814
Submitted by: Alex Vasylenko <lxv@mix.nest.org>
|
|
|
|
| |
can be handled intelligently.
|
|
|
|
|
|
|
|
| |
else, it is equivalent to strdup(). So, we will check if the substitution
tables are trivial at the load time, and possibly save 2 calls to
__collate_substitute() in strcoll().
Still, __collate_substitute() should not exist.
|
|
|
|
|
|
|
|
| |
Other minor optimizations. I got ~30% speedup in strcoll() for 50 char strings,
~40% speedup for 100 char strings, and unmeasurable speedup for 1M strings.
Collates are still terribly slow. To make them reasonable fast,
__collate_substitute() should be killed.
|
|
|
|
|
|
|
|
|
| |
representation of the full month name. In the Russian locale, this alternative
will be "nominative case", useful when the date designate month as a whole.
E.g. month heading in a calendar. I hope it can be useful for some other
locales too.
Discussed with: wollman, ache
|
|
|
|
| |
Pointed out by: obrien
|
| |
|
|
|
|
| |
Obtained from: NetBSD
|
| |
|
|
|
|
|
| |
Submitted by: Dan Nelson <dnelson@emsphone.com>
Forgotten by: mpp
|
|
|
|
| |
- mdoc(7) fixes
|
|
|
|
|
|
|
|
| |
where getpwent() would ignore wildcard entries that followed a netgroup
entry.
PR: misc/12999
Submitted by: David Hedley <david@inty.net>
|
| |
|
|
|
|
| |
Reviewed by: mpp
|
|
|
|
|
|
|
|
| |
Style and punctuation errors fixes.
ERRORS section included to RETURN VALUES because it's
describing return values instead of errors and their handling.
Reviewed by: mpp
|
|
|
|
|
|
| |
Correct RB_* values list bounds.
Reviewed by: mpp
|
|
|
|
| |
Reviewed by: mpp
|
|
|
|
| |
Reviewed by: mpp
|
|
|
|
| |
Reviewed by: mpp
|