From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: silent semantic changes with reiser4 Date: Thu, 26 Aug 2004 16:54:09 -0700 Message-ID: <412E7821.7020100@namesys.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andrew Morton , Spam , wichert@wiggy.net, jra@samba.org, torvalds@osdl.org, hch@lst.de, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, flx@namesys.com, reiserfs-list@namesys.com Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com To: Rik van Riel In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org Rik van Riel wrote: >On Thu, 26 Aug 2004, Andrew Morton wrote: > > > >>All of which can be handled in userspace library code. >> >>What compelling reason is there for doing this in the kernel? >> >> > >There's a compelling reason to do it in userspace. If an >unaware program copies or moves such a file with streams >inside, it doesn't break the streams and aware programs will >continue to see them. > >OTOH, if we had the streams in the kernel, unaware applications >would continuously break the metadata and streams that the >streams aware programs expect ! > > > Well, first off, you don't want streams in the kernel, you want all the little pieces that can be composed together into a stream if you so choose. Streams are ugly, the pieces are all cool.