Description of problem: Despite the fact that NFS is enabled, you can't actually mount anything over a network. Version-Release number of selected component (if applicable): kernel-2.6.5-1.322.i686.rpm How reproducible: Very Steps to Reproduce: 1.# chkconfig --list nfs nfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off 2.mkdir /mnt/test_mount 3.# mount -v 192.168.2.1:/test_mount /mnt/test_mount mount: no type was given - I'll assume nfs because of the colon mount: fs type nfs not supported by kernel Actual results: NFS mount was not successful. Expected results: NFS mount would have succeeded. Additional info: I did a "make defconfig", and noticed that NFSv3 client and server are not enabled filesystems by default.
You'll probably have to bug upstream to change defconfig.
I am continually doing research on this bug, because it made no sense that it has gone un-noticed by everyone else. Come to find out, in the %post section of my ks.cfg, I had the following command: # chkconfig --level 345 nfs on So, if I do a build with the above command commented out, after a reboot, I see this: 1.# chkconfig --list nfs nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off ... but guess what? NFS does actually work! It's only when you enable it, that it stops working. Sorry for the bad information in my original bug report.
It does not appear that this is a issue, please reopen if it is...