ARMbusybox connects to NFS

Main steps for ARMbusybox to connect to NFS: Create an NFS server on the PC using www.2cto. com1. 2. check whether the NFS server is correct on the PC. 3 Telent on ARM Board busybox, mount-tnfs-onolock10.0.2.130:/export/home establish NFS service... ARM busybox connect NFS main steps: www.2cto.com 1 on the PC, create NFS server. 2. check whether the NFS server is correct on the PC. 3. mount-t nfs-o nolock 10.0.2.130: /export/home create NFS server www.2cto.com 1 suppose firewall has been disabled 2 install yum install nfs-utils.i6863 install yum install rpc2 (I have installed it in my experiment, this is a very basic service) 4 vi/etc/idmapd. conf [General] Domain = localdomain # obtained using dnsdomainname, search "Linux: find out information about current domain name and host name "[Mapping] Nobody-User = nfsnobodyNobody-Group = nfsnobody5 start nfs (nfs-related services are rpcb Ind, usually normal, don't worry) systemctl enable nfs-server.service systemctl start nfs-server.service6 mkdir-p/export/{share1, share2, permission 3} sudo chmod-R a + rwx/export # I don't want to encounter permission problems. open the permission to 7 vi/etc/export 127.0.0.1 (ro, sync) /export 10.0.2.0/255.255.255.0 (rw, sync, insecure, no_root_squash)/home/hl/temp 10.0.2.131 (rw, sync, insecure, no_root_squash)/home/hl/temp 10.0.2.132 (rw, sync, insecure, no_root_squash)/home/ Hl/temp must have 777 permissions, and the entire 10.0.2 is allowed here. * Segment access: single host wildcards * .example.com ip networks 192.168.0.0/28 allows the first 16 IP addresses, from 192.168.0.0 to 192.168.0.15, to access the exported file system, but not 192.168.0.16 and higher.8 exportfs-rv # nfs re-configure the PC-side NFS client configuration because the server and client are on one machine and there is nothing to configure. Log on to sudo mount-t nfs 127.0.0.1 as a root user :/ In this case, the sudo mount-t nfs 127.0.0.1:/export/mntumount/mntsudo mount-t nfs 10.0.2.130:/export/mnt # directory that can be mounted should be displayed to check whether the ip address is correct. The ARM board busybox, of course, must support nfs during kernel and busybox compilation. No configuration is required. The only note is that the-o nolock option is required. Mount-t nfs-o nolock 10.0.2.130:/export/homemount-t nfs-o nolock 10.0.2.130:/home/hl/temp/home note: 1 directory on the server where the export is export, the nfsnobody user must have the corresponding permissions. The simplest is to grant 777 permissions. For example,/home/hl/temp must have the 777 permission. However, you do not need to set/home/hl. 2. the ARM and fedora virtual machines share a directory through NFS, so that the program compiled on the virtual machine can be used immediately on the ARM without copying. Can it be more convenient than this?