summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorguest <guest>2006-04-22 20:42:34 +0000
committerguest <guest>2006-04-22 20:42:34 +0000
commite7e194bdc1fd81cbe08c7fc866c3deb692502efc (patch)
treeebb9e137da683cc894bb0a7208b11f32502e7679
parentdf22dff57097d86d85ce4a79b875d31e67a356a3 (diff)
none
-rw-r--r--Hurd/MicrokernelCoyotos.mdwn9
1 files changed, 9 insertions, 0 deletions
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 @@
+# <a name="The_Coyotos_microkernel"> The Coyotos microkernel </a>
+
+[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)