Thomas Bushnell BSG wrote:
We generally tend to dislike the use of asynchronous messages. They are
great for Mach, but we would like to avoid the need to use them in
general.
Keeping things always as RPCs makes the system much more likely to be
portable in the future to other kernels.
It's nice to know the direction the implementation is headed. I
would be grateful if you could supply links that further document
the above mentioned statement. To be honest, i had the exactly
opposite idea since it has been mentioned that the Coyotos kernel
was a candidate to replace the Mach kernel and Coyotos has an
asynchronous design.
Regarding the syslog problem, what can be done? From what has been
said so far, the intermediate translator solution is not optimal.
Do we use syslog as it is but carefully because of the internal
locking? If so, this task should be deleted.
How about this: what if the syslog daemon was rewritten as a
syslog translator capable of handling the locking issue?
Constantine
_______________________________________________
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
