Re: plugin for cached network file system

[Hans Reiser <reiser@namesys.com>]

Michael James wrote:

>>>Michael James asked:
>>>
>>>How hard would it be to write a Reiser4 plug-in
>>>to implement a network file system with a cache on the local disk?
>>>      
>>>
>
>Then, On Thursday 13 May 2004 15:49, Hans Reiser wrote:
>
>  
>
>>It is easy to do a hack, and hard to do it right so that the world would 
>>want to drop nfs and move to it.  We are trying to find a sponsor to do 
>>it right, and have a proposal called Reiser5 that costs $1.8 million, 
>>and provides global scalability (which nfs/afs/clusterfs/intermezzo do 
>>not, in my view).
>>    
>>
>
>At this stage, I'm looking for the, "Don't worry, be scrappy" solution.
>
>1) Just kludge the basic functionality.
>	(read-only, file-fetching/flushing in sh or perl,
>	 NFS mounted master, manual deletion of outdated copies)
>
>2) Let time, necessity and the GPL refine it and add features.
>	(read-write-locking, automatic updating,
>	  built-in file fetching/flushing and network code)
>
>3) Always keeping an eye on 2) during 1).
>
>There doesn't seem to be anything like this in Linux, and having it
> would be a boon (and give reiser4 a leg-up) in the cluster community.
>
>michaelj
>
>
>  
>
I am very skeptical of the value of it (that is how NFS came about, just 
doing things quickly....), but to answer the question asked, it would be 
easy.