9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] any updated version of substfs?
Date: Tue,  9 Jul 2002 14:34:32 +0200	[thread overview]
Message-ID: <200207091234.g69CYWl18369@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Tue, 09 Jul 2002 13:37:12 +0200." <fe435dc5d40076d1d52345556954b371@plan9.escet.urjc.es>

[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]

> Someone sent me an early version of substfs.
> Is there an updated version of this?

I did. No, I don't have anything newer.
What you have is what I currently run.

It is still 'unfinished, unpolished'. (see below)

For those who missed my previous post about it, sort of a repost:
What it does? It sits between 'us' and a (remote) file server.
Its purpose is to do substitutions on file names in the 9p messages
to and from the (remote) file server.
Advantage of this approach: no need to adapt the (remote) file servers 
like u9fs), no need to adapt local stuff. Disadvantage: certainly
some performance loss.
Don't know whether the name substfs is correct, or whether something
like substsrv would be better.
For flexibility, to experiment, the substition rules are not built in.
Instead, on its command line it is given the names of two programs that
do back and forth translation. These translation programs just accept
a filename on stdin and output the translation on stdout.

The attached gzipped tar file contains the source and translation
scripts I currently use.

Inspiration and source code taken from multiple places
(u9fs? 9pcon,... see my previous post)

Status:
it still contains memory leaks, which may be one of the reasons for the
machine crash I mentioned in my earlier post of today, subject: Re: PGP)
Also, translation is not yet done for all 9p messages that would need it,
but that is easy enough to add.
Main real problem is that it might loose directory entries,
when reading directories, when translation of directory entry names
extend these such that the result no longer fits in a single 9p message.

Enjoy,
Axel.


[-- Attachment #2: substfs.tgz --]
[-- Type: application/octet-stream , Size: 3346 bytes --]

  reply	other threads:[~2002-07-09 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 11:37 Fco.J.Ballesteros
2002-07-09 12:34 ` Axel Belinfante [this message]
2002-07-09 12:41   ` Axel Belinfante

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200207091234.g69CYWl18369@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).