From: Kain X <kain@kain.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Breaking system configuration in stable kernels
Date: 08 Oct 2001 13:35:22 -0600 [thread overview]
Message-ID: <1002569722.1733.3.camel@noir> (raw)
In-Reply-To: <Pine.LNX.3.96.1011008113808.27023A-100000@gatekeeper.tmr.com>
In-Reply-To: <Pine.LNX.3.96.1011008113808.27023A-100000@gatekeeper.tmr.com>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Mon, 2001-10-08 at 09:54, Bill Davidsen wrote:
> I've beaten this dead horse before, but Linux will not look to
> management like a viable candidate for default o/s until whoever releases
> new versions of *stable* kernel series with cosmetic changes which break
> existing systems running earlier releases of the same stable kernel
> series.
This is why there are *distributions*. If you're going to be upgrading
straight from the devloper's mouth, you should be prepared to check for
these errata *when you upgrade*. I don't recall seeing any kernel
document that guarantees stability for anything but base APIs in any
(pure) kernel distribution I have ever seen.
--
The Internet interprets censorship as damage and routes around it.
-- John Gilmore
**
Amateur Nuclear Specialist
Bryon Roche, Kain <kain@imperativesoultions.com>
<kain@kain.org>
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-10-08 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 15:54 Breaking system configuration in stable kernels Bill Davidsen
2001-10-08 19:35 ` Kain X [this message]
2001-10-09 20:00 ` Tim Moore
2001-10-09 20:13 ` Tim Moore
2001-10-15 22:19 ` Bill Davidsen
[not found] <01Oct8.234022edt.62391@gpu.utcc.utoronto.ca>
2001-10-09 18:55 ` Bill Davidsen
2001-10-09 19:30 ` Richard B. Johnson
2001-10-11 18:15 ` bill davidsen
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
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=1002569722.1733.3.camel@noir \
--to=kain@kain.org \
--cc=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