summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/server_overriding.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'community/gsoc/project_ideas/server_overriding.mdwn')
-rw-r--r--community/gsoc/project_ideas/server_overriding.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/server_overriding.mdwn b/community/gsoc/project_ideas/server_overriding.mdwn
index 3a975ecf..6e3d5e14 100644
--- a/community/gsoc/project_ideas/server_overriding.mdwn
+++ b/community/gsoc/project_ideas/server_overriding.mdwn
@@ -12,7 +12,7 @@ License|/fdl]]."]]"""]]
[[!meta title="Server Overriding Mechanism"]]
/!\ [[!tag open_issue_documentation]] Is this completely resolved by
-[[service_solahart_jakarta_selatan__082122541663/virtualization/remap_root_translator]]?
+[[open_issues/virtualization/remap_root_translator]]?
The main idea of the Hurd is that every user can influence almost all system
functionality ([[extensible_system|extensibility]]), by running private Hurd
@@ -62,7 +62,7 @@ starts with (1) as the simplest approach, perhaps augmenting it with (3) for
certain servers that don't work with (1) because of indirect invocation.
Veriant (5) has been discussed and implemented,
-[[service_solahart_jakarta_selatan__082122541663/virtualization/remap_root_translator]].
+[[open_issues/virtualization/remap_root_translator]].
This tasks requires some understanding of the Hurd internals, especially a good
understanding of the file name lookup mechanism. It's probably not too heavy on