> I found the problem of mounting nfs. I want to develop program via > nfs using this commmand as following.
> cc_2:/# mount -t nfs 192.168.0.1:/home/myname /mnt > As a result, it can not work (I can not mount nfs). Reporting "it doesn't work" is usually of little to no use. In this case, I would like to see the error message. Given what you say about the portmapper, I'm assuming the error is something like "can't contact portmapper". > I have tried to check portmap running by using this command as below. > cc_2:/#rpcinfo -p > rpcinfo: can't contact portmapper: RPC: Remote system error - Connection > refused This isn't much use. rpcinfo normally contacts the local host if you don't specify a host, and the local host is cc_2, the client host, and whether it's running a portmapper is irrelevant; vide infra. You'd need to run "rpcinfo -p 192.168.0.1" to check the relevant portmapper in this case, 192.168.0.1 being the host you're trying to NFS mount from. > I have tried to insert module portmap to my system by using this > following command. > cc_2:/# insmod [...] You don't say what OS you're running. But I don't know of any where the portmapper is a kernel module; it's usually a user-level program called "portmap" or "rpcbind" or some such. Also, for NFS mounting to work, the place you need a working portmapper is on the *server* machine (192.168.0.1 in your case), not the *client* machine (cc_2 in your case). The prompt you quote is always "cc_2", implying that you're trying to set up the portmapper on the same machine you're trying to mount from, which is irrelevant. /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML [EMAIL PROTECTED] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
