Return to BSD News archive
Newsgroups: comp.os.386bsd.questions,alt.filesystems.afs Path: sserve!newshost.anu.edu.au!munnari.oz.au!foxhound.dsto.gov.au!fang.dsto.gov.au!yoyo.aarnet.edu.au!news.adelaide.edu.au!news.cs.su.oz.au!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!vixen.cso.uiuc.edu!sdd.hp.com!apollo.hp.com!netnews From: sommerfeld@apollo.hp.com (Bill Sommerfeld) Subject: Re: Compressed filesystem? Sender: usenet@apollo.hp.com (Usenet News) Message-ID: <CMo466.KvJ@apollo.hp.com> Date: Mon, 14 Mar 1994 18:46:54 GMT References: <2lvsqt$qu8@nigel.msen.com> <BDC.94Mar14125523@blackjack.ai.mit.edu> Nntp-Posting-Host: snarfblatt.ch.apollo.hp.com Organization: Hewlett Packard, Chelmsford Site Lines: 32 In article <BDC.94Mar14125523@blackjack.ai.mit.edu>, Brian D. Carlstrom <bdc@blackjack.ai.mit.edu> wrote: >>>>>> Mark Taylor writes: >In article <2lvsqt$qu8@nigel.msen.com> mtaylor@max.cybernet.com (Mark Taylor) writes: > > Mark> BTW- is there any support for AFS in FreeBSD? I have heard of > Mark> an NFS shim that SGI has which takes care of mapping AFS calls > Mark> to NFS calls. > >AFS is pretty muched owned by Transarc at this point. They arent too >friendly about giving out their code from what i can tell. However, the >afs-nfs translator as it is called is free. i run it under NetBSD. its >not the most reliable thing, but i trust to read files from AFS AFS source licensees with a pet kernel hacker or two should have no technical difficulties porting Transarc's AFS implementation into a NetBSD or FreeBSD kernel (it's just a lot of grunt work, because the vnode switch is subtly different from everything else out there..). Last I heard Transarc allowed its source licensees to share modified AFS implementations, and I believe that includes ports to new architectures. In the past, Transarc allowed distribution of a free, but unsupported, binary-only, client-only Apollo port, derived from their source base. The ideal way to package this for *BSD would be as a kernel extension loaded via modload; the one problem is that the internal kernel interfaces tend to change frequently, so it would really have to be targeted at one of the fixed releases and not any of the *-current releases. - Bill