Date: Sat, 30 Apr 2011 19:45:52 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> Cc: freebsd-fs@freebsd.org Subject: Re: RFC: make the experimental NFS subsystem the default one Message-ID: <1591833752.819973.1304207152724.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <86iptvg9uo.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> > This comes from mountcritremote: > > case "`mount -d -a -t nfs 2> /dev/null`" in > *mount_nfs*) > # Handle absent nfs client support > load_kld -m nfs nfsclient || return 1 > ;; > esac > > mount(8) will print "mount_oldnfs" instead of "mount_nfs". Note that > until you flipped the switch, the exact same error would occur, in > reverse, on systems running the new stack. > Yep, I spotted that, but haven`t had a chance to reproduce it and test a fix yet. My first attempt at fixing it will be to change the line to: load_kld -m nfs nfscl ... if that works, I`ll see what the rc folks think is the best fix. > > If you could test a pre-switchover (but recent) client and see if > > the > > message shows up, that would be appreciated. > > It does, so it's not something new. > Ok, thanks for testing it, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1591833752.819973.1304207152724.JavaMail.root>