summaryrefslogtreecommitdiff
path: root/community
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2009-03-10 03:56:40 +0100
committerantrik <antrik@users.sf.net>2009-03-10 23:56:43 +0100
commitae8fa4147ebd99a0825953694010d10467e78d33 (patch)
tree1975113d35d15ae9391456aab1b7f2f612759e88 /community
parent7be1677ac209d5ade197c8c53ab3556732082bb6 (diff)
Virtualization GSoC task: Drop subhurds subtask
Zheng Da is currently working on rootless subhurds etc.
Diffstat (limited to 'community')
-rw-r--r--community/gsoc/project_ideas/virtualization.mdwn8
1 files changed, 1 insertions, 7 deletions
diff --git a/community/gsoc/project_ideas/virtualization.mdwn b/community/gsoc/project_ideas/virtualization.mdwn
index 52b1f48d..4f2d260e 100644
--- a/community/gsoc/project_ideas/virtualization.mdwn
+++ b/community/gsoc/project_ideas/virtualization.mdwn
@@ -25,13 +25,7 @@ desired constellations.
The goal is to create a set of powerful tools for managing at least one
desirable virtualization scenario. One possible starting point could be the
[[hurd/subhurd]]/[[hurd/neighborhurd]] mechanism, which allows a second almost totally
-independant instance of the Hurd in parallel to the main one. The current
-implementation has serious limitations though. A subhurd can only be started by
-root. There are no communication channels between the subhurd and the main one.
-There is no mechanism for safe sharing of hardware devices. Fixing this issues
-could turn subhurds into a very powerful solution for lightweight
-virtualization using so-called logical partitions. (Similar to Linux-vserver,
-OpenVZ etc.)
+independant instance of the Hurd in parallel to the main one.
While subhurd allow creating a complete second system instance, with an own set
of Hurd servers and [[UNIX]] daemons and all, there are also situations where it is