Originally Posted by DanielGwalter
I tried cifs manager but that only shows up in the current session (ES File manager but no other apps).
so, i stripped all the commands back to the point where i could get it to mount, then i started adding back and got it working ....
question: I am trying to write a script that cleans up and creates the mounts....
what command can i use to unmount the mount points. i tried umount <path> and this appears to work (as long as you su it) but then when i try to delete the folder i get "device busy" ... if i reboot and delete its fine but thats not the desired umount method!
so what I am looking for is a forcible unmount and delete of mount folder...
Well that confirms you can mount cifs. The next step would be to try a manual mount via adb. 'adb shell' into your phone and do the mount there, see if you get the seg fault and if not if it shows up in apps.
As for unmounting, umount seems to work fine for me although I have never tried to delete the mount point afterwards. It's possible you have to umount from within adb if you mounted in adb. On a full Linux there is also 'umount -lf /mountpoint' (-l for lazy and -f for force) but I don't know if busybox supports that. It does seem to support moving a mount via the -o move option (i would assume the syntax is 'mount -o move /mnt/old /mnt/new' (untested). You could perhaps use that to just move it somewhere out of the way, then delete the folder.
Originally Posted by ThurstonX
I'm trying to make this work on a Nexus 7. I've got the modules and the script seems to load them and mount successfully. The mount point is empty, though.
Script Manager reports the following after connecting to localhost:5555 and "Mounting share via adb...":
Usage: adb services [-l] (I think that's a lowercase "L")
usage: setprop <key> <value>
To get that far I had to edit the script to change ` to ' and to stop CIFS Manager from loading the modules at startup (was getting "insmod .... failed (file exists)" errors.
I realize this is a Nexus 10 thread, but surely the principles are the same.
Any advice? Thanks.
There is a typo in the script that causes the setprop message, I was going to fix it but forgot, it doesn't seem to matter other than popping up a warning.
As for the modules. you need ones for the kernel version of your device, specifically you need to match the g4e6298b at the end which is the Nexus 10 kernel. I believe the Nexus 7 uses 3.1.10-g22b4fcd. So are you using Nexus 7 cifs specific modules or ones you got from here? There are Nexus 7 ones here
If you are using the correct modules, fire up a terminal and check the output of 'mount' to see if your mountpoint is listed and then check if you can see the mount contents in the terminal.