From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Breaking system configuration in stable kernels
Date: Thu, 11 Oct 2001 14:15:28 -0400 [thread overview]
Message-ID: <200110111815.f9BIFSZ17993@deathstar.prodigy.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1011009151209.3636A-100000@chaos.analogic.com>
In article <Pine.LNX.3.95.1011009151209.3636A-100000@chaos.analogic.com>
root@chaos.analogic.com wrote:
| As I see it, you get the chance to complain about some poor performance
| because you don't have anything to compare present performance against.
| So, you upgrade to a minimally-tested kernel and complain that it's
| not a "viable candidate for default o/s..." -your words. Guess what,
| this complaint will always fall upon deaf ears.
|
| What will help get your bleeding-edge kernel stable, is a bug report,
| a performance report, and sometimes even a "Hey... This one works great!".
|
| Don't ever expect the kernel's internals to remain constant. This means
| that you will have to modify any of your custom modules for each and
| every kernel you download.
|
| You can expect the API to remain constant. If it doesn't you have
| a valid beef. Otherwise, you will be talking to the forest.
There seems to be confusion about the meaning of "stable." The stable
kernel series should be getting bug fixes, and the untested changes
should go into the development (like 2.5) series where no one would
expect it to be stable.
There should be no bleeding edge stable kernels, my point exactly. As
long as Linux behaves like a hacker's dream it will be perceived as
such. When a stable kernel is released someone interested in reliable
operation should take it over. We should not have "oh, shit, don't use"
stable versions. For all the new features, the -ac kernels have
consistently been more stable, because, as Alan says, "I run these
kernels on my machines" and they behave like it.
| Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
|
| I was going to compile a list of innovations that could be
| attributed to Microsoft. Once I realized that Ctrl-Alt-Del
| was handled in the BIOS, I found that there aren't any.
Microsoft has actually had two good ideas; the software floating
point in the FORTRAN compiler for the 8080 CP/M system (one extra bit
of precision) and MS-CHAP to prevent clear text passwords from passing
on the net. Can't think of anything else which impressed me...
--
bill davidsen <davidsen@tmr.com>
"If I were a diplomat, in the best case I'd go hungry. In the worst
case, people would die."
-- Robert Lipe
next prev parent reply other threads:[~2001-10-11 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01Oct8.234022edt.62391@gpu.utcc.utoronto.ca>
2001-10-09 18:55 ` Breaking system configuration in stable kernels Bill Davidsen
2001-10-09 19:30 ` Richard B. Johnson
2001-10-11 18:15 ` bill davidsen [this message]
2001-10-11 20:54 ` Doug McNaught
2001-10-12 2:18 ` Horst von Brand
[not found] <007e01c152c7$2f7d39b0$1a01a8c0@allyourbase>
2001-10-15 21:43 ` Bill Davidsen
2001-10-08 15:54 Bill Davidsen
2001-10-08 19:35 ` Kain X
2001-10-09 20:00 ` Tim Moore
2001-10-09 20:13 ` Tim Moore
2001-10-15 22:19 ` Bill Davidsen
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=200110111815.f9BIFSZ17993@deathstar.prodigy.com \
--to=davidsen@tmr.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