From: "Sujal Shah" <sshah@progress.com>
To: linux-kernel@vger.kernel.org
Subject: Re: What is standing in the way of opening the 2.5 tree?
Date: 30 Oct 2001 16:59:25 -0500 [thread overview]
Message-ID: <1004479166.31041.13.camel@pcsshah> (raw)
In-Reply-To: <Pine.LNX.4.30.0110301335230.9312-100000@methlab.23.org>
In-Reply-To: <Pine.LNX.4.30.0110301335230.9312-100000@methlab.23.org>
[-- Attachment #1: Type: text/plain, Size: 2751 bytes --]
On Tue, 2001-10-30 at 16:39, lost wrote:
> sounds like more complication to me. i personally think both do a great
> job at getting the job done. sure there are problems with any source
> tree. but adding more version numbers and turning kernels over to other
> people doesnt seem like the solution for making anything more stable.
[SNIP]
For my .02, I completely disagree with you. I'll explain in a minute.
> On 30 Oct 2001, Thomas Hood wrote:
[SNIP]
> > Having suggested, this, I'll remind everyone that Linus
> > and Alan can do whatever the hell the like. Which is
> > what I like about Linux.
> >
This has to be a strength, to be honest. I'd take this further by
proposing something else.
<Flame Retardant Suit>
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.
So, while I don't appreciate "massive" VM changes in the middle of my
own testing and development :-), I always treat every new kernel
iteration as potentially "unstable" and operate on the "if it ain't
broke, don't fix it" principle on my daily use boxes (unless something
in a Linus or AC changelog looks too tempting ;-)
One can hope that the number of people reading this list plus those
keeping up with most kernel releases know what they're doing, and are a
far smaller number than those people running vendor supplied kernels and
installations. If this isn't true today, I hope it is true at some
point in the future.
Just my opinion,
Sujal
> > --
> > Thomas Hood
> >
> > -
> > 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/
> >
>
> ************************
> "If you want a picure of the future, imagine a boot smashing a human face"
> - 1984, George Orwell
> email: lost@23.org * website: http://www.23.org/~lost
> ************************
>
>
> -
> 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/
--
---- Sujal Shah ---- PSC Labs (Progress Software) ----
Now Playing: none
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-10-30 21:58 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 [this message]
2001-10-31 19:18 ` Michael Peddemors
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=1004479166.31041.13.camel@pcsshah \
--to=sshah@progress.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