Date: Wed, 4 May 2011 21:24:51 -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: <277230554.1031144.1304558691708.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
> Rick Macklem <rmacklem@uoguelph.ca> writes: > > "Dag-Erling Sm=C3=B8rgrav" <des@des.no> writes: > > > interface oldnfs.1 already present in the KLD 'kernel'! > > > /etc/rc: WARNING: Unable to load kernel module nfsclient > > Ok, I'll need to look at this. At a glance, I see a load_kld, > > but that won't get upset if it's already loaded. (It does need > > to be fixed, though, since it refers to nfsclient as the module > > for "nfs" instead of nfscl.) >=20 > This comes from mountcritremote: >=20 > 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 >=20 > 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. >=20 Testing here, it seems that none of the NFS specific stuff is needed in mountcritremote (as hinted by the comment). You can try the version without the NFS specific stuff if you'd like. It's in: http://people.freebsd.org/~rmacklem/rc.conf along with the other modified/added scripts. rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?277230554.1031144.1304558691708.JavaMail.root>