Return to BSD News archive
Xref: sserve comp.unix.bsd:16081 comp.protocols.nfs:11101 comp.os.386bsd.misc:5280 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!gatech!udel!news.mathworks.com!newshost.marcam.com!charnel.ecst.csuchico.edu!olivea!koriel!news2me.EBay.Sun.COM!engnews2.Eng.Sun.COM!jetsun!robinson From: robinson@jetsun.eng.sun.com (David Robinson) Newsgroups: comp.unix.bsd,comp.protocols.nfs,comp.os.386bsd.misc Subject: Re: NFS V3 Alpha release Date: 8 Feb 1995 21:25:13 GMT Organization: SunSoft Inc. Lines: 15 Message-ID: <3hbcrp$dpt@engnews2.Eng.Sun.COM> References: <3gm938$inb@ccshst05.cs.uoguelph.ca> <3gokf3$9h6@news.duke.edu> <3gpq0s$5v2@news.cloud9.net> <3gu1o8$mf3@hpindda.cup.hp.com> NNTP-Posting-Host: jetsun.eng.sun.com In article <3gu1o8$mf3@hpindda.cup.hp.com>, Rick Jones <raj@cup.hp.com> wrote: >How much of NFS V3 has to be in place before it can be called "NFS V3" >as opposed to "something that has many NFS V3 features?" My opinion is that the server must support all the ops in the V3 specification that are appliciable to the native filesystem (exceptions like no symlinks allowed). The client side is more flexible because it may never issue some ops like mknod or symlink, but for the ops that it does generate they should be "correct". Things like using a TCP transport are orthoganal to its V3ness. -David