284c2b9aef
we no longer need to guard against access from hardware interrupt handlers. Additionally, if cloning a process with CLONE_SIGHAND, arrange to have the child process share the parent's lock so that signal state may be kept in sync. Partially addresses PR kern/37437. |
||
---|---|---|
.. | ||
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 |
$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.