[Top][All Lists]

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

Re: httpfs, tarfs --help

From: Marcus Brinkmann
Subject: Re: httpfs, tarfs --help
Date: Sat, 22 Dec 2001 06:14:59 +0100
User-agent: Mutt/1.3.24i

On Fri, Dec 21, 2001 at 03:16:34PM +0100, Jeroen Dekkers wrote:
> 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.

You could only do this manually (well, cron job etc).

> 2) Use some special `extensions translator' which automatically sets
> translators for files with known extensions.

Yeah, this might be possible.  For a start, you could work on a filemux. 
Then you need to couple the translator to start by filemux to the file type.


`Rhubarb is no Egyptian god.' Debian http://www.debian.org brinkmd@debian.org
Marcus Brinkmann              GNU    http://www.gnu.org    marcus@gnu.org

reply via email to

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