public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Peddemors <michael@wizard.ca>
To: Sujal Shah <sshah@progress.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is standing in the way of opening the 2.5 tree?
Date: 31 Oct 2001 11:18:47 -0800	[thread overview]
Message-ID: <1004555927.11209.45.camel@mistress> (raw)
In-Reply-To: <1004479166.31041.13.camel@pcsshah>
In-Reply-To: <Pine.LNX.4.30.0110301335230.9312-100000@methlab.23.org>  <1004479166.31041.13.camel@pcsshah>

Full moon must be getting to me, I have to open my mouth, and howl my
opinion..

As a consultant, it seems a shame to open up a 2.5 UNTIL 2.4 is dead
stable.. When it comes to servers, I still have to recommend that my
clients stick to a 2.2 series..  Of course, I am subject to some deep
flames as well, but we defienlty aren't getting enough testing in the
-pre series each time..
So far, every 2.4.x release has followed with a series of OOPS, OOM
problems, last minite updates to the pre cycle that caused bugs..  The
2.4 series has changed So many fundamentals since 2.4.0 that it seems
more like it is still 2.3. under development.

Although a few vendors are supplying 2.4 kernels with relative success,
I cannot with good conscious say that my clients servers will be
bulletproof like the 2.2 series was..

(I say this as I just finished a work order for a new Oracle Server,
still on 2.2)

I am surely looking for the next in the 2.4 series, as it seems like we
are finally solidifying, but when I look at all of the reccomendations
for 'which 2.4' kernel to use, it is amazing at how many people are
recommending kernels or a -pre nature, or -ac - even -aa as the most
solid.. When I would expect to see everyone recommending a single
production Linus Kernel version.

Can we get a single 2.4 series kernel that has fully been tested before
moving on to even more fundamental changes?
> 
> To be honest, I think that any x.y.z kernel is "unstable."  As we move
> into a situation with an even larger installed base, I think you're
> going to see a third tier become more evident: a) unstable, b) stable,
> c) vendor supported.  Quite frankly, if I'm making recommendations to
> customers and clients for a linux installation, I typically recommend
> for them to go with a vendor supplied kernel and manage it through the
> vendor.
> 
> > Please read the FAQ at  http://www.tux.org/lkml/
-- 
"Catch the Magic of Linux..."
--------------------------------------------------------
Michael Peddemors - Senior Consultant
LinuxAdministration - Internet Services
NetworkServices - Programming - Security
Wizard IT Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com
--------------------------------------------------------
(604)589-0037 Beautiful British Columbia, Canada


  reply	other threads:[~2001-10-31 19:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30 21:11 What is standing in the way of opening the 2.5 tree? Thomas Hood
2001-10-30 21:39 ` lost
2001-10-30 21:59   ` Sujal Shah
2001-10-31 19:18     ` Michael Peddemors [this message]
2001-10-31 19:39       ` David Lang
2001-10-30 22:44 ` Alan Cox
2001-10-31  1:36   ` Mike Fedyk
  -- strict thread matches above, loose matches on Subject: below --
2001-10-27 21:51 Miles Lane
2001-10-28  5:04 ` Jeff Garzik
2001-10-28  5:46   ` David S. Miller
2001-10-29  1:58     ` Andreas Dilger
2001-10-30 18:29       ` Jan Kara
2001-10-30 23:03         ` Alan Cox
2001-10-31 13:19           ` Jan Kara
2001-10-28 11:28   ` Allan Sandfeld

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=1004555927.11209.45.camel@mistress \
    --to=michael@wizard.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshah@progress.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox