From: Mark Richards <richard@ecf.utoronto.ca>
To: Helge Hafting <helgehaf@idb.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multiplexing filesystem
Date: Tue, 27 Nov 2001 09:45:22 -0500 [thread overview]
Message-ID: <3C03A702.EBE823C9@ecf.utoronto.ca> (raw)
In-Reply-To: <3C030FB4.C3303BE4@ecf.utoronto.ca> <3C036A83.F23E6EBE@idb.hist.no>
Helge Hafting wrote:
>
> Coda already do what you want:
> Files are kept on a server, and copied to your local disk when
> you use it. You may even disconnect when working on the local
> copy - your changes will be propagated back to the server
> whenever you reconnect to the network.
> The copying is indeed completely transparent.
>
> If you need reservation - use the permission system.
> A suid program simply makes _you_ owner, and only
> the owner gets write permission. This is your check-out
> program. Check-in consists of changing ownership
> back to root (or some userid allocated to the versioning system)
>
> Helge Hafting
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.
Mark
next prev parent reply other threads:[~2001-11-27 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 3:59 Multiplexing filesystem Mark Richards
2001-11-27 4:34 ` Jeff V. Merkey
2001-11-27 4:39 ` Jeff V. Merkey
2001-11-27 7:38 ` James Davies
2001-11-28 0:34 ` Pavel Machek
2001-11-27 10:27 ` Helge Hafting
2001-11-27 14:45 ` Mark Richards [this message]
2001-11-27 19:37 ` Mike Fedyk
2001-11-28 11:11 ` Helge Hafting
2001-11-29 1:56 ` Mark Richards
2001-11-27 15:15 ` Eli Carter
2001-11-27 23:39 ` Blake Barnett
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=3C03A702.EBE823C9@ecf.utoronto.ca \
--to=richard@ecf.utoronto.ca \
--cc=helgehaf@idb.hist.no \
--cc=linux-kernel@vger.kernel.org \
/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