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. Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED] Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.marcus-brinkmann.de _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
