public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Moore <timothymoore@bigfoot.com>
To: linux-kernel@vger.kernel.org
Cc: Bill Davidsen <davidsen@tmr.com>
Subject: Re: Breaking system configuration in stable kernels
Date: Tue, 09 Oct 2001 13:13:37 -0700	[thread overview]
Message-ID: <3BC35A71.9F783868@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1011008113808.27023A-100000@gatekeeper.tmr.com>

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.
>
> [cmpci module stuff]
> 
>   I love getting problems like this on my vacation, I'm pissed, and I
> really think it indicates a lack of attention to detail. I think I saw

I wouldn't use a new release of Windows or OSF/1 or Digital Unix or
Solaris in a commercial situation and linux is no different.  In this
case [cmpci] it sounds like some user's desktop which is also asking for
problems.  Having it visible to management is just too much risk
regardless of the os. 

Stick with distribution OR 2.2.x (2.2.19pre2 or higher) kernels.

rgds,
tim.
--

  parent reply	other threads:[~2001-10-09 20:14 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
2001-10-09 20:00 ` Tim Moore
2001-10-09 20:13 ` Tim Moore [this message]
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=3BC35A71.9F783868@bigfoot.com \
    --to=timothymoore@bigfoot.com \
    --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