
	Where results make sense

Topic: Coda file system

	InterMezzo (file system) - Wikipedia, the free encyclopedia
		InterMezzo is a distributed file system written for Linux, distributed with a GPL licence.
		An InterMezzo system consists of a server, which holds the master copy of the file system, and one or more clients with a cache of the file system.
		Distributed file serving, e.g., FTP or WWW servers could be mirrored in a remote location without needing to propagate files that are never accessed.
	en.wikipedia.org /wiki/InterMezzo_(file_system) (373 words)

	Coda (file system) - Wikipedia, the free encyclopedia
		Coda is a distributed filesystem, developed at Carnegie Mellon University since 1987, under the direction of Mahadev Satyanarayanan.
		It is based on an older version of AFS, a similar but in some aspects less advanced distributed file system.
		The emphasis of the Coda development appears to be on moving from a very good research project to a filesystem ready for production use.
	en.wikipedia.org /wiki/Coda_(file_system) (261 words)

	The Coda Distributed File System
		The Coda distributed file system is a state of the art experimental file system developed in the group of M. Satyanarayanan at Carnegie Mellon University.
		A system call is an operation through which a program asks the kernel for service: for example, when opening the file the kernel will want to do a lookup operation to find the inode of the file and return a file handle associated with the file to the program.
		Coda is a pretty minimalistic file system module: it keeps a cache of recently answered requests from the VFS, but otherwise passes the request on to the Coda cache manager, called Venus.
	www.coda.cs.cmu.edu /ljpaper/lj.html (3542 words)

	Coda (file system) (Site not responding. Last check: 2007-10-08)
		Coda is an experimental distributed file system, developed at Carnegie Mellon University since 1987, under the direction of M. Coda is an experimental distributed file system, developed at Carnegie Mellon University since 1987, under the direction of M.
		Coda is still under development, and the emphasis appears to be on moving from a very good research project to a useful filesystem ready for large-scale production use.
		The peace had been judged, with reason, system; and yet when it was made we found ourselves at a full stand.
	www.termsdefined.net /co/coda-(file-system).html (287 words)

	Coda File System (Site not responding. Last check: 2007-10-08)
		Coda is a distributed filesystem with its origin in AFS2.
		We believe that the system needs to be taken from its current status to a widely available system.
		The current activities with Coda are mostly aimed at making this very good file system widely available, and a network file system of choice.
	www.coda.cs.cmu.edu (167 words)

	The Coda File System (Site not responding. Last check: 2007-10-08)
		The Coda File System was developed at the Carnegie Mellon University from the late 80s on.
		The System is based on the Andrew File System [Morr86, Howard88] which (unlike NFS or RFS) allows for large networks and thousands of clients.
		Coda provides the same functionality but adds two distinct features: Servers can be replicated in order to avoid congestion and to reduce high traffic areas in the network.
	www.cs.ucsb.edu /%7Ematz/study/coda.html (1935 words)

	1999 USENIX Annual Technical Conference, June 6-11, 1999, Monterey, California, USA
		The Coda project began in 1987 with the goal of building a distributed file system that had the location transparency, scalability and security characteristics of AFS [11] but offered substantially greater resilience in the face of failures of servers or network connections.
		Coda pioneered the concept of disconnected operation and was the first distributed file system to provide this capability [13].
		Coda is implemented as a collection of substantial user level programs together with a small kernel module on the client which provides the necessary Coda file system interface to the operating system.
	www.usenix.org /events/usenix99/full_papers/braam/braam_html (3911 words)

	PVFS: Description
		For a parallel file system to be easily used, it must provide a name space that is the same across the cluster and it must be accessible via the utilities to which we are all accustomed.
		PVFS file systems may be mounted on all nodes in the same directory simultaneously, allowing all nodes to see and access all files on the PVFS file system through the same directory scheme.
		While the traditional mechanism of system calls for file access is convenient and allows for all applications to access files stored on many different file system types, there is overhead in accessing through the kernel.
	www.parl.clemson.edu /pvfs/desc.html (1366 words)

	The Coda Distributed File System \| Linux Journal
		The Coda distributed file system is a state-of-the-art experimental file system developed in the group of M.
		Coda is a fairly minimalistic file-system module: it keeps a cache of recently answered requests from the VFS, but otherwise passes the request on to the Coda cache manager, called Venus.
		The file is now an ordinary file on the local disk, and read/write operations to the file do not reach Venus but are (almost) entirely handled by the local file system (EXT2 for Linux).
	www.linuxjournal.com /article/2390 (3628 words)

	Coda File System User and System Administrators Manual: Unix Manual Pages
		The Coda failure emulation package consists of two pieces: a library of routines (libfail) that is linked in with each client and server, and a user interface program (filcon) that controls the behavior of the linked-in libraries.
		Column 2 specifies the directory of the Coda data tree which must be a local file system partition for optimal performance.
		Each file specified in it has its current date checked at the server, and a new copy of the file is fetched if the date does not match that on the control machine.
	coda.cs.cmu.edu /doc/html/manual-19.html (14020 words)

	Disconnected Operation in the Coda File System (Site not responding. Last check: 2007-10-08)
		The Coda paper was interesting, especially as it seems to have been the first of its kind.
		I think that the Coda needs a concept of "cache installation" which would allow system files (like apps) to be installed in a seperate cache from the user cache.
		For example, Coda could go so far as to email the users regarding the conflict and allow them to discuss and the execute some sort of choose command to choose which update to go with, or to discard both and create a new one...
	www.cs.princeton.edu /~yitzhakm/598e/coda.html (503 words)

	CS701 - File System Seminar
		In this seminar we will study the evolution in the design of specific file systems and investigate the issues that are of importance for the performance of these file systems.
		The systems that will be studied in detail are the Windows NT NTFS, the BSD UNIX fast file system, the Sprite Log Structured file system, NFS, the Andrew file system, Coda, as well as a number of more experimental file system architectures.
		There are projects available for the analysis of trace data of the NT file system, for the development of a NT cache manager simulator and for implementing and testing new algorithms within Windows NT.
	www.cs.cornell.edu /Info/Courses/Fall-97/CS701 (364 words)

	EXPLOITING WEAK CONNECTIVITY IN A DISTRIBUTED FILE SYSTEM.
		The design of distributed file systems has traditionally been based on an assumption of strong connectivity.
		The starting point of this work is disconnected operation, in which a file system client operates using data in its cache during server or network failures.
		The foundation of adaptivity in this system is the communications layer, which derives and supplies information on network conditions to higher system layers.
	quanterion.com /Documents/Documents.asp?ArgVal=751 (301 words)

	File Systems (Site not responding. Last check: 2007-10-08)
		Coda from CMU; Notes on reading The Coda Distributed File System.
		For now I am going to ignore the feature of file systems participating in update resolution, even while admitting that it might be strategic.
		Coda has some interesting ideas but they are not germane to the scheme afoot which seeks a virtual disk rather than a virtual file system.
	cap-lore.com /Software/fileSystems (236 words)

	DarwinCoda project (Site not responding. Last check: 2007-10-08)
		The DarwinCoda project aims to provide the missing bits and pieces for the Coda File system, that is, the missing bits and pieces for Darwin and MacOS X. The most important piece is the kernel extension needed to be able to use Coda.
		The Coda file system is a Reserarch project at the Carnegie-Mellon University.
		What use to be the most interesting thing with Coda is its ability to act like a decent distributed file system even when you are not connected to any networks, something that comes in handy for all those iBooks and PowerBooks.
	www.opendarwin.org /projects/DarwinCoda (676 words)

	[No title] (Site not responding. Last check: 2007-10-08)
		E.g., “Coda> File not found.” Editing/Updating: You can build a very primitive editor that would help you to change the contents and write the file (on client itself).
		The same 8 — 10 files may be considered as 1 volume, replicated, and stored in all the 3 servers.
		The documentation file should describe the design aspects of the program and mention whatever assumptions made in the program.
	www.utdallas.edu /~praba/f04/p3f04.doc (750 words)

	CS262A Reading Summary (Site not responding. Last check: 2007-10-08)
		Using caching to improve not only performance, but availability of remote file systems, is a novel idea.
		First, whole file, disk based persistent caching makes the data for disconnected operation readily available to the client machine.
		Resolving conflicts is hard with Coda, because the user needs to decide which version of the file to keep, while the modificaiton to files can be related to each other.
	www.eecs.berkeley.edu /~zf/cs262b/coda.htm (183 words)

	InterMezzo File System Home
		InterMezzo is a new distributed file system with a focus on high availability.
		Intersync is a new client server system that we have started to put together, it periodically polls the server and integrates any changes made into the client file system.
		InterMezzo was deeply inspired by the Coda File System, but totally re-designed and re-engineered.
	www.inter-mezzo.org (194 words)

	Coda (file system)
		Coda is a distributed file system, developed at Carnegie Mellon University since 1987, under the direction of M. Satyanarayanan.
		The emphasis of the Coda development appears to be on moving from a very good research project to a useful filesystem ready for large-scale production use.
		The Linux Virtual Server Project already recommends Coda for high availability applications.
	www.sciencedaily.com /encyclopedia/coda__file_system_ (219 words)

	Secunia - Vulnerability Report - Coda File System 6.x
		This is based on the most severe Secunia advisory, which is marked as "Unpatched" in the Secunia database.
		Also certain operating systems bundle a very large number of software packages and are therefore affected by many vulnerabilities that would be counted as a vulnerability in stand alone products for other operating systems / platforms.
		A vulnerability has been identified in Coda File System, which can be exploited by malicious people to cause a DoS (Denial of Service) on certain programs.
	secunia.com /product/1850?menu=repo (625 words)

	File Systems
		This is a most interesting project; the author has been benchmarking a file system that stores both inodes and data blocks as a balanced tree.
		Moreover, porting file system code from one operating system to another is almost as difficult as the first port.
		These proposals, however, advocated massive changes to existing operating system interfaces and existing file systems; operating system vendors and maintainers resist making any large changes to their kernels because of stability and performance concerns.
	cbbrowne.com /info/fs.html (3798 words)

	Coda and Odyssey (Site not responding. Last check: 2007-10-08)
		Coda and Odyssey are experimental systems built by the research group of Professor M.
		in the context of a distributed file system.
		Coda and Odyssey are building blocks of Aura, a new flagship project focusing on
	www.cs.cmu.edu /afs/cs/project/coda/Web/coda.html (134 words)

	Debian -- coda-server (Site not responding. Last check: 2007-10-08)
		This package provides the binaries to set up a Coda server.
		Note that the "experimental" distribution is not self-contained; missing dependencies are likely found in the "unstable" distribution.
		Common files for the Coda distributed file system
	packages.debian.org /experimental/misc/coda-server (168 words)

	File Systems (Site not responding. Last check: 2007-10-08)
		VERITAS - File System enhances the performance of traditional, enterprise-level UNIX file management systems.
		ReiserFS - Journalling file system for Linux based on balance tree algorithms.
		InterMezzo - a new distributed file system with a focus on high availability.
	www.peterindia.net /FileSystems.html (68 words)

	The arla project.
		Since AFS uses the Kerberos system for authentication, you really want to build Arla with Kerberos support.
		Coda is a forked of version of AFS that support disconnected and weakly connected mode better then AFS.
		XFS is a high-performance journaling file system from SGI.
	www.stacken.kth.se /projekt/arla (876 words)

	Lustre: scalable, secure, robust, highly-available cluster file system
		Lustre is a scalable, secure, robust, highly-available cluster file system.
		The central goal is the development of a next-generation cluster file system which can serve clusters with 10,000's of nodes, petabytes of storage, move 100's of GB/sec with state of the art security and management infrastructure.
		Cluster File Systems, Inc. Public Open Source releases of Lustre are made under the GNU General Public License.
	www.lustre.org (205 words)

	WebDAV Linux File System (davfs2) (Site not responding. Last check: 2007-10-08)
		Davfs2 is a Linux file system driver that allows you to mount a WebDAV server as a local disk drive.
		Davfs allows a remote Web server to be edited using standard applications that interact with the file system.
		You may also store them in a secrets file that is readable and writeable by the owning user only.
	dav.sourceforge.net (309 words)

	Debian -- coda-doc (Site not responding. Last check: 2007-10-08)
		Users of experimental packages are encouraged to contact the package maintainers directly in case of problems.
		It has been developed at CMU by the systems group of M. Satyanarayanan in the SCS department.
		This package provides manual pages and documentation files.
	packages.debian.org /experimental/doc/coda-doc (157 words)

Try your search on: Qwika (all wikis)