summaryrefslogtreecommitdiff
path: root/open_issues/implementing_hurd_on_top_of_another_system.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-10-31 08:02:38 +0100
committerThomas Schwinge <thomas@schwinge.name>2010-10-31 08:02:38 +0100
commite4dce63f1d51611a0f123299680160a82f11e1ea (patch)
treec4d7faec6eb97f0f3a25838ea1987ebe46344a24 /open_issues/implementing_hurd_on_top_of_another_system.mdwn
parent713fec605aeb6076188ae6d803f4ec3114a574bf (diff)
open_issues/virtualization/networking: New. And some other minor reorganization.
Diffstat (limited to 'open_issues/implementing_hurd_on_top_of_another_system.mdwn')
-rw-r--r--open_issues/implementing_hurd_on_top_of_another_system.mdwn3
1 files changed, 2 insertions, 1 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 a3e367ce..1d7a1e50 100644
--- a/open_issues/implementing_hurd_on_top_of_another_system.mdwn
+++ b/open_issues/implementing_hurd_on_top_of_another_system.mdwn
@@ -11,7 +11,8 @@ License|/fdl]]."]]"""]]
[[!tag open_issue_documentation]]
It is possible to run Hurd stuff on top of another system instead of on Mach.
-One obvious variant is emulation ([[hurd/running/QEMU]], for example), but
+One obvious variant is [[emulation]] (using [[hurd/running/QEMU]], for
+example), but
doing that does not really integratable the Hurd guest into the host system.
There is also a more direct way, more powerful, but it also has certain
requirements to do it effectively: