🚀 go-pugleaf

In article <7416@cbmvax.UUCP>, kevin@cbmvax.UUCP (Kevin Klop) writes:
>In article <3855@cps3xx.UUCP> porkka@frith.UUCP (Joe Porkka) writes:
>>Real question: Will there be an actuall ENV: handler as the
>>1.3 update manual says? If so, is it OK to make subdirectories? Is
>>it ok to make arbitrary files, possibly somewhat large files?
>>I guess the real question is: Will ENV: handler have a filesystem, or
>>will it be like PIPE:?
>
>ENV: will remain as an assign for the moment.

One thing to consider is to create a special sub-filesystem handler which
would take (as specified in the MountList) a filename somewhere, and it
would use the specified file to create a complete filesystem in that one
file, which would be much more adapted to small files.  It would be sort of
like an 'ARC' or 'ZOO' in a DOS handler, except with no compression.

What use would it be?  This would be great for things that require many
small variable-length files and even subdirectories.  BBSes come to mind
immediately.  Each user could have a subdirectory, and various files could
be stored in each subdirectory (stats, configuration, even received mail).
It could also be used for message directories.  Messages could be as long
as necessary, but short messages wouldn't use an entire 1K of disk space
(as it does on the AmigaDOS filesystems).

So, is anybody up for writing something like this?  I've been wanting to
for a while, but never found the time.

				Bryan

--

     _______________________________________
   _/   Bryan Ford - bryan@geo-works.uucp   \_
 _/  ..!utah-cs!caeco!i-core!geo-works!bryan  \_
/ ..!uunet!iconsys!caeco!i-core!geo-works!bryan \
\_____________Author: Chroma Paint______________/