::chuckles:: this took me about 3 weeks to get right.
primarily, check out the 'etherboot' package. this grabs the kernel and
ip info, then boots the kernel. however, the etherboot home page has a
lot of good info on it re. doing a remote boot like this.
make etherboot work. this requires setting up bootp and tftp, then
creating the bootdisk. read the docs...pretty easy.
next, re-compile your kernel, it needs support for your nic and NFS-root
filesystems. again, docs on the etherboot page will walk you through
next, get NFS to work. this was the hard bit, because the NFS errors
are cryptic, to say the least. two caveats from personal experience:
1) the version of knfsd i was using won't export to subnets correctly;
export to each machine individually.
2) NFS must be able to resolve the ip address of the client into a name
before it will connect the client! don't ask me why. read the messages
log file if this doesn't cut it.
3) if NFS is working entirely, you should have a remote-bootable