Erlang filesystem (was: Re: File versioning)

[Bengt Kleberg]

> From: Scott Lystig Fritchie <fritchie@REDACTED>
> To: erlang-questions@REDACTED
> Subject: Re: Erlang filesystem (was: Re: File versioning) 

...deleted

> ... we did such a thing.  It used TCP (and UNIX domain sockets, later)
> and Sun RPC.  Client applications spoke RPC to an Erlang I/O daemon
> (running on the same box).  The Erlang I/O daemon "knew" were files
> were really stored: their "real" path(s) on an NFS server(s)
> somewhere.  It knew if the file was replicated or not.  Though we
> never finished it, we had an icky draft of code that could
> transparently migrate files to new paths and/or new NFS servers in the
> event that the mapping of files -> {replication-mode, [NFS servers]}
> changed.
> 
> We stole open(2), read(2), write(2), close(2), chdir(2), unlink(2)
> ... everything file I/O related.  We could tell the difference between

i could be blinded by a very good pr effort, but i belive that 9p (or
styx) is better than nfs (simplified unix) semantics.


bengt