Re: nfssvc not available or version mismatch (nfsv4 client)

On 7 January 2011 12:09, Marek Salwerowicz <marek_sal_at_wp.pl> wrote:
>>
>> kldload nfssvc && dmesg | tail -n 10 ?
>>
>
> vm-salwerom% sudo kldload nfssvc
> kldload: can't load nfssvc: File exists
>
> but:
>
> vm-salwerom% sudo kldload nfssvc.ko
> vm-salwerom% dmesg | tail -n 10
> em0 at 194.29.146.128 server 194.29.146.27 server name amp2
> subnet mask 255.255.255.0 router 194.29.146.1 rootfs 194.29.146.3:/ rootopts
> nolockd hostname vm-salwerom
> Adjusted interface em0
> SMP: AP CPU #1 Launched!
> Trying to mount root from nfs: []...
> NFS ROOT: 194.29.146.3:/
> KLD nfscommon.ko: depends on nfssvc - not available or version mismatch
> linker_load_file: Unsupported file type
> KLD nfscl.ko: depends on nfssvc - not available or version mismatch
> linker_load_file: Unsupported file type
> vm-salwerom%
> vm-salwerom%
>
>
> so, why if I want to load nfssvc I have to type it with the suffix? How can
> I tell nfsuserd and anfscbd to try to load it with suffix during system
> boot?

That's because .ko (a kldname mode) and w/o .ko (a modname mode)
are handled differently (see kern/kern_linker.c). AFAIR, the latter looks
if the interface name (modname) is already registered by kernel or
some earlier loaded KLD (and returns EEXIST on success), otherwise
it searches the requested interface name in the list of available KLDs
in the module path and loads the appropriate one.

-- 
wbr,
pluknet