On Jan 7, 2011, at 1:09 AM, Marek Salwerowicz 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? Try loading all of the modules one-by-one. -GarrettReceived on Fri Jan 07 2011 - 09:14:13 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:10 UTC