>
> If I split sigaction(), sigsuspend(), sigpending(), sigprocmask() and
> sigaltstack() into front-end and back-end pieces a-la NetBSD so that
> emulator-specific signal semantics can be imposed without totally
> duplicating those routines inside the emulator (like I did with
> sendit() and rec
< said:
> If I split sigaction(), sigsuspend(), sigpending(), sigprocmask() and
> sigaltstack() into front-end and back-end pieces a-la NetBSD so that
> emulator-specific signal semantics can be imposed without totally
> duplicating those routines inside the emulator (like I did with
> sendit() a
We currently have routines like fork1() and killpg1() in /sys/kern/*
to implement generic functionality for actions with more than one
"front-end".
NetBSD has done something similar for signals, so that emulators
with non-BSD signal semantics can implement their way of doing things
as an emulat
