From owner-freebsd-hackers Tue Jan 5 17:13:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17506 for freebsd-hackers-outgoing; Tue, 5 Jan 1999 17:13:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17500 for ; Tue, 5 Jan 1999 17:13:14 -0800 (PST) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id UAA12204; Tue, 5 Jan 1999 20:12:36 -0500 (EST) (envelope-from witr@rwwa.com) Message-Id: <199901060112.UAA12204@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Alfred Perlstein cc: Robert Withrow , hackers@FreeBSD.ORG, witr@rwwa.com Subject: Re: 3.0-REL NFS interop problems redux In-reply-to: Your message of "Tue, 05 Jan 1999 17:24:52 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jan 1999 20:12:35 -0500 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bright@hotjobs.com said: :- as a workaround, have you tried: :- a) tcp mounts b) nfs 3 I can only mount the way that the AMD maps (which I don't control) mount. Our maps have about >1,000 different mount points and the maps work fine for SunOs, Solaris, Linux, Hpux, etc. People will laugh if I ask them to change the maps. :- c) cvsup'ing to a new -current (there was some problems with signals :- being delivered during NFS activity in -release) Not an option. I have to deploy a released version, with a possibly patched kernel. I'm not able to deploy a -current version. bright@hotjobs.com said: :- you also may want to look into the bugfixes that were done :- post-release Where can I found out about them? Thanks! --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message