running kernel 2.6.5 with slackware-current

i built the kernel with nfs file system support using nfs version 3

i have modfied my exports, host.allow and hosts.deny files, but running rc.nfsd (after starting rc.portmap) yields the following output:

root@darkstar:/etc/rc.d# ./rc.nfsd start
FATAL: Module nfsd not found.
Starting NFS services:
/usr/sbin/exportfs -r
192.168.0.2:/mnt/2winData: Function not implemented
192.168.0.2:/home/user: Function not implemented
/usr/sbin/rpc.rquotad
/usr/sbin/rpc.nfsd 8
/usr/sbin/rpc.mountd
/usr/sbin/rpc.lockd
lockdsvc: Function not implemented
/usr/sbin/rpc.statd

afaik, there is no such nfsd module in the 2.6 kernels, but i can modprobe nfs without a problem, but the nfsd script still will not function

is there an explicit way that i should start nfs or is there another problem?
i have even tried with an empty hosts.deny file

here is my hosts.allow:
portmap: 192.168.0.2
lockd: 192.168.0.2
rquotad: 192.168.0.2
mountd: 192.168.0.2
statd: 192.168.0.2

exports:
/home/user 192.168.0.2(ro,sync)
/mnt/2winData 192.168.0.2(rw,sync)


*EDIT: omg, what a moron.... i completely missed the nfs server option in kernel config... oops
i'll recompile and hopefully that will get everything working

*edit 2: ya, everything is working now (nfsd is the nfs server kernel module)
i have to say, this system is awesome, i've never had such an easily setup and flawless network!

I was gonna say, another classic example of where slackware likes modules as opposed to compiled into the kernel.

less the idea that slackware itself likes modules, but the startup scripts do, simply because a lot of the things the startup scripts modprobe are things that are not absolutely necessary to run the computer

but then again, slackware's startup scripts are easily modifiable to just remove the modprobe nfsd lines and let the script start the nfsd services (portmapper, etc); it wouldn't complain because as these calls are made, the kernel will know what to do

nfs(d) is a good idea to compile as module if you know that it will not be necessary every time; if you are running a dedicated nfs server, then it would be a decent idea to compile into the kernel (though it will definitely do some enlargement....)

but it probably wouldn't matter because if i was running a dedicated file server, nfs server, then i wouldn't even include sound, video, or usb/firewire support, but simply basic necessities and net support