NetBSD

History

christos 020a6ad2d4 - move debugging functions to vcoda so modules with -DDEBUG link

- fix writing to coda files. this is probably not the right way to do
  this, but it satisfies the locking protocol:
	1. Sometimes coda_open() is called with an unlocked vnode which
	   does not satisfy the locking protocol. Lock it for now. We
	   need to find out why this happens
	2. VFS_VGET sometimes returns the container vnode unlocked. What
	   is the locking protocol for VFS_VGET? We also lock it here.

2012-08-02 16:06:58 +00:00

cnode.h

…

coda_io.h

…

coda_namecache.c

…

coda_namecache.h

…

coda_opstats.h

…

coda_pioctl.h

…

coda_psdev.c

…

coda_subr.c

…

coda_subr.h

…

coda_venus.c

…

coda_venus.h

…

coda_vfsops.c

…

coda_vfsops.h

…

coda_vnops.c

…

coda_vnops.h

…

coda.h

…

files.coda

…

README

…

TODO

…

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.