Date: Mon, 19 Dec 2005 22:16:43 -0500 From: "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-current@freebsd.org Subject: Re: "Native" journaling file systems? Message-ID: <8A3BB8D9-9270-4265-89CD-BBFB3154FA93@ece.cmu.edu> In-Reply-To: <p0623092dbfcd264ee25e@[128.113.24.47]> References: <1263.193.231.237.171.1135037978.squirrel@dummy-host.example.com> <E47CD3DB-71A4-464E-8CCC-F0492BF0A4A1@ece.cmu.edu> <43A76A95.2070402@mac.com> <p0623092dbfcd264ee25e@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 19, 2005, at 10:14 , Garance A Drosihn wrote: > At 9:21 PM -0500 12/19/05, Chuck Swiger wrote: >> Brandon S. Allbery KF8NH wrote: >> [ ... ] >>> (No production FreeBSD: we absolutely *need* AFS clients, and >>> none of us is enough of a kernel-level hacker to make OpenAFS >>> or Arla sufficiently stable. *grumble*) >> >> You ought to be able to NFS-export an AFS volume mounted on a Sun >> box to FreeBSD clients. That worked fine at CMU, anyway, but >> there were plenty of people with significant AFS-mojo available >> there, too. > > Ugh. We did NFS-exporting of AFS volumes early on, and it caused > us no end of headaches. We were very glad to abandon that setup, > and stick with native AFS clients. Yeh, I've used tha AFS-NFS translator and knfs to bootstrap new systypes. Not about to do that for general use. -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8A3BB8D9-9270-4265-89CD-BBFB3154FA93>