linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: linas@austin.ibm.com
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Linas Vepstas <linas@linas.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Kernel Panic in 2.2.x
Date: Mon, 2 Jun 2003 11:47:16 -0500	[thread overview]
Message-ID: <20030602114716.C36746@forte.austin.ibm.com> (raw)
In-Reply-To: <E985F997-9509-11D7-BBCD-000A95A0560C@us.ibm.com>; from hollisb@us.ibm.com on Mon, Jun 02, 2003 at 09:53:03AM -0500


On Mon, Jun 02, 2003 at 09:53:03AM -0500, Hollis Blanchard wrote:
>
> However, don't complain that upgrading your system can make things
> break and ask me for sympathy. :) I for one would rather spend my time
> making things work than making things backwards-compatible back to

Well, part of the problem is, of course, that things that used to
work in old versions sometimes don't work in newer versions.  No
one will argue that 'making things work' isn't a good intention,
but, by itself, it is not enough to make an effective process.

Everyone has good intentions, but accidents still happen.  You say
that you want to drive 100 mph, and you think I'm saying 'everyone
must drive 55 mph'.  That's not what I'm saying.  I'm trying to talk
about what it takes to drive 100 mph *safely*.

> version 0.3. I guess you're trying to convince me of the exact
> opposite, but IMHO there's simply too much stuff left to get working.
> Once it all works

Surely, you know that that day will never, ever come!  You do understand
that, don't you?

> then we can talk about

That's like saying "once we have eliminated all wars and killing,
only then shall we start to think about medicine and health care!"

> backwards-compatibility... ;)

I don't think you understood what I'm saying.  Its not about backwards
compatibility.  Backwards-compat can help, but its *NOT* what I'm
talking about.   Did I actually use the words 'backwards compatible'
anywhere in any of my series of notes on this topic?  I don't think so!

Part of what I'm talking about is technology, like having an installer
that allows you install the new version without trashing the old version,
so that the new version can be backed out if it doesn't work.  I think
AIX has an installer like this (I've never used it).  Linux doesn't.

Part of what I'm talking about is a change of attitude, such as the
idea that maintaining and patching the 2.2 kernel is wrong.  It's
not wrong, and there are some very good technical reasons for
maintaining this kernel/code base.

--linas


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-06-02 16:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 16:11 Kernel Panic in 2.2.x Hawkins Jeffrey-CJH016
2003-05-30 16:20 ` Hollis Blanchard
2003-05-30 16:34   ` linas
2003-05-30 16:40     ` Hollis Blanchard
2003-05-30 21:48       ` linas
2003-05-30 22:11         ` Hollis Blanchard
2003-05-31  0:58         ` Linas Vepstas
2003-06-02 14:53           ` Hollis Blanchard
2003-06-02 16:47             ` linas [this message]
2003-06-03 22:01           ` Remote serial console through USB daRonin
  -- strict thread matches above, loose matches on Subject: below --
2003-05-30 22:47 Kernel Panic in 2.2.x Hawkins Jeffrey-CJH016
2003-05-29 19:04 Hawkins Jeffrey-CJH016

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=20030602114716.C36746@forte.austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=hollisb@us.ibm.com \
    --cc=linas@linas.org \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).