NetBSD

History

ad e3610f1886 kern/38135 vfs_busy/vfs_trybusy confusion The symptom was that sometimes file systems would occasionally not appear in output from 'df' or 'mount' if the system was busy. Resolution: - Make mount locks work somewhat like vm_map locks. - vfs_trybusy() now only fails if the mount is gone, or if someone is unmounting the file system. Simple contention on mnt_lock doesn't cause it to fail. - vfs_busy() will wait even if the file system is being unmounted.		2008-04-29 23:51:04 +00:00
..
README	…
TODO	…
cnode.h	…
coda.h	…
coda_io.h	…
coda_namecache.c	…
coda_namecache.h	…
coda_opstats.h	…
coda_pioctl.h	…
coda_psdev.c	kern/38135 vfs_busy/vfs_trybusy confusion	2008-04-29 23:51:04 +00:00
coda_subr.c	…
coda_subr.h	…
coda_venus.c	…
coda_venus.h	…
coda_vfsops.c	…
coda_vfsops.h	…
coda_vnops.c	…
coda_vnops.h	…
files.coda	…

README

$NetBSD: README,v 1.3 2007/04/08 13:50:51 gdt Exp $

Coda is a distributed filesystem.  It is derived from AFS, but
supports disconnected operation, both reading and writing.  This
directory contains the interface between the VFS layer and a
user-space program ("venus") that implements the client part of Coda.
The interface is similar to puffs(9) in many respects.

Coda servers do not need kernel support.

For information on Coda, see
  http://www.coda.cs.cmu.edu

As of April 2007, Coda is not quite stable enough for demanding
production use, but is usable by those who are willing to deal with
problems.  Help can be obtained via the list codalist@coda.cs.cmu.edu.

As of April 2007, pkgsrc/net/coda\* is old, and gdt recommends running
code from Coda's CVS.

As of April 2007, the kernel code has not been tested on 64-bit
architectures.  It runs on i386 and has previously been tested on
sparc.