1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
|
[[!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
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
(See Wikipedia page for the meaning of [[!wikipedia "101_(term)"]].)
Not the first time that something like this is proposed...
# 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
many people who insist on picking a hard task; realizing that indeed it's
hard; and going into hiding
< antrik> we see that happen every couple of months
< cluck> maybe we need a "hurd 101"
< cluck> getting a teacher and setting up a regularly held "class" for hurd
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"
and "students", which, going by gsoc numbers, may not be all that
helpful)
< Tekk_> cluck: gsoc isn't an accurate indicator
< Tekk_> cluck: I'm not allowed to participate in gsoc but I'd join :P
< antrik> cluck: we don't need code monkeys... we need hackers
< Tekk_`> antrik: code monkeys involve into hackers
< 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
# IRC, freenode, #hurd, 2013-10-12
<ahungry> Hi all, can anyone expand on
https://www.gnu.org/software/hurd/contributing.html - if I proceed with
the quick start and have the system running in a virtual image, how do I
go from there to being able to start tweaking the source (and recompiling
) in a meaningful way?
<ahungry> Would I modify the source, compile within the VM and then what
would be the next step to actually test my new changes?
<braunr> ahungry: we use debian
<braunr> i suggest formatting your changes into patches, importing them
into debian packages, rebuilding those packages, and installing them over
the upstream ones
<ahungry> what about modifications to mach itself? or say I wanted to try
to work on the wifi drives - I would build the translator or module or
whatever and just add to the running instance of hurd?
<ahungry> s/drives/drivers
<braunr> same thing
<braunr> although
<braunr> during development, it's obviously a bit too expensive to rebuild
complete packages each time
<braunr> you can use the hurd on top of a gnumach kernel built completely
from upstream sources
<braunr> you need a few debian patches for the hurd itself
<braunr> a lot of them for glibc
<braunr> i usually create a temporary local branch with the debian patches
i need to make my code run
<braunr> and then create the true development branch itself from that one
<braunr> drivers are a a dark corner of the hurd
<braunr> i wouldn't recommend starting there
<braunr> but if you did, yes, you'd write a server to run drivers, and
start it
<braunr> you'd probably write a translator (which is a special kind of
server), yes
<ahungry> braunr: thanks for all the info, hittin the sack now but ill have
to set up a box and try to contribute
|