Hi, My way to reproduce this:
I have a Karmic 32bit, completly uptodate. (in a VMware client, but i don't think, this should make no difference for this issue.) I use Synaptic Package Manger and remove completely _EVERY_ linux kernel, headers, modules etc. After this i have an empty /boot (except for ./grub, memtest) and an empty /lib/modules. Then i install the package 'linux-virtual'. /boot has the kernel now, and /lib/modules the <version>-generic-pae/kernel/fs, but in kernel/fs is only the configfs sub folder. On reboot i select the generic-pae kernel (witch is the only one). If i try to start the nfs server, it fails with initially * Not starting NFS kernel daemon: no support in current kernel. Now the same story again: Removing completely all (now the only one) kernel, but installing the 'linux-server' package, reboot, select generic-pae kernel again, and starting nfs server is no problem. Now /lib/modules/<version>-generic-pae/kernel/fs/ is full of sub folders, including the nfs and nfsd stuff. So i think, the bug description should better be 'No NFS support in Karmic virtual kernel?' And the answer could be: This is intended to keep the virtual kernel small. Only thing is, you can't even import nfs file systems with this virtual kernel, and that is what i tried to do, when i found this issue. But using the server kernel is ok for me. greetings Ralf -- No NFS support in Karmic kernel 32bit generic-pae? https://bugs.launchpad.net/bugs/444458 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
