summaryrefslogtreecommitdiff
path: root/open_issues
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues')
-rw-r--r--open_issues/anatomy_of_a_hurd_system.mdwn15
-rw-r--r--open_issues/hurd_101.mdwn3
2 files changed, 18 insertions, 0 deletions
diff --git a/open_issues/anatomy_of_a_hurd_system.mdwn b/open_issues/anatomy_of_a_hurd_system.mdwn
index e1d5c9d8..64af3d00 100644
--- a/open_issues/anatomy_of_a_hurd_system.mdwn
+++ b/open_issues/anatomy_of_a_hurd_system.mdwn
@@ -71,3 +71,18 @@ IRC, freenode, #hurd, 2011-03-12
<antrik> well, it serves the root FS ;-)
<antrik> it also does some bootstrapping work during startup, to bring the
rest of the system up
+
+---
+
+Provide a cross-linked sources documentation, including generated files, like
+RPC stubs.
+
+ * <http://www.gnu.org/software/global/>
+
+---
+
+[[Hurd_101]].
+
+---
+
+More stuff like [[hurd/IO_path]].
diff --git a/open_issues/hurd_101.mdwn b/open_issues/hurd_101.mdwn
index 5c7031c9..6146885d 100644
--- a/open_issues/hurd_101.mdwn
+++ b/open_issues/hurd_101.mdwn
@@ -24,6 +24,9 @@ IRC, freenode, #hurd, 2011-07-25
noobs
< Tekk_> cluck: what would that include?
< cluck> explaining core concepts, giving out "homework" (small tasks), etc
+
+[[Anatomy_of_a_Hurd_system]].
+
< cluck> that way "the big guys" could focus on the hard stuff and have an
army of code monkeys at their disposal to write speced stuff
< cluck> (then again this idea would heavily depend on available "teachers"