Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S130013AbQLKTnL>; Mon, 11 Dec 2000 14:43:11 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S130029AbQLKTnC>; Mon, 11 Dec 2000 14:43:02 -0500
Received: from mailout01.sul.t-online.com ([194.25.134.80]:16910 "EHLO
	mailout01.sul.t-online.com") by vger.kernel.org with ESMTP
	id <S130013AbQLKTmy>; Mon, 11 Dec 2000 14:42:54 -0500
Message-ID: <3A352443.E3FEE114@sam-net.de>
Date: Mon, 11 Dec 2000 20:00:19 +0100
From: Dietmar Kling <dietmar.kling@sam-net.de>
X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.16 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Alexander Viro <viro@math.psu.edu>
CC: Martin Dalecki <dalecki@evision-ventures.com>,
        Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCE: Linux Kernel ORB: kORBit
In-Reply-To: <Pine.GSO.4.21.0012111306150.7433-100000@weyl.math.psu.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

> You do realize what "evolution" means? I'm not talking about the bugs
> in implementation. I'm talking about botched design. _That_ never gets
> fixed. Show me one example when that would happen and I might consider
> taking such possibility seriously.

That's what I am talking about in my "mean" attitude. Some things
must be  carried until the dead end. When there's no place to move
anymore than new things will evolve.
< short thinking >
As for your second point. Take libc5 and libc6. I really have no
*deep* insight. But I believe redesigning it for Multithreading
was mayor step.

Regards
Dietmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/