From owner-freebsd-afs Mon Jan 25 16:36:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12707 for freebsd-afs-outgoing; Mon, 25 Jan 1999 16:36:27 -0800 (PST) (envelope-from owner-freebsd-afs@FreeBSD.ORG) Received: from hawkwind.ncsa.uiuc.edu (hawkwind.ncsa.uiuc.edu [141.142.21.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12698; Mon, 25 Jan 1999 16:36:24 -0800 (PST) (envelope-from koziol@hawkwind.ncsa.uiuc.edu) Received: (from koziol@localhost) by hawkwind.ncsa.uiuc.edu (8.9.2/8.9.2) id SAA03155; Mon, 25 Jan 1999 18:35:55 -0600 (CST) (envelope-from koziol) Message-Id: <199901260035.SAA03155@hawkwind.ncsa.uiuc.edu> Subject: AFS client with 3.0S To: freebsd-ports@FreeBSD.ORG, freebsd-afs@FreeBSD.ORG Date: Mon, 25 Jan 1999 18:35:55 -0600 (CST) From: koziol@ncsa.uiuc.edu Reply-To: koziol@ncsa.uiuc.edu X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-afs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Howdy, I had the AFS client in net/arla running on my 2.2.8-Stable machine, but the port is broken under 3.0-Stable. Has anyone tried it out or have any suggestions on fixing it? The compile is failing currently while building the LKM code. Thanks, Quincey Koziol koziol@ncsa.uiuc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-afs" in the body of the message From owner-freebsd-afs Wed Jan 27 17:01:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11401 for freebsd-afs-outgoing; Wed, 27 Jan 1999 17:01:59 -0800 (PST) (envelope-from owner-freebsd-afs@FreeBSD.ORG) Received: from telos.odyssey.cs.cmu.edu (TELOS.ODYSSEY.CS.CMU.EDU [128.2.185.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11395; Wed, 27 Jan 1999 17:01:57 -0800 (PST) (envelope-from jaharkes@telos.odyssey.cs.cmu.edu) Received: (from jaharkes@localhost) by telos.odyssey.cs.cmu.edu (8.8.7/8.8.7) id TAA03989; Wed, 27 Jan 1999 19:47:21 -0500 From: jaharkes@cs.cmu.edu Message-Id: <199901280047.TAA03989@telos.odyssey.cs.cmu.edu> Subject: Coda Distributed Filesystem 5.0.1 To: coda-announce@TELEMANN.coda.cs.cmu.edu, codalist@TELEMANN.coda.cs.cmu.edu, linux-fsdevel@vger.rutgers.edu, linux-kernel@vger.rutgers.edu, current-users@netbsd.org, port-i386@netbsd.org, current@FreeBSD.ORG, freebsd-afs@FreeBSD.ORG Date: Wed, 27 Jan 1999 19:47:21 -0500 (EST) Reply-To: codalist@TELEMANN.coda.cs.cmu.edu Content-Type: text Sender: owner-freebsd-afs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Coda Distributed File System, version 5.0.1 Coda is a distributed file system like NFS and AFS. It is freely available under the GPL. It functions somewhat 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. Coda also has read write replication servers. The Coda file server is outside the kernel and on the client theCoda cache manager Venus is again outside of the kernel, but on clients one needs a kernel module. To get more information on Coda, check out 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 and a Coda-HOWTO: http://www.coda.cs.cmu.edu/coda-howto.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: linux 2.0: i386 & sparc linux 2.2: i386 & sparc Freebsd-2.2.x: i386 Freebsd -current: i386 NetBSD 1.3x: i386 NetBSD -current: i386 There are also alpha releases for: Windows 95 -- Coda client Windows NT -- Coda server The relevant sources, binaries, and docs can be found in ftp://ftp.coda.cs.cmu.edu/pub/coda/ There are several mailing lists @coda.cs.cmu.edu that discuss coda: coda-announce and codalist. We appreciate comments, feedback, bug reports, bug fixes, enhancements, etc. Changes since our previous release are mostly to fix reported bugs. - A fully qualified domainname was not correctly recognized by clog. - The inet_aton function for Win95 handle non IP- addresses correctly. - New glibc libraries crashed on NULL args given to getservbyname. - egcs compilations were hit by a dangling else bug. - A bunch of compilation fixes. Please let us know about problems, since we will try to fix them right away. Compatibility with previous versions: - network protocol: can coexists with 4.6.7 and later - disk format client: can only coexists with 5.0pre1 - disk format for server: backward compatible The Coda Team ------------- Peter Braam Bob Baron Jan Harkes Marc Schnieder coda@cs.cmu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-afs" in the body of the message