5 ms·
Why not use FUSE?
by akhilcacharya 8y ago
Why not use FUSE?
- pbalau 8y agoCare to elaborate? A link works :)
- ricketycricket 8y agoThey probably are referring to something like SSHFS that allows you to mount remote filesystems over SSH using FUSE. I have tried this and it doesn't work well. https://github.com/libfuse/sshfs https://github.com/libfuse/sshfs
- pbalau 8y agoThanks. I tried libfuse in the past and I reached the same conclusion.
- akhilcacharya 8y agoI use https://osxfuse.github.io/ https://osxfuse.github.io/ Big file changes are never going to be fast (even doing git operations is pretty slow) but remote interaction can be done via ssh in another tab.
- imbiased 8y agoThis would mean things (compile, run, debug, etc) would be done on the local machine, not on the remote one. Not to mention the network lag if a huge codebase.
- akhilcacharya 8y agoWhat I usually just do is open up a terminal in the FUSE mounted directory and an SSH session in another tab. Run everything on the remote machine and make edits on the local machine using any editor I want. RE: building, compiling without login etc - I have a bunch of aliases that let me do that remotely with ssh. You're still "logging in" but don't need to deal with anything major.
- nikitakit 8y agoI've found that FUSE/sshfs (at least on Mac) doesn't survive network reconnects. Switching WiFi networks, or even having the computer go to sleep, is enough to put it in a state where it can neither be used nor unmounted cleanly.