/ Opt/FriendlyARM/mini2440/root_qtopia *
172.16.19.132, gateway and subnet mask of the development board and the host, respectively, 172.16.19.254 and 255.255.0.0
B # mount – t nfs localhost :/ opt/FriendlyARM/mini2440/root_qtopia / / mnt /
vim hosts.allow strong>
[OK]
Setup linux parameters at 0×30000100
The meaning of this command breaks down as follows:
host the / opt/FriendlyARM/mini2440/root_qtopia “directory
run the mount command, just the directory to mount their own computer to give it a try.
statd: 172.16.19.
Upstart job, you may also use the start (8) utility, eg start portmap
(7) strong> “ eth0 strong> “development board of the network equipment (that is, the selected card)
vim, hosts.deny as in strong>
rquotad: the 172.16.19
MACH_TYPE = 1999
here, the things you want to configure the configuration finished. After that start, the verification service.
first explain my basic configuration: the the
(1) strong> the “ param the set linux_cmd_line strong>” set of Linux command line;
ZImage the magic = 0×016f2818
vim / etc / exports strong>
rquotad: ALL
apt-get install nfs-kernel-server strong>
/ opt/FriendlyARM/mini2440/root_qtopia * (rw, after the sync, no_root_squash)
enter the command, you can press Enter, then type boot, and the development board from the start the NFS directory on the host.
Enter the following: Jul 28, 2010
NOTE: this default has changed since nfs-utils version 1.0.x
the portmap: ALL
* Starting an NFS kernel daemon [OK]
lockd: ALL
strong> * Exporting directories for NFS kernel daemon …
NOW, Booting Linux ……
mountd: ALL
exportfs: / etc / exports [3]: Neither ubtree_check or o_subtree_check specified for export “* :/ opt/FriendlyARM/mini2440/root_qtopia”. Assuming default behaviour (o_subtree_check.
and then test, to see shared directory exists, the command is as follows:
then save and exit (banned all IP addresses)
/ etc / init.d / portmap start strong>
then you want to share the directory permissions changed to 777 (I was lazy, did not count, so that is not very good, you can count) command as follows:
[B # / etc / init.d / nfs-kernel-server start
the showmount-e
first configure a shared directory: the
Supervivi> the boot strong>
(Note * I personally prefer the direct use of root user to configure under Linux the following command does not add the sudo if your user permissions are not root privileges, remember to add sudo, and then enter the root password)
bin etclib mnt the proc sbin test_nfs usr www
Enter the following:
/ etc / init.d / nfs-kernel-server start strong>
to see such a result, if no unexpected events occur, the following steps are can be successful:
2 start configuration:
chmod-the R 777-the / opt/FriendlyARM/mini2440/root_qtopia strong>
which “/ opt/FriendlyARM/mini2440 / root_qtopia “is the directory you want to share,” * “represents all IP addresses can access,” rw “mount read and write permissions for the user to the directory of the directory, no_root_squash said, if the directory is mounted the user log in as root in that directory, with root privileges. (Note * I am still not clear why the setting can access the IP segment of the directory, can only be used *, but not use of online IP segment set methods, such as 172.16.19. or 172.16.19.3/233, if you set these IP ranges will appear the following error mount: mount.nfs from: access denied by the server while mounting xxxx is: of yyyyy permissions prompt. There are also worth noting that yes, there are spaces between the catalog and behind the “*” I did not play this space, has spent nearly half an hour)
(3) strong> “ root = / dev / nfs, strong>” root directory for the / dev / nfs
(4) strong> “< strong> nfsroot = 172.16.19.132 :/ opt/FriendlyARM/mini2440/root_qtopia The strong> “directory of the NFS service is IP” 172.16.19.132 “
similar to the following results, then the shared directory configuration successful.
utility to, eg the service the portmap start
today to do here, starting tomorrow in order to configure FTP, HTTPD to TELNET, Samba services. real ARM development.
Since the script you are attempting to invoke has been converted to an
apt-get install nfs-common strong>
[B # showmount-e strong>
If you are running as follows: (in this inconvenient shots, so I had to directly copy the results of the run to give you a bold command line, no bold are the results for my own privacy, I host name instead of by XXXX)
Copy linux kernel from 0×00060000 to 0×30008000, size = 0×00500000 … done
Export list for XXXX:
dev home linuxrc is opt root systmp The var
Oh, here, NFS configuration is complete. later developed, directly from the NFS to start the development board, to write on the host, compiler, and then directly to the development board running, verify, rather than the program through other be downloaded to the development board, and permanent changes to the system under development board, not because of the development board to restart, power down and lost things, the development of larger projects is very good.
linux command line is: “console = ttySAC0 root = / dev / nfs nfsroot = 172.16.19.132 :/ op”
(5) strong> “ ip = 172.16. 19.110:172.16.19.132:172.16.19.254:255.255.0.0 strong> “development board IP address is 172.16.19.110, the IP of the host
B # / etc / init.d / portmap start strong>
save and exit (in this case has opened up a channel, so that by to 172.16.19 starts with the IP address, here rewritten according to their own IP)
the portmap: 172.16.19.
Rather than invoking the init scripts through / etc / init.d, use the service (8)
run the command:
and then configure the access permissions (these things can be omitted, but in front of IP ranges * So here it is recommended to configure the following security!): the
(8) strong> “ off strong>” As for this off, I am still not clear in the end want to close things, in the hope that the expert can give an advice
the lockd: 172.16.19.
after completion of the above configuration, connect the development board, and then open minicom, to the board to boot from NAND Flash, instant power-up or reset (this is a friendly arm of the official to the original words-year-old course not, but generally mean is, this is rubbish do, sometimes I Feeling bad, reset several times). development board any key press, enter supervivi mode, press the “q” key, in supervivi the command line mode, enter:
me through a router, connect the computer and development board computer IP address: 172.16.19.132, development boards, IP address: 172.16.19.110 Gateway: 172.16.19.254, subnet mask: 255.255.0.0. development board and the computer can access the router friends can Set the computer and development board to the same network segment and subnet mask, gateway IP address in front of three segments of the same, the last paragraph (such as the above), then take a direct crossover cable (not ordinary network cable) connected to the computer and development board, but can not access (wireless network, configure the following wireless, you can also access to the Internet, anyway, as long as the development board and the computer can ping each other)
(6) strong> “ sbc2440.arm9.net strong>” host name of the host (PC), this does not matter, what to write
1. download and install the necessary software:
strong> [B # ls / mnt / strong> the
(2) strong> “ the console = ttySAC0 < / strong> “terminal is set to ttySAC0; the
apt-the get the portmap strong>
the statd: ALL
param set linux_cmd_line” the console = ttySAC0 the root = / dev / nfs nfsroot = 172.16.19.132 :/ opt/FriendlyARM/mini2440/root_qtopia ip = 172.16.19.110:172.16.19.132:172.16.19.254:255.255.0.0: sbc2440.arm9.net: eth0: off “ strong>
Oh, excited not? such a result in front of the hard work is not white, if you do what I say, there is a problem, then please do not blame me, because the Linux system, the difference is too large, each person not the same, so, please be patient on Google Soso to see (the site of China foreign website on the solution of many problems in this regard, recommended on foreign websites, it is English, but the solution steps detail, explain the patient and meticulous)
today to spend a morning mini2440 development board configured NFS service The reason why it took so long, because at the beginning of a waste of a very long time on a virtual machine, found that these things are just not worth it, so that someone is in a pure Linux environment on a virtual machine configuration I, in turn, run the windows virtual machine under Linux, this log is in Linux written on the windows virtual machine environment. Here to you talk about my NFS configuration process.
interpretation of the above are my own understanding, the official did not say, if my understanding is there is an error, correction given in the message board.
mountd: 172.16.19.
enter the following: