= Network =

== Network File System (NFS) Testing ==
It is helpful to setup an NFS share on your host computer for application testing. You may place your executables to be tested in the directory and access them from the target hardware. Using MiniCom, HyperTerminal or another communications program to communicate with the debug serial port 115000 8N1 the prompt should appear as:

{{{
#
}}}
Type:

{{{
# mount –t nfs !90.1.2.69:/tftpboot/ltib /mnt/nfs –o nolock <CR>
}}}
Replace 90.1.2.69:/tftpboot/ltib with the appropriate IP address and share name of your NFS share

Type:

{{{
# cd /mnt/nfs
}}}
to change to the NFS directory. You can then run an application from the NFS folder such as:

{{{
# ./indicator &
}}}
To run an application named indicator. Make sure the application is flagged as executable from the host. To stop a running application type:

{{{
# ps

  PID TTY          TIME CMD
    1 ?        00:00:02 init
    2 ?        00:00:00 kthreadd
    3 ?        00:00:00 migration/0
    4 ?        00:00:00 ksoftirqd/0
    5 ?        00:00:00 watchdog/0
    6 ?        00:00:00 migration/1
    7 ?        00:00:00 ksoftirqd/1
    8 ?        00:00:00 watchdog/1
    9 ?        00:00:00 events/0
   10 ?        00:00:00 events/1
   11 ?        00:00:00 khelper
   85 ?        00:00:00 kintegrityd/0
   86 ?        00:00:00 kintegrityd/1
   88 ?        00:00:00 kblockd/0
   89 ?        00:00:00 kblockd/1
   91 ?        00:00:00 kacpid
   92 ?        00:00:00 kacpi_notify
}}}
This will list the running processes. Identify the PID number of the process to stop and type:

{{{
# kill <PID>  (where <PID> is the appropriate process ID)
}}}
At times you may lose track of your current path. To check the current path type:

{{{
# pwd
}}}
This will respond with the current path such as “/mnt/nfs”.

[[Top]]