From: Theodore Tso <tytso@mit.edu>
To: Robert Bradbury <robert.bradbury@gmail.com>
Cc: Thomas Backlund <tmb@mandriva.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: RFC: Updating the LKML bug reporting/updating framework
Date: Mon, 26 Oct 2009 10:56:37 -0400 [thread overview]
Message-ID: <20091026145637.GE13941@mit.edu> (raw)
In-Reply-To: <deaa866a0910260512p1eca02f6k89aa180aec27558d@mail.gmail.com>
On Mon, Oct 26, 2009 at 08:12:23AM -0400, Robert Bradbury wrote:
> I was unaware of the kernel.org bugzilla database. Sometimes people
> will go from AT&T UNIX to SGI IRIX to Linux without making a stop at
> kernel.org. If it comes on a CD and boots relatively easily people
> may not bother with such details. I think I started using Linux
> around the time I started using Mosaic and that may have been before
> the kernel.org site was as robust as it now appears to be (if it
> existed at all).
>
> Given the bugzilla database, is the LKML with its high volume and
> noise level (IMO), now largely obsolete [1]? (I think I a Google
> search may have led me in the direction that it was the place to
> report bugs).
Robert,
Most end users who use a Linux distribution will have a much better
time if they use the support channels (bugzilla, irc, web forums,
etc.) for their particular Linux distribution. So if you are using
Ubuntu, use the Ubuntu bugzilla and web forums. If you are using
Fedora, they have their own bugzilla and web forums. Debian users
have the Debian BTS (Bug Tracking System), as well as many mailing
lists (focused on debian newbies, debian developers, etc.)
The LKML and the kernel bugzilla are best used for people who are
working on the mainline Linux kernel, as opposed to the kernels which
have been snapshotted and customized for each distribution. Community
distributions, which tend to snapshot every six months, do tend to be
closer to mainline than Enterprise kernels (RHEL, SLES) that snapshot
every 24 months or so, but even some community distributions, such as
Ubuntu, do add a significant number of "value add" (and thus, bugs :-)
to their kernels.
There are also individual sublists for people who are only working on
a specific part of the kernel (i.e., the linux-ext4 mailing list, the
linux-scsi mailing list, etc).
- Ted
next prev parent reply other threads:[~2009-10-26 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 22:59 RFC: Updating the LKML bug reporting/updating framework Robert Bradbury
2009-10-25 23:32 ` Thomas Backlund
2009-10-26 12:12 ` Robert Bradbury
2009-10-26 13:12 ` Frans Pop
2009-10-26 14:56 ` Theodore Tso [this message]
2009-10-26 18:40 ` Stefan Richter
2009-10-27 6:44 ` Pavel Machek
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=20091026145637.GE13941@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.bradbury@gmail.com \
--cc=tmb@mandriva.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox