Date: Wed, 7 Sep 2011 17:21:42 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org, lev@freebsd.org Cc: Garrett Cooper <yanegomi@gmail.com> Subject: Re: -CURRENT (BETA2) nfs client surprise Message-ID: <201109071721.42950.jhb@freebsd.org> In-Reply-To: <1036483457.20110908010247@serebryakov.spb.ru> References: <1505890415.20110908005042@serebryakov.spb.ru> <CAGH67wQ1iZ-GyR8=T0C2tEKYWvR3fMpY0y3oSWi1QjP9qHhRXA@mail.gmail.com> <1036483457.20110908010247@serebryakov.spb.ru>
index | next in thread | previous in thread | raw e-mail
On Wednesday, September 07, 2011 5:02:47 pm Lev Serebryakov wrote: > Hello, Garrett. > You wrote 8 сентября 2011 г., 0:55:11: > > > It needs to be changed to NFSCL: > > > $ svngrep -r NFSCL /sys/i386/conf/GENERIC > > options NFSCL # New Network Filesystem Client > > options NFS_ROOT # NFS usable as /, requires NFSCL > Yep, I found it in seconds, but after that kernel + nanobsd image > rebuild takes considerable amount of time. > > > I think the nomenclature change was done s.t. clients using old NFS > > implementations didn't require any changes in their KERNCONF files. > It is not true. I'm using old KERNCONF (with only NFSCLIENT) and old > fstab (Without any NSF vversion options) -- and got error on boot due > to unmountable file system! Of course, if this system had had full set > of modules, this situation would have masked by transparent loading of > nfscl.ko. You can't rely on using kernel configs unchanged across major releases. -- John Baldwinhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201109071721.42950.jhb>