*BSD News Article 82195


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!newsrelay.netins.net!newsfeed.dacom.co.kr!arclight.uoregon.edu!news.sprintlink.net!news-peer.sprintlink.net!uunet!in3.uu.net!news.artisoft.com!usenet
From: Terry Lambert <terry@lambert.org>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Using FreeBSD as a File Server to Solaris Clients?
Date: Sun, 03 Nov 1996 16:01:29 -0700
Organization: Me
Lines: 55
Message-ID: <327D2449.6041BBC0@lambert.org>
References: <55bq2i$n2o@fidoii.cc.lehigh.edu> <55dq9q$ovi@netaxs.com>
NNTP-Posting-Host: hecate.artisoft.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.01 (X11; I; Linux 1.1.76 i486)

A. Karl Heller wrote:
] 
] Stephen Corbesero (flash@EECS.Lehigh.EDU) wrote:
] : I have such a setup, and I am getting error messages (on the Solaris
] : machines) about "no file locking, upgrade server software".
] : Everything seems okay otherwise.
] 
]   I'm going to want to do the same thing soon.  I am not sure,
] but I don't think FreeBSD supports NFS 3.0.  Solaris 2.5/2.5.1
] and possibly 2.4. However, Solaris is supposed to default to
] the server protocol. ( But, I never believe anything about
] solaris anymore ).. You can force solaris to use NFS2 .  Also,
] you can force it to use UDP packets instead of TCP.
] 
]   I don't know if FreeBSD NFS TCP works with Solaris's.


The NFS 3.0 code came out of a research project at the University
of Guelph.  This code was released for BSD before Sun released the
NFS 3.0 implementation.  Technically, it was the second public
release.  DEC beat all of us to the punch in an OSF release.


The "error message" on the client is a complaint about the server
not supporting the insufficiently documented Sun NFS locking
protocol implemented by "lockd" and "statd".

There is source code for a fully functional "statd" (rpc.statd)
and a sufficiently functional "lockd" (rpc.lockd) to make Sun
clients shut up and quit bitching.  You can get it from the
-current source tree; I believe it was in the "experimental"
section of the last CDROM release.

I posted kernel patches for server-side locking support to the
-current mailing list a year and a half ago.  You can see them
in the -current list archives on www.freebsd.org.  I estimate it
would take about a day to make the server locking fully functional
(Jordan Hubbard was going to do it as a class project for his
BSD internals class at Berkeley), and another 6 months to get
them to check it in (the FS area is sensitive because they have
not integrated the Lite2 changes yet).


In any case, it has nothing to do with a protocol mismatch... it
has to do with Sun tightening up their client code to only talk
to servers on OS's which have licensed the Sun locking code (the
ISO documentation on lockd is not enough to build a working
implementation).


                                        Terry Lambert
                                        terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.