Differences between current version and predecessor to the previous major change of Coda.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 12 | Last edited on Monday, May 15, 2006 12:40:48 pm | by CraigBox | |
| Older page: | version 8 | Last edited on Saturday, June 18, 2005 4:03:31 pm | by DanielLawson | Revert |
@@ -1,22 +1,21 @@
[Coda | http://www.coda.cs.cmu.edu/] is an Advanced NetworkFileSystem developed as a research project by the team which wrote [AFS]. [Coda] extends the FileSystem for DisconnectedOperation.
Some of [AFS]' developers noticed that caching lets it work quite well for a while in the face of loss of the connection except for issues when writes occur. [Coda] was to allow for scenarios like allowing a laptop with a [WLAN] connection wandering in and out of range to seamlessly synchronize all files (and notify the user of conflicts). The project was quite a success.
-Coda is supported well in the 2.6
[Kernel
] series and appears to be under active development. Currently it seems to be the only option for
a FileSystem
with support for DisconnectedOperation until [OpenAFS] supports this
as well
.
+A former developer of [
Coda] started
[Intermezzo
] as
a simpler implementation
with the goal of making Intermezzo
as fast as a local FileSystem
.
-As of May 2005 the website is horribly out of date, with many pages dating back to 2000 or earlier, however the [mailing list| http://www.coda.cs.cmu.edu/maillists/] is active and is the current authoritative source of documentation.
-
-A former developer of [Coda] started [Intermezzo] as a simpler implementation
.
+Coda is supported well in the 2.6 [Kernel] series and appears to be under active development. Currently it seems to be the only option for a FileSystem with support for DisconnectedOperation until [OpenAFS] supports this as well.
As of May 2005 the website is horribly out of date, with many pages dating back to 2000 or earlier, however the [mailing list| http://www.coda.cs.cmu.edu/maillists/] is active and is the current authoritative source of documentation.
----
-!!My experiences with setting up Coda.
+
+
!! My experiences with setting up Coda
Be wary of the documentation on the coda site, most of it is out of date enough to be horribly misleading. In mozilla use "View > Page Info" to check the modification date on any documentation you are interested in using, if it's older than a year or so, pretend it was 404 and completely ignore it!
I started with sarge machines running 2.6. Apparently 2.4 requires patching your kernel. The coda version in the 2.6 kernel tree is up to date, and, as an added bonus is usually compiled as a module by most kernels shipped by vendors.
-One of the best sources of up to date information other than the mailing list appears to be [http://telemann.coda.cs.cmu.edu/news.html].
+One of the best sources of up to date information other than the mailing list appears to be [http://telemann.coda.cs.cmu.edu/news.html], and the mirrors pages [http://www
.coda.cs.cmu.edu/mirrors.html]
I used the debian repositories to retrieve coda. Once again, be careful that you're not retrieving something that's horribly out of date. The repositories are mentioned in the above news list.
!! The Server
@@ -36,8 +35,10 @@
vice-setup should start the server, and everything should be running on the server.
!! The Client
The client requires a kernel module to run. This kernel module is very simple, mostly just forwarding requests for data to userspace, and therefore is very small and reliable. The main "brains" are in a userspace process.
+
+If you don't have the module compiled, no matter, just go add the module to your config, build it and install it, and load it. You shouldn't even need to reboot.
I installed it as:
<pre>
apt-get install coda-client
@@ -72,4 +73,8 @@
* RPC2 errors are often because the client and the server can't agree on what IP address each other is using. Check your forward and reverse DNS for problems.
* rpc2ping can be used to test connectivity of the client to the server.
* I've not yet got this working under gentoo, I don't yet know why.
* Everything is probably much much nice if you use kerberos for authentication.
+
+-----
+CategoryFileSystem%%%
+CategoryNetworkFileSystem
