mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jread@semiotek.com (Justin Wells)
To: linux-kernel@vger.kernel.org
Subject: Re:  Re: Please tag tested releases of the 2.4.x kernel
Date: Sat,  1 Dec 2001 06:37:34 -0500 (EST)	[thread overview]
Message-ID: <20011201113734.5187E38329@fever.semiotek.com> (raw)


Christoph Hellwig <hch@ns.caldera.de> wrote:

>In article <20011130220451.9D5AD38326@fever.semiotek.com> you wrote:
>>
>> It would be great if on kernel.org there were a note indicating which 
>> releases of the linux kernel had been favourably received. 
>>
>> If you could organize a bit you could even mark a release as "TESTED",
>> or even "APPROVED". All it would mean is that after it had been out for
>> a week or two nobody found any really serious problems.

>Approved kernel are usually come in files ending in i386.rpm,
>ia64.rpm or .deb.

>Come on, no one expects stock kernel to be tested.  Distributors
>on the other hand spend a lot of effort on testing their releases,
>so go for a distribution kernel if you need something tested.  Really.

I'm sure I'm not the only one who would like to know which stock kernels 
are relatively stable, and which ones aren't. There must be at least two
more people, just like me, who wonder which stock kernel to use.

Just because I like to apply a few patches that my distributor doesn't 
ship doesn't mean that I want to play russian roulette with my system,
though I'm willing to risk the occasional bug or problem when
I compile my own kernel.

And the kernels on kernel.org *are* tested, by lots of people, by kernel 
developers, by lots of ordinary folks even. I bet right after theren's 
an announce on slashdot you see lots of traffic on the ftp/http sites.

After a week or two I bet you even have some pretty good idea which
stock kernels are relatively stable, and which ones have big issues.

The word "relatively" is important here, everyone knows that if you roll 
your own kernel you're facing some risks. But everyone also knows that 
for some of the stock kernels the risks are reasonable, and for some of
them the risks are unreasonable.

I'm not asking for any additional testing, I'm just asking someone to 
summarize the consensus about a kernel once it's been kicked around 
for a week or two.

Justin


             reply	other threads:[~2001-12-01 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01 11:37 Justin Wells [this message]
2001-12-01 12:00 ` Christoph Hellwig
2001-12-01 19:51 ` Colonel

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=20011201113734.5187E38329@fever.semiotek.com \
    --to=jread@semiotek.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®