| WARNING: /home/ubuntu/openatv/build-enviroment/builds/openatv/spark/tmp/work/sh4-oe-linux/openssl-old/0.9.8x-r15.0/temp/run.do_configure.17909:1 exit 2 from
| Can't locate in contains: /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl.
| DEBUG: Executing shell function do_configure | DEBUG: Python function sysroot_cleansstate finished | DEBUG: Executing python function sysroot_cleansstate I am able to read and write files in that directory as the osmc user.Code: ERROR: Function failed: do_configure (log file is located at /home/ubuntu/openatv/build-enviroment/builds/openatv/spark/tmp/work/sh4-oe-linux/openssl-old/0.9.8x-r15.0/temp/log.do_configure.17909)ERROR: Logfile of failure stored in: /home/ubuntu/openatv/build-enviroment/builds/openatv/spark/tmp/work/sh4-oe-linux/openssl-old/0.9.8x-r15.0/temp/log.do_configure.17909 Returns the directory structure shown below with osmc as the user and permissions preserved. I am able to manually mount as sshfs -o idmap=user,allow_other,nonempty /mnt/sshfsmount Ls: cannot access '/mnt/sshfsmount/': No such device When I include the following in /etc/fstab and reboot /mnt/sshfsmount fuse.sshfs tomount,noauto,rw,user,transform_symlinks,identityfile=/home/osmc/.ssh/id_rsa,allow_other,default_permissions,uid=1000,gid=1000 0 0 As such, I’m not able to create the user osmc on the server nor edit /etc/ssh/sshd_config on the server side. The ftp server is on a shared host that does not provide root access.
mnt/sshfsmount fuse.sshfs tomount,noauto,rw,user,transform_symlinks,identityfile=/home/osmc/.ssh/id_rsa,allow_other,default_permissions,uid=1000,gid=1000 0 0 I can’t remember why I didn’t choose NFS however: what are its main limitations, compared to other network sharing protocols? Security?Īlso, why does OSMC doesn’t show the login window for the SFTP server so I know it works?Īnd how would you mount a remote folder with SSHFS without requiring root access? Non-TM AFP network transfers work just as well, without Samba’s configuration nightmare and toll levied from the CPU (at first I chose Netatalk over Samba for its better security, and kept or because it was easier to configure and overall faster during transfers). Maybe a backport?Īnd Apple hasn’t killed it: it’s actually mandatory for Time Machine backups support, and the problems experienced with it come from TM’s complexity itself. Removed? I can confirm it’s alive and well on my other Jessie-based NAS, OpenMediaVault, the last package is from december 2015. It is a dying protocol that Apple themselves have deprecated a number of years ago - the 3rd party implementations did not work very well and nobody in the open source community is interested in trying to bug fix a protocol everyone is moving away from. There is no netatalk package available in Debian Jessie (it was removed after Wheezy) and Kodi also had built in support for Netatalk removed quite some time ago. What makes you think it would require root access on the server ?I can’t dissociate SSH connection from needing, witht the notable exception of the Raspberry Pi.
0 kommentar(er)
