Live data from Hacker News

A currently maintained fork of SSHFS

github.com

61–70 of 144 posts

Re: A currently maintained fork of SSHFS

#62

If you want something in user land and you don't mind emacs there is TRAMP “Transparent Remote (file) Access, Multiple Protocol”. https://www.gnu.org/software/tramp/ I use it a lot when I am accessing files from my server on my MacBook Pro .

My favorite thing about using TRAMP is being able to cd to a directory on a remote system, and then cp a file either from my working directory to my local machine (or another remote!), or from my local machine to the current working directory.

Before I started using TRAMP, my flow for this was: SSH to a remote system, locate where I want to copy a file to with cd + ls, kill my SSH session, and then scp or rsync the file over, and then usually SSH back into the system.

Re: A currently maintained fork of SSHFS

#63
post #11

Discovered that you can replace sshfs with rclone. And the project appear to be way more active : https://github.com/rclone/rclone Edit: cf: https://rclone.org/commands/rclone_mount/

I'm trying to use rclone, but it seems like it's kind of hard to set up compared to sshfs. Do I really need to go through their 20 question setup script?

Re: A currently maintained fork of SSHFS

#64
post #43

It's obviously a slightly different combination of technologies, but I've been using NFS over wireguard pretty happily for a while...

I myself went to other way around. While my VPN infra is very stable, I went into repo route. I use my very simple DVFS repo utility to sync files and never looked back. I like to have multiple copies of stuff here and there.

Re: A currently maintained fork of SSHFS

#65
post #11

Discovered that you can replace sshfs with rclone. And the project appear to be way more active : https://github.com/rclone/rclone Edit: cf: https://rclone.org/commands/rclone_mount/

I love rclone, I'm currently using `rclone mount` to mount a Backblaze B2 bucket to use as backing storage for Jellyfin and it works a treat. There are plenty of dials to tune things like cache size and duration to minimize unnecessary downloads from B2, and with my usage patterns it ends up astoundingly cost effective (although at some point I might move to Hetzner storage boxes for even cheaper storage).

Wasabi might been a good choice for you on that front

Re: A currently maintained fork of SSHFS

#66
post #33

Interesting, I alaways assumed sshfs was part of OpenSSH, learn something new every day. Also, looks like sshfs used in Slackware is abandoned. https://github.com/libfuse/sshfs A quote from the link, I wonder if this project will be the 'one': >If you would like to take over this project, you are welcome to do so. Please fork it and develop the fork for a while. Once there has been 6 months of reasonable activity, pl…

It does seem like a good fit for the maintainers of openssh. I too had thought it was key linux ssh infrastructure.

I kinda doubt it, SSH already have SFTP and SSHFS is .... quite honestly a tool that has no business existing.

It's a neat trick but it's always going to be something that someone bolted on to a solution because they didn't want to deal with a proper file server. Part of the appeal might be that NFS (3 or 4, take your pick) is still the best we've been able to come up with and neither is really that great for basic installation. Still SSHFS is a mess to deal with in a production setup. Some of the messiest production systems I've de-tangled over years have frequently been relying on SSH and SSHFS to do stuff assumes a permanent connection.

Re: A currently maintained fork of SSHFS

#67
post #33

Interesting, I alaways assumed sshfs was part of OpenSSH, learn something new every day. Also, looks like sshfs used in Slackware is abandoned. https://github.com/libfuse/sshfs A quote from the link, I wonder if this project will be the 'one': >If you would like to take over this project, you are welcome to do so. Please fork it and develop the fork for a while. Once there has been 6 months of reasonable activity, pl…

It does seem like a good fit for the maintainers of openssh. I too had thought it was key linux ssh infrastructure.

No it’s a horrible fit. OpenSSH is focused on a high quality, secure implementation of a rather complex protocol. And OpenSSH is not a core piece of Linux infrastructure any more than say gcc is. These projects serve other, greater ends. A FUSE driver is a bunch of baggage that is poorly suited to be maintained with it.

Re: A currently maintained fork of SSHFS

#69
post #55
post #28

Nautilus (Ubuntu's file explorer) allows to mount SFTP folders. Supposedly it uses `gvfs` under the hood. Note that SFTP uses an SSH connection for its file transfers, so I have not seen an UI difference from SSHFS

It allows you to browse sftp endpoints in the nautilus GUI but does it simultaneously create a mount point in the file system that you could use in the terminal? I don’t remember…

gvfs has a bridge to fuse, cf. https://manpages.ubuntu.com/manpages/trusty/man1/gvfsd-fuse.... -- that means: Yes, you can use gvfs mounts natively in all other non-GNOME/GTK-applications running on your computer.

Re: A currently maintained fork of SSHFS

#70
post #55
post #28

Nautilus (Ubuntu's file explorer) allows to mount SFTP folders. Supposedly it uses `gvfs` under the hood. Note that SFTP uses an SSH connection for its file transfers, so I have not seen an UI difference from SSHFS

It allows you to browse sftp endpoints in the nautilus GUI but does it simultaneously create a mount point in the file system that you could use in the terminal? I don’t remember…

> does it simultaneously create a mount point in the file system that you could use in the terminal?

Yes it does. You can find it in /run/user/$(id -u)/gvfs/

Post reply on HN