All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: John Walsh <server422@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: What Distro is best for Starting Kernel Dev?
Date: Sat, 23 May 2009 11:44:11 -0400	[thread overview]
Message-ID: <4A1819CB.9010104@redhat.com> (raw)
In-Reply-To: <9f7f2c020905221910m2ffe4c53v8fd5dbc6cd236602@mail.gmail.com>

John Walsh wrote:
> What Distro is best for Starting Kernel Dev?

If you want to learn more about the system than
anybody should ever need to know, you can stick
with a bleeding-edge development distro like
Fedora Rawhide, Mandriva Cooker or Debian Unstable.

Make sure to always pull all the latest updates.

Sometimes you'll have a broken system which you'll
somehow have to untangle, but it's all part of
learning more than anybody should ever know...

-- 
All rights reversed.

  parent reply	other threads:[~2009-05-23 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23  2:10 What Distro is best for Starting Kernel Dev? John Walsh
2009-05-23  3:51 ` Justin Mattock
2009-05-23  8:24 ` Alan Cox
2009-05-23 15:44 ` Rik van Riel [this message]
2009-05-25 15:01   ` Jonathan Corbet
2009-05-25 15:16     ` Michael S. Zick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A1819CB.9010104@redhat.com \
    --to=riel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=server422@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.