diff options
-rw-r--r-- | hurd/history/port_to_l4.mdwn | 63 | ||||
-rw-r--r-- | hurd/ng.mdwn | 2 | ||||
-rw-r--r-- | hurd/ng/history.mdwn | 50 |
3 files changed, 55 insertions, 60 deletions
diff --git a/hurd/history/port_to_l4.mdwn b/hurd/history/port_to_l4.mdwn index 6a17d1ff..03795dc4 100644 --- a/hurd/history/port_to_l4.mdwn +++ b/hurd/history/port_to_l4.mdwn @@ -1,5 +1,5 @@ -[[meta copyright="Copyright © 2001, 2002, 2003, 2004, 2005, 2008, 2009 Free -Software Foundation, Inc."]] +[[meta copyright="Copyright © 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009 +Free Software Foundation, Inc."]] [[meta license="""[[toggle id="license" text="GFDL 1.2+"]][[toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -12,8 +12,16 @@ is included in the section entitled [[meta title="Porting the Hurd to L4: Hurd/L4"]] There was an effort to port the Hurd from [[microkernel/Mach]] to the -[[L4_microkernel_family|microkernel/L4]], mostly lead by Marcus Brinkmann and -Neal Walfield. Even though there was progress, this port never reached a +[[L4_microkernel_family|microkernel/L4]]. + +The idea of using L4 as a [[microkernel]] for a [[Hurd_system|hurd]] was +initially voiced in the [[Hurd_community|community]] by Okuji Yoshinori, who, +for discussing this purpose, created the [[mailing_lists/l4-hurd]] mailing list +in November 2000. + +The project itself then was mostly lead by Marcus Brinkmann and Neal Walfield. +Even though there was progress -- see, for example, the +[[QEMU_image_for_L4|running/qemu/image_for_l4]] -- this port never reached a releasable state. Eventually, a straight-forward port of the original Hurd's design wasn't deemed feasible anymore by the developers, partly due to them not cosidering L4 suitable for implementing a general-purpose operating system on @@ -24,12 +32,13 @@ they discovered along their way. Read the [[critique]] and a By now, the development of Hurd/L4 has stopped. However, Neal Walfield moved on to working on a newly designed kernel called [[microkernel/viengoos]]. +Over the years, a lot of discussion have been held on the +[[mailing_lists/l4-hurd]] mailing list, which today is still the right place +for [[next-generation_Hurd|ng]] discussions. -Development was done in the `hurd-l4` module of the Hurd CVS repository. The -`doc` directory contains a design document that is worth reading for anyone who -wishes to learn more about Hurd/L4. Discussion have been held on the -[[mailing_lists/l4-hurd]] mailing list, which is still the right place for -[[next-generation_Hurd|ng]] discussions. +Development of Hurd/L4 was done in the `hurd-l4` module of the Hurd CVS +repository. The `doc` directory contains a design document that is worth +reading for anyone who wishes to learn more about Hurd/L4. One goal of porting the Hurd to L4 was to make the Hurd independend of Mach @@ -54,3 +63,39 @@ of the kernel's [[TCB]]. One idea was to first introduce a Mach-on-L4 emulation layer, to easily get a usable (though slow) Hurd-using-Mach-interfaces-on-L4 system, and then gradually move the Hurd servers to use L4 intefaces rather than Mach ones. + + +Neal Walfield started the original Hurd/L4 port while at Karlsruhe in 2002. He +explains: + +> My intention was to adapt the Hurd to exploit L4's concepts and intended +> [[design_pattern]]s; it was not to simply provide a Mach +> [[compatibility_layer]] on top of L4. When I left Karlsruhe, I no longer had +> access to [[microkernel/l4/Pistachio]] as I was unwilling to sign an NDA. +> Although the specification was available, the Karlsruhe group only [released +> their code in May +> 2003](https://lists.ira.uni-karlsruhe.de/pipermail/l4ka/2003-May/000345.html). +> Around this time, Marcus began hacking on Pistachio. He created a relatively +> complete run-time. I didn't really become involved again until the second +> half of 2004, after I complete by Bachelors degree. + +> Before Marcus and I considered [[microkernel/Coyotos]], we had already +> rejected some parts of the Hurd's design. The +> [[ng/resource_management_problems]] were what prompted me to look at L4. +> Also, some of the problems with [[translator]]s were already well-known to +> us. (For a more detailed description of the problems we have identified, see +> our [[critique]] in the 2007 July's SIGOPS OSR. We have also written a +> forward-looking [[ng/position_paper]].) + +> We visited Jonathan Shapiro at Hopkins in January 2006. This resulted in a +> number of discussions, some quite influential, and not always in a way which +> aligned our position with that of Jonathan's. This was particularly true of +> a number of security issues. + +A lange number of discussion threads can be found in the archives of the +[[mailing_lists/l4-hurd]] mailing list. + +> Hurd-NG, as we originally called it, was an attempt to articulate the system +> that we had come to envision in terms of interfaces and description of the +> system's structure. The new name was selected, if I recall correctly, as it +> clearly wasn't the Hurd nor the Hurd based on L4. diff --git a/hurd/ng.mdwn b/hurd/ng.mdwn index 22613f54..fb4d742f 100644 --- a/hurd/ng.mdwn +++ b/hurd/ng.mdwn @@ -14,7 +14,7 @@ This section explains the motivations behind the new design: * [[Issues_with_L4_Pistachio]] * [[Limitations_of_the_original_Hurd_design]] - * [[History]] + * History of the [[history/port_to_L4]] # Work already done diff --git a/hurd/ng/history.mdwn b/hurd/ng/history.mdwn deleted file mode 100644 index 652bccf3..00000000 --- a/hurd/ng/history.mdwn +++ /dev/null @@ -1,50 +0,0 @@ -[[meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[meta license="""[[toggle id="license" text="GFDL 1.2+"]][[toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU_Free_Documentation_License|/fdl]]."]]"""]] - -The idea of using [[microkernel/L4]] as a [[microkernel]] for a -[[Hurd_system|hurd]] was initially voiced in the [[Hurd_community|community]] -by Okuji Yoshinori. He created the [[mailing_lists/l4-hurd]] mailing list in -November 2000. It does not appear that he got any further than simply -suggesting it as an alternative to [[microkernel/Mach]] and doing some reading. - -Neal Walfield started the original Hurd/L4 port while at Karlsruhe in 2002. -He explains: - -> My intention was to adapt the Hurd to exploit L4's concepts and intended -> [[design_pattern]]s; it was not to simply provide a Mach -> [[compatibility_layer]] on top of L4. When I left Karlsruhe, I no longer had -> access to [[microkernel/l4/Pistachio]] as I was unwilling to sign an NDA. -> Although the specification was available, the Karlsruhe group only [released -> their code in May -> 2003](https://lists.ira.uni-karlsruhe.de/pipermail/l4ka/2003-May/000345.html). -> Around this time, Marcus began hacking on Pistachio. He created a relatively -> complete run-time. I didn't really become involved again until the second -> half of 2004, after I complete by Bachelors degree. - -> Before Marcus and I considered [[microkernel/Coyotos]], we had already -> rejected some parts of the Hurd's design. The [[resource_management_problems]] -> were what prompted me to look at L4. Also, some of the problems with -> [[translator]]s were already well-known to us. (For a more detailed -> description of the problems we have identified, see our [[critique]] in the -> 2007 July's SIGOPS OSR. We have also written a forward-looking -> [[position_paper]].) - -> We visited Jonathan Shapiro at Hopkins in January 2006. This resulted in a -> number of discussions, some quite influential, and not always in a way which -> aligned our position with that of Jonathan's. This was particularly true of -> a number of security issues. - -A lange number of discussion threads can be found in the archives of the -[[mailing_lists/l4-hurd]] mailing list. - -> Hurd-NG, as we originally called it, was an attempt to articulate the system -> that we had come to envision in terms of interfaces and description of the -> system's structure. The new name was selected, if I recall correctly, as it -> clearly wasn't the Hurd nor the Hurd based on L4. |