Mark Richards wrote:
[...]
> I'll look into Coda, but ideally I wouldn't have to copy each file to the local
> workstation when I use it, only when it is reserved for editing. Also, I'd like to
> be able to store the local copy anywhere on the filesystem, if possible.
Worried your drive will fill up? The files copied to your
drive is merely copied as a "caching" operation. They
still seem to reside at the server - this is totally transparent.
And of course you can limit this caching - if too many files
is cached some is simply thrown away. (Or sent back
if they were changed.) They will be re-
loaded automatically if you ever need them again.
If you really want to store them where you want instead of
transparent access, why bother with a new FS at all?
(I believe coda lets you specify where the caching
will happen, if you have several partitions/drives)
Simply run a script that reserves the file (by using
the permission system) and *copy* it to
where you want. Check-in will consist of copying
the altered file back, and restore normal permissions.
You might even want to run a system like CVS, unless
there is some special reason for not doing that.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Nov 30 2001 - 21:00:30 EST