I use sshfs for chroot development. I have a meego chroot on my big desktop, do all edits and builds there, then to install on to the target hardware is do:
INSTALL_ROOT=/target-sshfs make install It is a shorter development loop than to build the rpm, copy that over and install it. [Sent from my phone] ----- Original Message ----- From: Niels Mayer [mailto:nielsma...@gmail.com] Sent: Wednesday, April 27, 2011 09:36 AM To: meego-dev@meego.com <meego-dev@meego.com> Subject: [MeeGo-dev] FYI -- using fuse-sshfs to mount remote filesystems with only SSH (sftp) ## install fuse-sshfs-2.2-4.30.i586 $ sudo zypper in fuse-sshfs ## f use module must be loaded else fail $ sudo modprobe fuse ## make a permanent mount point in "/media" $ sudo mkdir /media/gnulem-npm ## allow non-superuser 'npm' to mount $ sudo chown npm.npm /media/gnulem-npm ##mount the sftp filesystem on mount point $ sshfs gnulem: /media/gnulem-npm npm@gnulem's password: ... Now 'df' reports: gnulem: 453G 408G 23G 95% /media/gnulem-npm And the remote system is mounted as if locally, without needing to setup NFS -- just needs SSHD running. Obviously not as fast or performant given the encrypt/decrypt invoked by SSH, but at least it's as secure as SSH and can be further secured by using public/private keypairs in SSH. Niels http://nielsmayer.com _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
