> It's also questionable if you really want another thread to wait on a > condition all the time. OTOH, there probably is no suitable other > thread. So, if we need another thread, then that's ok. But block > signals for all other threads, and have that thread also handle the > signals you want to catch. That's best because then memory is already > synchronized. Having that thread sleep most of the time and check for the Thinking of it, this must have caused the problems I had with console_exit. It is called from the pc_kbd driver's thread. I will fix this as well as soon as someone can explain me how to block signals for other threads... Thanks, Marco
_______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-hurd