| Age | Commit message (Collapse) | Author |
|---|
|
The variable "clang" is modified from a signal handler. Change it
from an 'int' to a 'sig_atomic_t' and mark it 'volatile', as we
recommend in signal(3).
ok millert@ kn@
|
|
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
|
|
|
|
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.
|
|
Tolerance for up to 25 SIGSYS deliveries was added to init(8) soon after
the addition of sysctl(2) at CSRG, presumably to ease the transition to
the new ABI.
After 25 years of work the ABI transition is finally complete and we can
now safely remove this splint.
In general, we now have better practices and methods for helping userspace
across kernel ABI breaks.
ok deraadt@
|
|
Ensures that we can use the check if the system clock is set backwards.
While here, move time retrieval into the child process in start_getty(),
and only get the time if se_started has been set.
ok millert@ tb@
|
|
ok deraadt@
|
|
OK jca@, no objection deraadt@
|
|
ok mlarkin
|
|
instead of relying on other methods, after readpassphrase. Some programs on
this diff won't benefit that much since it happens near the terminal path, but
someone might copy the unsafe idiom to another program and place it where it
may leak sensitive data.
Discussed aeons ago with tb@, OK deraadt@ and beck@
|
|
machdep.lidaction=0 # do nothing
machdep.lidaction=1 # suspend
machdep.lidaction=2 # hibernate
lidsuspend is just an alias for lidaction, so if you change one, the
other one will have the same value. The plan is to remove
machdep.lidsuspend eventually when people have upgraded their
/ets/sysctl.conf.
discussed with deraadt, who came up with the new MIB name
no objections mlarkin
ok stsp halex jcs
|
|
patches from Sevan Janiyan <venture37 at geeklan dot co dot uk>;
verified using minnie.tuhs.org/cgi-bin/utree.pl
|
|
from rob pierce
|
|
OK tedu millert
|
|
|
|
ok deraadt@
|
|
from /dev/null. The code is taken from daemon(3). Also move this
operation to the beginning.
OK millert@ deraadt@
|
|
ok millert@
|
|
|
|
|
|
|
|
immutable flags would just be a pita. remove custom bin mode.
|
|
malloc, calloc, realloc*
ok krw millert
|
|
modified inside signal handlers. Instead of returning a function
pointer, the state functions now return an enum for the next state.
This is used as an index into an array of function pointers to
do the actual state change in transition(). OK deraadt@
|
|
ok deraadt@
|
|
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)
|
|
OK millert@
|
|
|
|
multiuser since we are not actually going multiuser. Fixes a problem
where the securelevel was raised for rc.shutdown even when reboot
was run from single user mode. OK deraadt@
|
|
Just because CPU_LIDSUSPEND is defined in cpu.h does mean it is
actually supported by the hardware. OK halex@
|
|
- pull in machine/cpu.h so we can actually see CPU_LIDSUSPEND if it's there
- fix the resulting compilation errors now that the code is actually used
"Just go for it" deraadt@
|
|
|
|
|
|
- Explain single user mode once, not three times.
- Do not claim that the boot program talked to init; it cannot do so.
- Mention that the OpenBSD kernel does not support init -f.
- And some minor rewordings and reorderings.
Feedback and ok jmc@.
|
|
|
|
pointed out by kettenis@ and deraadt@
|
|
reboots the machine instead just halting or powering down.
diff from Jonathan Matthew
manpage tweaks from jmc@
ok deraadt@
|
|
OK deraadt@
|
|
|
|
"I like this" marco@, "Sure" deraadt@
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
very painful, and "gettys" is misleading;
|
|
This will be used by kernel components which are trying to really really
power the system down. suggested and tested by jason
|
|
deraadt@
|
