Date: Mon, 21 Sep 2009 11:33:57 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: src-committers@freebsd.org, jhb@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org, rmacklem@freebsd.org, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: svn commit: r197298 - head/sbin/mount_nfs Message-ID: <Pine.GSO.4.63.0909211127450.26309@muncher.cs.uoguelph.ca> In-Reply-To: <200909211416.11654.doconnor@gsoft.com.au> References: <20090919.230053.58383965.imp@bsdimp.com> <200909211216.07249.doconnor@gsoft.com.au> <20090920.220343.-737556392.imp@bsdimp.com> <200909211416.11654.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 21 Sep 2009, Daniel O'Connor wrote: [good stuff snipped] >> : >> : The thought of doing NFS over the internet boggles my mind :) >> [more stuff snipped] Just fyi, NFSv4 avoids all of this by doing everything via NFS over TCP to port 2049. Unless someone stands up and thinks that it isn't an appropriate change for 8.0, I'll email re@ at the end of to-day requesting the merge of the one line change I already committed to head. - It makes the default for Mount and the NFS Null RPC done before the mount(2) syscall use TCP by default. (It doesn't affect the behaviour when any of "udp", "tcp", "mntudp" options are specified.) Since Linux uses Mount over TCP for "tcp" mounts, I believe pretty well any server that supports NFS over TCP must also support Mount over TCP. (They'd get screamed at, otherwise.) Thanks for the input, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0909211127450.26309>