Thanks all for the answers. I still find it's something strange. The share on the nas is shared as 777, so whoever who mounts should be able to read the contents.
I had stock (4.2.1), changed to CM 10 (4.2), and recently upgraded to 10.1 (4.2.1 again) I did not change anything. At this moment, I start a su shell, in which I enter mount -t nfs ip-adres:/share/subfolder localpath The next step would be to automate it, so I have the path mounted as soon as the nas is available. Actually, my goal is to use files which are located on a WD network drive (mybookworld) without having to copy them on my droid, so any other suggestion (eg samba) is welcome as well. On 28 January 2013 00:12, Tito <[email protected]> wrote: > On Sunday 27 January 2013 00:46:04 Tsjoecha wrote: >> unfortenately, I don't find the cause by now... ideas still are welcome >> >> TIA! >> >> On 26 January 2013 21:44, Tsjoecha <[email protected]> wrote: >> > Dan, >> > >> > I guess you could be right. after the mount, the permissions are >> > indeed changed (I guess the permissions from the nas are being taken >> > over to the mountpoint) >> > >> > I'll investigate my nas-settings, but it feels strange as it worked >> > before I migrated to CM10.1 >> > >> > On 26 January 2013 20:56, Dan Fandrich <[email protected]> wrote: >> >> On Sat, Jan 26, 2013 at 06:41:02PM +0100, Tsjoecha wrote: >> >>> The mount succeeds perfectly, if I go in the terminal to >> >>> /sdcard/Pictures and execute the ls command, I can see all my pics >> >>> from my nas-device. >> >>> >> >>> Though, when starting apps, like EZ File Explorer, the folder seems to >> >>> be empty. Other apps don't see the files neither. >> >>> >> >>> What can I do to resolve this issue? >> >>> I'm using BusyBox 1.20.2 >> >> >> >> It sounds like it could be a file/mount permissions issue. >> >> >> >>>>> Dan > > Hi, > just out of curiosity is it a static linked busybox build > or is it linked against android's bionic libc? > If it statically linked to another libc (uclibc?) > this could eventually explain the different behaviour. > Is it the same busybox binary as used before > you migrated to cm10.1? > What from did you migrate to CM10, standard android, > Aosp, other ROM? > Are the mounts in (/system)/etc/fstab? > Used there to be also (/system)/etc/mtab > or was it a link to /proc/mounts? > Also check permissions as vold for example uses very > specific ones for mounting the vfat partition of the sdcard: > > dev/block/vold/179:1 /mnt/sdcard vfat > rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015, > fmask=0702,dmask=0702,allow_utime=0020, > codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 > > > Hope it helps. Ciao, > Tito > > > > _______________________________________________ > busybox mailing list > [email protected] > http://lists.busybox.net/mailman/listinfo/busybox _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
