diff options
| -rw-r--r-- | history/port_to_another_microkernel.mdwn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/history/port_to_another_microkernel.mdwn b/history/port_to_another_microkernel.mdwn index a8ec3fe7..5815402f 100644 --- a/history/port_to_another_microkernel.mdwn +++ b/history/port_to_another_microkernel.mdwn @@ -31,7 +31,7 @@ At first, there was an effort to directly port the Hurd to the Encountering a number of fundamental design issues with the [[Mach microkernel|microkernel/mach]] (mostly regarding [[resource -management|open_issues/resource_management_problems]]), some of the Hurd +management|service_solahart_jakarta_selatan__082122541663/resource_management_problems]]), some of the Hurd developers began experimenting with using other microkernels for the Hurd around the turn of the millenium. @@ -117,7 +117,7 @@ along their way. Neal goes on: > Before Marcus and I considered [[microkernel/Coyotos]], we had already > rejected some parts of the Hurd's design. The -> [[open_issues/resource_management_problems]] were +> [[service_solahart_jakarta_selatan__082122541663/resource_management_problems]] were > what prompted me to look at L4. Also, some of the problems with > [[hurd/translator]]s were already well-known to us. (For a more detailed > description of the problems we have identified, see our [[hurd/critique]] in the @@ -166,7 +166,7 @@ trying to use a third-party microkernel will always result in trouble. So Neal Walfield created the experimental [[microkernel/Viengoos]] kernel instead -- based on the experience from the previous experiments with L4 and Coyotos -- for his [[research on resource -management|open_issues/resource_management_problems]]. Currently he works in +management|service_solahart_jakarta_selatan__082122541663/resource_management_problems]]. Currently he works in another research area though, and thus Viengoos is on hold. |