From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 29 Jul 2001 07:03:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 29 Jul 2001 07:03:37 -0400 Received: from weta.f00f.org ([203.167.249.89]:16774 "HELO weta.f00f.org") by vger.kernel.org with SMTP id ; Sun, 29 Jul 2001 07:03:31 -0400 Date: Sun, 29 Jul 2001 23:04:07 +1200 From: Chris Wedgwood To: Matthew Gardiner Cc: Christoph Hellwig , kernel , Hans Reiser , Joshua Schmidlkofer Subject: Re: ReiserFS / 2.4.6 / Data Corruption Message-ID: <20010729230407.A3917@weta.f00f.org> In-Reply-To: <200107281645.f6SGjA620666@ns.caldera.de> <01072922193201.03891@kiwiunixman.nodomain.nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01072922193201.03891@kiwiunixman.nodomain.nowhere> User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Original-Recipient: rfc822;linux-kernel-outgoing On Sun, Jul 29, 2001 at 10:19:32PM +1200, Matthew Gardiner wrote: Just a little suggestion. Is it possible to offer "kernel binary upgrades" every other major release, for example, it shipped with 2.4.2, hence, the next upgrade to be release, 2.4.4 then 2.4.6 then 2.4.8. I can compile everthing however, I know a couple of people too scared to get down into the nitty gritty of Linux and compile their own kernel. Umm.. most (if not all) vendors provide kernel binary upgrades. If these are not frequent enough for your needs, you need to complain to them. --cw