Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/sys/coda
History
jmmv 2a3e5eeb7c Apply the NFS exports list rototill patch: 
- Remove all NFS related stuff from file system specific code.
- Drop the vfs_checkexp hook and generalize it in the new nfs_check_export
  function, thus removing redundancy from all file systems.
- Move all NFS export-related stuff from kern/vfs_subr.c to the new
  file sys/nfs/nfs_export.c.  The former was becoming large and its code
  is always compiled, regardless of the build options.  Using the latter,
  the code is only compiled in when NFSSERVER is enabled.  While doing this,
  also make some functions in nfs_subs.c conditional to NFSSERVER.
- Add a new command in nfssvc(2), called NFSSVC_SETEXPORTSLIST, that takes a
  path and a set of export entries.  At the moment it can only clear the
  exports list or append entries, one by one, but it is done in a way that
  allows setting the whole set of entries atomically in the future (see the
  comment in mountd_set_exports_list or in doc/TODO).
- Change mountd(8) to use the nfssvc(2) system call instead of mount(2) so
  that it becomes file system agnostic.  In fact, all this whole thing was
  done to remove a 'XXX' block from this utility!
- Change the mount*, newfs and fsck* userland utilities to not deal with NFS
  exports initialization; done internally by the kernel when initializing
  the NFS support for each file system.
- Implement an interface for VFS (called VFS hooks) so that several kernel
  subsystems can run arbitrary code upon receipt of specific VFS events.
  At the moment, this only provides support for unmount and is used to
  destroy NFS exports lists from the file systems being unmounted, though it
  has room for extension.

Thanks go to yamt@, chs@, thorpej@, wrstuden@ and others for their comments
and advice in the development of this patch.
 		2005-09-23 12:10:31 +00:00
..
00READ insert newlines to the MAKEDEV section, so that it's more clear 2002-12-26 13:20:44 +00:00
README
…
TODO
…
cnode.h nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda.h coda inodes are still 32 bits. Don't use ino_t in coda_open_out. 2005-08-28 08:57:45 +00:00
coda_io.h nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda_kernel.h nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda_namecache.c * Remove __P() 2005-08-30 22:24:11 +00:00
coda_namecache.h nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda_opstats.h nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda_pioctl.h nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda_psdev.c oops, fix previous. 2005-08-30 22:27:16 +00:00
coda_subr.c * Remove __P() 2005-08-30 22:24:11 +00:00
coda_subr.h nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda_venus.c nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda_venus.h nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda_vfsops.c Apply the NFS exports list rototill patch: 2005-09-23 12:10:31 +00:00
coda_vfsops.h nuke trailing whitespace 2005-02-26 22:58:54 +00:00
coda_vnops.c * Remove __P() 2005-08-30 22:24:11 +00:00
coda_vnops.h * Remove __P() 2005-08-30 22:24:11 +00:00
files.coda update for the protocol used by coda>=6, 2003-08-27 17:49:48 +00:00

README 

                Announcing the Availability of the
                        Coda Distributed
                           Filesystem
                              for
                         BSD Unix Systems

        Coda is a distributed file system like NFS and AFS.  It is
freely available, like NFS.  But it functions much like AFS in being a
"stateful" file system.  Coda and AFS cache files on your local
machine to improve performance.  But Coda goes a step further than AFS
by letting you access the cached files when there is no available
network, viz. disconnected laptops and network outages.  In Coda, both
the client and server are outside the kernel which makes them easier
to experiment with.

To get more information on Coda, I would like to refer people to
        http://www.coda.cs.cmu.edu
There is a wealth of documents, papers, and theses there.  There is
also a good introduction to the Coda File System in
        http://www.coda.cs.cmu.edu/ljpaper/lj.html

Coda was originally developed as an academic prototype/testbed.  It is
being polished and rewritten where necessary.  Coda is a work in
progress and does have bugs.  It is, though, very usable.  Our
interest is in making Coda available to as many people as possible and
to have Coda evolve and flourish.

The bulk of the Coda file system code supports the Coda client
program, the Coda server program and the utilities needed by both.
All these programs are unix programs and can run equally well on any
Unix platform.  Our main development thrust is improving these
programs.  There is a small part of Coda that deals with the kernel to
file system interface.  This code is OS specific (but should not be
platform specific).

Coda is currently available for several OS's and platforms:
        Freebsd-2.2.5: i386
        Freebsd-2.2.6: i386
	Freebsd -current: i386
        linux 2.0: i386 & sparc
        linux 2.1: i386 & sparc
        NetBSD 1.3: i386
	NetBSD -current: i386
The relevant sources, binaries, and docs can be found in
        ftp://ftp.coda.cs.cmu.edu/pub/coda/

We intend to come out with new Coda releases often, not daily.  We
don't want to slight any OS/platform not mentioned above.  We are just
limited in our resources as to what we can support internally.  We
will be happy to integrate OpenBSD support as well as other OS
support.  Also, adding platform support should be relatively easy and
we can discuss this.  The only difficulty is that Coda has a light weight
process package.  It does some manipulations in assembler which would
have to be redone for a different platform.

There are several mailing lists @coda.cs.cmu.edu that discuss coda:
coda-announce and linux-coda.  We are going to revise linux-coda to be
OS neutral, since it is mainly Coda we want to discuss.  We appreciate
comments, feedback, bug reports, bug fixes, enhancements, etc.