[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HHG and newbie Hurd Hackers

From: Thomas Schwinge
Subject: Re: HHG and newbie Hurd Hackers
Date: Thu, 20 Sep 2007 17:59:43 +0200
User-agent: Mutt/1.5.11


On Tue, Sep 18, 2007 at 05:28:00PM -0500, R. Steven Rainwater wrote:
> "How to become a Hurd Hacker" tutorial

OK, no problem with starting such a thing.  There just has to be someone
to do it :-).  And, good news: parts of it already exist.

Some examples:

  * <http://www.bddebian.com/~wiki/hurd/contributing/>.
  * <http://www.bddebian.com/~wiki/microkernel/mach/gnumach/building/> --
    fairly complete and up-to-date.
  * <http://www.bddebian.com/~wiki/microkernel/mach/mig/building/> --
  * <http://www.bddebian.com/~wiki/hurd/building/> -- incomplete.
  * <http://www.bddebian.com/~wiki/hurd/debugging/> -- evolving.  For
    example, just yesterday I added

> that provides a step-by-step
> explanation of setting up a Hurd development box, [...]

> Should I create patches against the savannah CVS [...]

Might be good to add all these items you collected to the discussion
subpage of `hurd/contributing'.  Again, feel invited to create it.

> I've already found answers to some of these on #hurd but I'm afraid
> they'll get tired of me asking too many dumb questions eventually. :)

#hurd can be ``callous'', so don't worry about that.  The most
displeasing thing to happen is when people start ignoring you.  But it's
a long way.  ;-)

> Here's an example that explains this sort of stuff for new Linux
> hackers:
> http://www.linuxchix.org/content/courses/kernel_hacking/lesson0
> It goes through preparing the development environment, downloading and
> configuring the source, creating and submitting patches (including
> political considerations), and then goes into the technical stuff about
> the kernel code.

If that is a useful structure, then we can surely create something
analogous.  First the structure and then people can piece by piece fill
it with information.


Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]