12
13
My university's CS department has its own server used for development (from here on out, dev.univ.edu
). I have SSH and SFTP access to this server, and I was hoping to do some heavy work on my Windows laptop using WSL. My plan was to use sshfs
to mount the server's filesystem on my laptop via SFTP, so that I could use my own tools instead of having to use the limited programs on our server. However, whenever I try using sshfs
, the following happens:
user@host:~$ sshfs -p 22 user@dev.univ.edu: ~/dev/ -o follow_symlinks
> fuse: device not found, try 'modprobe fuse' first
Running modprobe fuse
gives me the following result:
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.0-43-Microsoft/modules.dep.bin'
modprobe: FATAL: Module fuse not found in directory /lib/modules/4.4.0-43-Microsoft
After some digging, it seems that fuse
is not supported on WSL, even after the UserVoice page for fuse
support has been up for over 2 years with over 1500 people asking for it. Since sshfs
relies on fuse
(I assume for creating the filesystem that the remote files sit in), this renders sshfs
unusable.
I have found a project (billziss-gh/winfsp
) that seems promising, but I have no idea how to implement it in combination with sshfs
. Is there someone more knowledgeable than I am that can help me get this working?
EDIT: According to this issue, winfsp
will not work with WSL. However, I noticed a project by the same guy (billziss-gh/nfs-win
) that might be useful.
Until a good sshfs filesystem implementation has been created for window have you considered using git? creat repo on server, clone to desktop over ssh and push changes back to the server as you make them. – lijat – 2019-01-10T12:06:15.117