summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2011-01-08 00:23:31 +0100
committerThomas Schwinge <thomas@schwinge.name>2011-01-08 00:23:31 +0100
commit9d64538617425f795e33d711d8bd4f5d823de8e7 (patch)
tree7bd27567dd404bfa2c3de5949e8cf27715f4240d
parent8e59767f344fd15cbb2e1adfa6137223adfe3ccb (diff)
open_issues/implementing_hurd_on_top_of_another_system: IRC, #hurd, 2010-12-28.
-rw-r--r--open_issues/implementing_hurd_on_top_of_another_system.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/open_issues/implementing_hurd_on_top_of_another_system.mdwn b/open_issues/implementing_hurd_on_top_of_another_system.mdwn
index 7e88e322..614cf442 100644
--- a/open_issues/implementing_hurd_on_top_of_another_system.mdwn
+++ b/open_issues/implementing_hurd_on_top_of_another_system.mdwn
@@ -65,3 +65,16 @@ IRC, #hurd, August / September 2010
the Hurd to Linux or BSD
Continue reading about the [[benefits of a native Hurd implementation]].
+
+---
+
+IRC, #hurd, 2010-12-28
+
+ <antrik> kilobug: there is no real requirement for the Hurd to run on a
+ microkernel... as long as the important mechanisms are provided (most
+ notably external pagers and Mach IPC), the Hurd could run an top of
+ pretty much any kernel...
+ <antrik> whether it makes sense is another question of course :-)
+ <antrik> though I must say that I'm more and more convinced running the
+ Hurd on top of a monolithic kernel would actually be a useful approach
+ for the time being...