Go to file
Tomas Hruby d3e991a7b6 PM signal handling check too strict
- this panic may be unnecessarily triggered if PM gets the delayed
  stop signal from kernel before it gets reply from VFS to the UNPAUSE
  call.

- after this change PM does not proceed to delivering the signal until
  the reply from VFS is received. Perhaps PM could deliver the signal
  straight away as it knows that the process does not run. Possibly
 i dangerous.

- the signal is deliverd immediately after the UNPAUSE reply as the
  pending signals are always checked at the moment.
2010-05-10 14:27:22 +00:00
benchmarks only check local benchmark dir if it exists 2010-02-04 18:15:10 +00:00
boot Allow loading images > 16M 2010-04-29 15:14:07 +00:00
commands Use of all NIL_* defines converted to NULL 2010-05-10 13:26:00 +00:00
docs Fix Inet initialization race. 2010-05-06 22:18:21 +00:00
drivers Use of all NIL_* defines converted to NULL 2010-05-10 13:26:00 +00:00
etc Fix Inet initialization race. 2010-05-06 22:18:21 +00:00
include Removed defines not used since r6844. 2010-05-10 13:29:04 +00:00
kernel Use of all NIL_* defines converted to NULL 2010-05-10 13:26:00 +00:00
lib Use of all NIL_* defines converted to NULL 2010-05-10 13:26:00 +00:00
man Add scancode reading capability to TTY 2010-04-15 06:55:42 +00:00
servers PM signal handling check too strict 2010-05-10 14:27:22 +00:00
test - Add test52 to test FPU context switching 2010-05-03 15:12:39 +00:00
tools cd boot workaround for bioses that didn't want to boot >4 image sectors. 2010-04-26 22:07:21 +00:00
LICENSE Fix parameter parsing in cut 2010-01-21 10:16:05 +00:00
Makefile Convert kernel over to bsdmake 2010-04-01 22:22:33 +00:00