Date: Wed, 7 Sep 2011 13:55:11 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: lev@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT (BETA2) nfs client surprise Message-ID: <CAGH67wQ1iZ-GyR8=T0C2tEKYWvR3fMpY0y3oSWi1QjP9qHhRXA@mail.gmail.com> In-Reply-To: <1505890415.20110908005042@serebryakov.spb.ru> References: <1505890415.20110908005042@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/9/7 Lev Serebryakov <lev@freebsd.org>: > Hello, Freebsd-current. > > =A0I've built NanoBSD image for my router based on latest HEAD sources. > Image contains minimal set of kernel modules and custom kernel with > NFSCLIENT option. 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 > =A0Router mounts "/usr/home" via NFS with this "/etc/fstab" line: > > 192.168.134.2:/usr/home /usr/home nfs rw,late,soft,intr,bg,wsize=3D65536,= rsize=3D65536,tcp 0 0 > > =A0And I've been very surprised when boot failed because it cannot find > "nfscl" module. > > =A0Yes, I know, that now here are TWO versions of in-kernel NFS > clients. But, IMHO, it is POLA violation not to boot with valid > configuration from previous version. I think the nomenclature change was done s.t. clients using old NFS implementations didn't require any changes in their KERNCONF files. Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wQ1iZ-GyR8=T0C2tEKYWvR3fMpY0y3oSWi1QjP9qHhRXA>