From ec65a094c5367ff523fe572d3dfdcc5b1c92715c Mon Sep 17 00:00:00 2001 From: GNU Hurd wiki engine Date: Fri, 19 Sep 2008 08:43:07 +0000 Subject: web commit by scolobb --- community/scolobb.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/community/scolobb.mdwn b/community/scolobb.mdwn index 594281fe..2de8eb4f 100644 --- a/community/scolobb.mdwn +++ b/community/scolobb.mdwn @@ -26,6 +26,18 @@ The code is at . --- +###Did this week + +* Modified the node cache so that it maintains shadow nodes alive. + +###Plans for the next week + +* Implement the shutting down of translator stacks when *nsmux* is asked to go away (in case **antrik** considers that necessary). + +* Make *nsmux* provide the access to the translator stack of the real node, in case a translator (mainly, a filter) should ask for its underlying node to be opened in O_NOTRANS mode. + +--- + ###Current Status ####DONE: @@ -66,6 +78,10 @@ The code is at . ###Progress +####8: Fri Sep 19: + +> Modified the ncache so that it now maintains shadow nodes (and directory nodes too, it is a side effect at the moment) alive. + ####7: Sat Aug 30 - Fri Sep 5: > Added the code for shutting down dynamic translator stacks. -- cgit v1.2.3 From bb896d18594fe9f3176fe9b5cc12bd841794ffdd Mon Sep 17 00:00:00 2001 From: tschwinge Date: Fri, 19 Sep 2008 11:58:48 +0000 Subject: Typo fixes, minor enhancement, and a removal. --- index.mdwn | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/index.mdwn b/index.mdwn index 3b52f033..3a6cfe7c 100644 --- a/index.mdwn +++ b/index.mdwn @@ -52,7 +52,7 @@ Find more information about it at the There are [[various_possibilities|hurd/running]] of running a GNU/Hurd system. -And this wiki is living proof of the usability of the HURD, as it is served by a GNU/HURD system. More people using GNU: [[Hurd/WhoRunsGNU]] +And this wiki is living proof of the usability of the Hurd, as it is served by a Debian GNU/Hurd system. More people using GNU: [[Hurd/WhoRunsGNU]] ## What is the Hurd? @@ -99,8 +99,6 @@ Functional systems are installable in a dual-boot configuration. Development systems are currently mostly based on the [[Debian_GNU/Hurd|hurd/running/debian]] port sponsored by the [Debian project](http://www.debian.org/). -This wiki is living proof of a working HURD installation, as it is served by a HURD based system. - Community resources for related projects focus around the official website , this site at , the [[mailing_lists]] and the [[IRC_channels|IRC]]. -- cgit v1.2.3 From 3b44aa0aa790cc501f15308f4d5b86c97f0ab0b6 Mon Sep 17 00:00:00 2001 From: pjrm Date: Mon, 22 Sep 2008 05:44:55 +0000 Subject: Add link to L4 verification. (Feel free to move to a better page, e.g. up a level once it has some other text.) --- hurd/ng/microkernelcoyotos.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hurd/ng/microkernelcoyotos.mdwn b/hurd/ng/microkernelcoyotos.mdwn index 40fd6e9d..e6b2fe8e 100644 --- a/hurd/ng/microkernelcoyotos.mdwn +++ b/hurd/ng/microkernelcoyotos.mdwn @@ -1,6 +1,6 @@ # 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](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. [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 whith asynchronous syscalls). -- cgit v1.2.3 From 2ddd53f4463ee8ba0bab65be7a10efcbad3a27c7 Mon Sep 17 00:00:00 2001 From: pjrm Date: Mon, 22 Sep 2008 05:50:15 +0000 Subject: Add link for bitc. --- hurd/ng/microkernelcoyotos.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hurd/ng/microkernelcoyotos.mdwn b/hurd/ng/microkernelcoyotos.mdwn index e6b2fe8e..cdf4e1bf 100644 --- a/hurd/ng/microkernelcoyotos.mdwn +++ b/hurd/ng/microkernelcoyotos.mdwn @@ -1,8 +1,8 @@ # 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). 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. [See [l4.verified](http://nicta.com.au/research/projects/l4.verified) for work on formally verifying an L4 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). 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 whith asynchronous syscalls). +Coyotos is an orthogonally persistent pure capability system. It uses continuation based unbuffered asynchronous IPC (actually it's synchronous IPC with asynchronous syscalls). TODO: explain these terms and (more important) their consequences on system design. -- cgit v1.2.3