Invoke-rc.d: initscript autofs, action "start" failed.ĭpkg: error processing autofs5 (-configure):Įrrors were encountered while processing: Starting automount: Error: failed to load autofs4 module. Subprocess installed post-installation script returned error exit status 1 Invoke-rc.d: initscript nfs-common, action "start" failed.ĭpkg: error processing nfs-common (-configure): Starting NFS common utilities: statd failed! Insserv: warning: script '99CleanTWEAKS' missing LSB tags and overrides If I install the openssh-server in debian and stop the SSHDroid server, then I can see the /mnt/tower content from my ssh login from PC. If I remote login from PC to an SSHDroid server on the Android, then I cannot see the mounted content of /mnt/tower (even as root). I can see the /mnt/tower content both with the ConnectBot shell as normal user as root, and with the shell I get after running 'deb' from a ConnectBot shell. I mounted the nas using ConnectBot local shell with the command: I have tried the TotalCommander Android app, and tried telling TotalCommander to always use root (in case user made a difference). I can browse the files on the nas from the mounted directory in the ConnectBot Shell, but I cannot see the mounted directory through android apps (or adb shell), eg TotalCommander, OI FileManager, MX video player. I have managed to get debian-kit + sshfs installed, and my nas mounted using sshfs. My problem is that Android Apps cannot see the mounted content, which is what I desire. I've been longing to get sshfs on my Android for three years Robert, thanks for the guide to sshfs with debian-kit. SSHFS problems Android 4.2.2 Nexus 10 - apps cannot see mounted content
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |