Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269674AbUICNJj (ORCPT ); Fri, 3 Sep 2004 09:09:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269663AbUICNJj (ORCPT ); Fri, 3 Sep 2004 09:09:39 -0400 Received: from e33.co.us.ibm.com ([32.97.110.131]:13482 "EHLO e33.co.us.ibm.com") by vger.kernel.org with ESMTP id S269674AbUICNJV (ORCPT ); Fri, 3 Sep 2004 09:09:21 -0400 Subject: Re: The argument for fs assistance in handling archives (was: silent semantic changes with reiser4) From: Dave Kleikamp To: Spam Cc: Paul Jakma , Alan Cox , Jamie Lokier , Linus Torvalds , Horst von Brand , Adrian Bunk , Hans Reiser , viro@parcelfarce.linux.theplanet.co.uk, Christoph Hellwig , fsdevel , Linux Kernel Mailing List , Alexander Lyamin aka FLX , ReiserFS List In-Reply-To: <142794710.20040903023906@tnonline.net> References: <20040826150202.GE5733@mail.shareable.org> <200408282314.i7SNErYv003270@localhost.localdomain> <20040901200806.GC31934@mail.shareable.org> <1094118362.4847.23.camel@localhost.localdomain> <20040902161130.GA24932@mail.shareable.org> <1835526621.20040903014915@tnonline.net> <1094165736.6170.19.camel@localhost.localdomain> <32810200.20040903020308@tnonline.net> <142794710.20040903023906@tnonline.net> Content-Type: text/plain Message-Id: <1094216718.2679.30.camel@shaggy.austin.ibm.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 03 Sep 2004 08:05:19 -0500 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1810 Lines: 52 On Thu, 2004-09-02 at 19:39, Spam wrote: > > > > On Fri, 3 Sep 2004, Spam wrote: > > >> Yes, some archive types can't be partially unzipped either. But my > >> point is that it wouldn't be transparent to the application/user in > >> the same way. > > > It doesnt matter whether it is transparent to the application. It can > > be the application which implements the required level of > > transparency. > > > User doesnt care what provides the transparency or how it's > > implemented. > > Indeed. I hope I didn't say otherwise :). Just that I think it will > be very difficult to have this transparency in all apps. You're missing the point. We don't need transparency in all apps. You can write an application to be as transparent as you want, but you don't need every app to to understand every file format. > Just > thinking of "nano file.jpg/description.txt" or "ls > file.tar/untar/*.doc". I don't do much image editting, but I'm sure there are applications that let you edit the description in a text file. You can even create a script that extracts it, runs nano, and puts it back into the jpeg. This works for me: tar -tf file.tar | grep '\.doc' There are userland tools that deal with hundreds of file formats. Use the tool you need, rather than try to have the kernel do everything. > Sure in some environments like Gnome it could > work, but it still doesn't for the rest of the flora of Linux > programs. Just choose the right program. tar groks tar files, not ls. -- David Kleikamp IBM Linux Technology Center - 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/