summaryrefslogtreecommitdiff
path: root/open_issues/hurd_101.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/hurd_101.mdwn')
-rw-r--r--open_issues/hurd_101.mdwn25
1 files changed, 23 insertions, 2 deletions
diff --git a/open_issues/hurd_101.mdwn b/open_issues/hurd_101.mdwn
index 6146885d..574a03ec 100644
--- a/open_issues/hurd_101.mdwn
+++ b/open_issues/hurd_101.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2011, 2013 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -12,7 +12,8 @@ License|/fdl]]."]]"""]]
Not the first time that something like this is proposed...
-IRC, freenode, #hurd, 2011-07-25
+
+# IRC, freenode, #hurd, 2011-07-25
[failed GNU/Hurd project]
< antrik> gnu_srs1: I wouldn't say he was on track. just one of the many
@@ -39,3 +40,23 @@ IRC, freenode, #hurd, 2011-07-25
< Tekk_`> under the right conditions
< cluck> antrik: jokes aside some sort of triage system/training ground for
newcomers could be helpful
+
+
+# IRC, freenode, #hurd, 2013-01-20
+
+ <zacts> so once I have written my first translators, and really understand
+ that, what kinds of projects would you recommend to an operating
+ systems/hurd newbie.
+ <zacts> I am reading the minix book now as I have it, but I'm waiting on
+ getting the modern operating systems book by the same author.
+ <zacts> I was initially going to start working on minix, but their focus
+ seems to be on embedded, and I want to work on a system that is more
+ general purpose, and I like the philosophy of freedom surrounding the
+ hurd.
+ <zacts> I like how the hurd design allows more freedom for users of the
+ operating system, but I would also like to incorporate ideas from minix
+ on the hurd. mainly, rebootless updates of servers/translators.
+ <neal> then you should study how translators work
+ <neal> how ipc works
+ <neal> and understand exactly what state is stored where
+ <zacts> ok