From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: Re: silent semantic changes with reiser4 Date: Tue, 7 Sep 2004 16:43:11 +1000 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <16701.22655.230704.534640@cse.unsw.edu.au> References: <200408311931.i7VJV8kt028102@laptop11.inf.utfsm.cl> <20040901194445.GM26192@nysv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Linus Torvalds , Horst von Brand , Pavel Machek , David Masover , Jamie Lokier , Chris Wedgwood , viro@parcelfarce.linux.theplanet.co.uk, Christoph Hellwig , Hans Reiser , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Alexander Lyamin aka FLX , ReiserFS List Return-path: Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.24]:51420 "EHLO note.orchestra.cse.unsw.EDU.AU") by vger.kernel.org with ESMTP id S267634AbUIGGoV (ORCPT ); Tue, 7 Sep 2004 02:44:21 -0400 To: mjt@nysv.org (Markus =?ISO-8859-1?Q?=20T=F6rnqvist?=) In-Reply-To: message from Markus =?ISO-8859-1?Q?=20T=F6rnqvist?= on Wednesday September 1 List-Id: linux-fsdevel.vger.kernel.org On Wednesday September 1, mjt@nysv.org wrote: > On Tue, Aug 31, 2004 at 01:05:40PM -0700, Linus Torvalds wrote: > > > >There's no point to having the kernel export information that is already > >inherent in the main stream. Having read this quote a few times in this thread I finally figured out what was wrong with it. It seems to imply that "iso9660" shouldn't be in the kernel. After all, it just exports information that is already in the underlying device. It doesn't provide any "mediate multiple access" benefit as a read-only filesystem doesn't require any mediation between users. It might provide some caching benefit, but I somehow don't think that is the reason that it is in the kernel. Now I'm happy to agree that there is a case for "iso9660" but not for "tarfs", but I don't think it is that "there's no point to having the kernel export information that is already [there]" NeilBrown