summaryrefslogtreecommitdiff
path: root/hurd/ng/microkernelcoyotos.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-12-07 14:26:40 +0100
committerThomas Schwinge <thomas@schwinge.name>2010-12-07 14:26:40 +0100
commit238c43499c4e08562024c3ef59e50aa365b5f1b2 (patch)
tree7fbef4ecd63fc7526c24660866338f887f2bdeae /hurd/ng/microkernelcoyotos.mdwn
parenta167e7ae26b5159da570771ae39a6d56def1be7c (diff)
Some bits about L4 and Coyotos.
Diffstat (limited to 'hurd/ng/microkernelcoyotos.mdwn')
-rw-r--r--hurd/ng/microkernelcoyotos.mdwn11
1 files changed, 0 insertions, 11 deletions
diff --git a/hurd/ng/microkernelcoyotos.mdwn b/hurd/ng/microkernelcoyotos.mdwn
deleted file mode 100644
index 2340901d..00000000
--- a/hurd/ng/microkernelcoyotos.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-# <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). Its main objectives are to correcte some shortcomings of EROS, demonstrate that an atomic kernel design scales well, and (eventually) to completely formally verify both the kernel and critical system components by writing them in a new language called [bitc](http://www.bitc-lang.org/). [See [l4.verified](http://nicta.com.au/research/projects/l4.verified) for work on formally verifying an L4 microkernel.]
-
-Coyotos is an orthogonally persistent pure capability system. It uses
-continuation based unbuffered asynchronous IPC (actually it's synchronous IPC
-with asynchronous [[system calls]]).
-
-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)