I am trying to setup a build environment for OMAP blaze device which is running ice cream sandwich. I am trying to mount a folder from my Linux box (Ubuntu) to blaze using NFS. After setting up the server on Ubuntu I use the following command on omap to map the drive:
mount -t nfs IP_OF_UBUNTU_MACHINE:/SOME_DIR/ /sdcard/nfs/SOME_DIR_2
which returns with the following error message: "invalid argument". I already checked the following: (1) IP is correct as I can ping it (2) source and destination directories exist (3) after doing "make menconfig" in kernel's directory I noted that "NFS client support" is actually selected. Could anybody help me resolve this issue?
By typing "man mount" in terminal the option nfs3 is not available try using nfs or nfs4;
Mount options for nfs and nfs4 See the options section of the nfs(5) man page (nfs-common package must be installed).A point to check is next link
and adding some options to command line it could depend on how PC's NFS is configured defaults Use default options: rw, suid, dev, exec, auto, nouser, and async.
Yes I noted that and updated the post accordingly. Now I am using
mount -t nfs ...
which returns "invalid argument". On a side note. Please correct me if I am wrong. The "mount" utility on android is not the same as the linux one. i.e. "man mount" does not necessarily give me correct information. e.g. typing "mount --version " returns error on android.
I just ran mount -t nfs4 and "invalid argument" error became "no such device" i used my PC's IP address that is not using a nfs server.
try using nfs4
source code for mount is in toolbox code, it has menu options
Thanks a lot for double checking. Yes using nfs4 returns "No such device" for me too. But this I would expect as nfs4 is not built as a part of ice cream sandwich release (i.e. default configuration of kernel excludes it). Still wondering how this could go wrong as I am pretty sure a lot of OMAP developers should rely on it for driver/software development. Hopefully someone would have an answer :)
Your version of mount might not support NFS. See Xavier's post here:
Check to see which mount program you are using by "which mount" on the target. You might be running "/bin/mount" or a symbolic link to "/bin/busybox".
one link for Busybox in Android is
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.