On Fri, Feb 24, 2012 at 8:41 PM, Chuck Forsberg WA7KGX N2469R <caf@xxxxxxxx> wrote: > On 02/23/2012 08:50 PM, Tom H wrote: >> On Thu, Feb 23, 2012 at 4:55 AM, Chuck Forsberg WA7KGX N2469R >> <caf@xxxxxxxx> wrote: >>> >>> Here is the relevant /etc/exports entry in my server: >>> / 192.168.1.1/255.255.255.0(rw,async) >>> >>> Here is the screen capture from RC4 64 bit Xfce session: >>> [root@omen3 /]# mount 192.168.1.13:/ /o >>> mount.nfs: No such device >>> [root@omen3 /]# >>> >>> FWIW the /etc/exports has not been changed since November, >>> and the "mount 192.168.1.13:/ /o" where .o exists has worked >>> on client Fedoras for years until now. >> >> "nfs" must not be loaded; run "modprobe nfs". > > modprobe nfs complains about failed memory allocation. > > This was on the 32 bit, will try 64 bit later. > NFS mounts worked fine on 64 bit RC3 on another machine. (Please don't top post.) Not particularly helpful: I have no problems mounting nfs and nfs4 shares on an F17 Desktop 32-bit install once I add "nfs-utils" to the build. I can "modprobe -r nfs" and the nfs kernel modules are loaded automatically by "mount -t nfs ...". What's the actual "modprobe nfs" error? Someone might figure out what's going wrong for you. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
