From e7e194bdc1fd81cbe08c7fc866c3deb692502efc Mon Sep 17 00:00:00 2001 From: guest Date: Sat, 22 Apr 2006 20:42:34 +0000 Subject: none --- Hurd/MicrokernelCoyotos.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 Hurd/MicrokernelCoyotos.mdwn (limited to 'Hurd') diff --git a/Hurd/MicrokernelCoyotos.mdwn b/Hurd/MicrokernelCoyotos.mdwn new file mode 100644 index 00000000..40fd6e9d --- /dev/null +++ b/Hurd/MicrokernelCoyotos.mdwn @@ -0,0 +1,9 @@ +# The Coyotos microkernel + +[Coyotos](http://www.coyotos.org/index.html) is a microkernel and OS and the successor of EROS, that itself is the successor of KeyKOS. A more complete history can be found [here](http://www.coyotos.org/history.html). It's main objectives are to correcte some shortcomings of EROS, demonstrate that an atomic kernel design scales well and to completely formally verify both the kernel and critical system components by writing them in a new language called bitc. + +Coyotos is an orthogonally persistent pure capability system. It uses continuation based unbuffered asynchronous IPC (actually it's synchronous IPC whith asynchronous syscalls). + +TODO: explain these terms and (more important) their consequences on system design. + +The coyotos microkernel specification can be found [here](http://www.coyotos.org/docs/ukernel/spec.html) -- cgit v1.2.3