Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S292384AbSBYW6z>; Mon, 25 Feb 2002 17:58:55 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S292382AbSBYW6q>; Mon, 25 Feb 2002 17:58:46 -0500
Received: from quechua.inka.de ([212.227.14.2]:27756 "EHLO mail.inka.de")
	by vger.kernel.org with ESMTP id <S292378AbSBYW6g>;
	Mon, 25 Feb 2002 17:58:36 -0500
From: Bernd Eckenfels <ecki-news2002-02@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18
In-Reply-To: <20020225215452.GB27211@matchmail.com>
X-Newsgroups: ka.lists.linux.kernel
User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (Linux/2.0.39 (i686))
Message-Id: <E16fU4l-0002D4-00@sites.inka.de>
Date: Mon, 25 Feb 2002 23:58:31 +0100
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

In article <20020225215452.GB27211@matchmail.com> you wrote:
> The only binaries that are affected are ones compiles without shared
> libraries on some non-x86 arches, and anyone doing that should know what
> they are doing and which kernels to use.

Sorry, I dont see a reason to treat any architecture different. And static
apps are quite common on install and rescue systems.

> Does anyone know how long this bug has been in the kernel?

What is so bad about releasing a final kernel which matches the RC? I mean we
could have the chance to do it with 2.4.19

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