public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Walp <faceprint@think.faceprint.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: John Alvord <jalvo@mbay.net>,
	David Relson <relson@osagesoftware.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Kernel Releases
Date: Sun, 25 Nov 2001 11:23:32 -0500	[thread overview]
Message-ID: <20011125112332.A13505@think.faceprint.com> (raw)
In-Reply-To: <Pine.LNX.4.20.0111242147500.26049-100000@otter.mbay.net> <m1d726zwdm.fsf@frodo.biederman.org>
In-Reply-To: <m1d726zwdm.fsf@frodo.biederman.org>

> Correctness means you can write a proof showing how it meats it's
> specifications.  Stability means something passes the test of time.
                                             ^^^^^^^^^^^^^^^^^^^^^^^
I think you hit the nail on the head here.  2.<even>.x kernels are not
stable, they are presumably stable.  Nothing is stable until it proves
itself.

If you run a hours-old kernel on a production machine, you will get
burned sooner or later.  If you run an hours-old kernel on a production
machine, and manage to reboot it so quickly, I start to wonder what kind
of "production" you're running.

Nathan

  reply	other threads:[~2001-11-25 16:22 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-25  4:27 Kernel Releases David Relson
2001-11-25  5:49 ` John Alvord
2001-11-25  6:34   ` CaT
2001-11-25 14:12   ` John Jasen
2001-11-26  7:15     ` John Alvord
2001-11-25 15:46   ` Eric W. Biederman
2001-11-25 16:23     ` Nathan Walp [this message]
2001-11-26 21:03     ` Bill Davidsen
2001-11-25 19:55 ` Phil Sorber
2001-11-26  9:22 ` Allan Sandfeld
2001-11-26 14:51   ` Ian Stirling
2001-11-26 15:02     ` Rik van Riel
2001-11-26 19:11       ` Ian Stirling
2001-11-26 19:55       ` vda
2001-11-26 20:42 ` Bill Davidsen
2001-11-27  4:21   ` Mike Fedyk
2001-11-27  9:50   ` Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2001-11-25  5:37 Dan Kegel
2001-11-25  9:25 ` Nathan Dabney
2001-11-25 10:24   ` Keith Owens
2001-11-25 13:34     ` Phil Howard
2001-11-25 19:03     ` Nathan Dabney
2001-11-26 10:46 Martin Knoblauch
2001-11-26 15:27 ` John Jasen
2001-11-26 20:36   ` Horst von Brand
2001-11-27  2:40     ` Gerhard Mack
2001-11-27 17:25 Dan Kegel
2001-11-27 17:36 ` François Cami
2001-11-27 17:38   ` Dan Kegel
2001-11-27 18:13     ` Vitaly Luban
2001-11-28 16:23     ` Horst von Brand
2001-11-28 19:17       ` Mike Fedyk
     [not found] <fa.dac7a7v.1hkofg8@ifi.uio.no>
2001-11-27 17:53 ` Giacomo Catenazzi
     [not found] <Pine.LNX.4.33.0111261807570.489-100000@mikeg.weiden.de>
2001-11-27 18:08 ` vda
2001-11-27 16:58   ` Mike Galbraith

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=20011125112332.A13505@think.faceprint.com \
    --to=faceprint@think.faceprint.com \
    --cc=ebiederm@xmission.com \
    --cc=jalvo@mbay.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=relson@osagesoftware.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