[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: httpfs, tarfs --help

From: Jeroen Dekkers
Subject: Re: httpfs, tarfs --help
Date: Fri, 21 Dec 2001 15:16:34 +0100
User-agent: Mutt/1.3.24i

On Fri, Dec 21, 2001 at 01:39:39PM +0100, Marcus Brinkmann wrote:
> However, if you don't pass an argument to tarfs, it can assume that the tar
> file is what we call the underlying file of the translator.
> If you have a file /tmp/foo, you can put a translator on /tmp/foo while
> keeping the original file intact.  All normal file accesses go to the
> translator though, the file is "hidden", it lies under the translator
> (underlying file).  But the translator always gets a port to its underlying
> file, so it can access it.  This case is what I wanted to illustrate.

Is it possible to make that transparant? I.e. you can just cd into a
tarfile without using settrans first, because somethings detects the
tar.gz extensions and knows to run the tarfs translator on that.

I've been thinking about two ways to do that:
1) Set the translator field of every tarfile to /hurd/tarfs.
2) Use some special `extensions translator' which automatically sets
translators for files with known extensions.

I don't know if there are other ways to do it. I think it's nice to have
this feature. It looks a bit like how midnight commander (or the old
non-free norton commander for dos) handles tar (or zip) files.

Jeroen Dekkers
Jabber supporter - http://www.jabber.org Jabber ID: jdekkers@jabber.org
Debian GNU supporter - http://www.debian.org http://www.gnu.org
IRC: jeroen@openprojects.net

Attachment: pgpfZszm_Ushv.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]