From: "Michael S. Zick" <lkml@morethan.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Rik van Riel <riel@redhat.com>, John Walsh <server422@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: What Distro is best for Starting Kernel Dev?
Date: Mon, 25 May 2009 10:16:43 -0500 [thread overview]
Message-ID: <200905251016.46366.lkml@morethan.org> (raw)
In-Reply-To: <20090525090112.3919d117@bike.lwn.net>
On Mon May 25 2009, Jonathan Corbet wrote:
> On Sat, 23 May 2009 11:44:11 -0400
> Rik van Riel <riel@redhat.com> wrote:
>
> > 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.
>
> I do the bulk of my work on such distributions, but if you're really
> wanting to get started with *kernel* development, there is one thing to
> be aware of: development distributions can be an independent source of
> instability/weirdness in a system. If you're at an early stage with the
> kernel, you may want to minimize the number of variables which can be
> changing at once. So it might make more sense to base your work on a
> distribution which is not changing underneath you.
>
One of the major "outside" variables is the tool-chain you use - -
For that reason, I suggest you use one of the "Build From Source"
distributions. At least you know your tool chain is working. ;)
Personally, I use both 32-bit and 64-bit Gentoo.
Also, I avoid doing any updates that would change the tool chain
while in the midst of trouble shooting something.
Just keep your hands off of the --update button. ;)
Currently (both flavors, 32/64):
gen2-32# gcc-config -l
[1] i686-pc-linux-gnu-4.1.2 *
[2] i686-pc-linux-gnu-4.3.2
The 4.1.2 tool chain is "good" across the board for all Gentoo archs.
The 4.3.2 tool chain is not marked as "good" for hp-parisc.
Mike
> jon
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
prev parent reply other threads:[~2009-05-25 15:16 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
2009-05-25 15:01 ` Jonathan Corbet
2009-05-25 15:16 ` Michael S. Zick [this message]
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=200905251016.46366.lkml@morethan.org \
--to=lkml@morethan.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--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.