Date: Tue, 11 Mar 1997 13:48:16 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Maybe a showstopper, maybe not. Message-ID: <19970311134816.TB12296@uriah.heep.sax.de> In-Reply-To: <1713.858063029@time.cdrom.com>; from Jordan K. Hubbard on Mar 10, 1997 22:50:29 -0800 References: <Pine.NEB.3.95.970310211652.24717A-100000@mail.cdsnet.net> <1713.858063029@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As Jordan K. Hubbard wrote: > I'd very much like to know if others can reproduce this - my only test > environment for NFS here involves other FreeBSD boxes, and they appear > to work just fine with NFS. If we've broken interoperability with > everything else, however, then you're definitely right about this > being a show-stopper - I wouldn't want to roll 2.2-RELEASE with a bug > of that magnitude in NFS. We are heavily relying on NFS on our machines at work, including a shared mount of /usr/local (from a FreeBSD 2.0.5 machine), and mounts of our homedirectories across FreeBSD 2.2 machines. They all work fine, and the only problem that came up at some point in time has been fixed. (A panic condition, i forgot what it has been.) I can also mount our Sun without problems. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970311134816.TB12296>