From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] second cut of tcl 9pvfs on sources/contrib/axel/tcl/9pvfs
Date: Wed, 22 Mar 2006 16:37:15 +0100 [thread overview]
Message-ID: <200603221537.k2MFbFn21020@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Sat, 18 Mar 2006 13:03:34 +0100." <200603181203.k2IC3Zp13318@zamenhof.cs.utwente.nl>
> first version, no auth, only reading, not even seek.
second version with auth and seek, still only reading.
> needs tcl 8.5 alfa/beta for 'chan create' support.
needs also tclDES (http://tcldes.sourceforge.net/).
the main-auth.tcl and main-no-auth.tcl
in the directory give some idea of how to use it.
todo:
- writing/creation/deletion
- some support to write simple servers
- better random number generator for auth
- better naming scheme for global tcl variables,
and maybe better tcl packaging?
- documentation
- ...
Axel.
next prev parent reply other threads:[~2006-03-22 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-18 12:03 [9fans] first " Axel Belinfante
2006-03-22 15:37 ` Axel Belinfante [this message]
2006-03-22 20:45 ` [9fans] second " 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=200603221537.k2MFbFn21020@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).