When using TWM I always want to maintain the uniformity and consistency of the environment.
This is not a sophisticated environment like modern KDE, Gnome, Xfce ... But it's an environment that has had its days of glory and sophistication.
Some tools help give a more "techno" feel to this file manager.
One such tool is Xfe - a very lightweight and simple file manager that follows the MC approach (Norton Commander for unices).
It does not have many sophistications, but it has some features that help like the "terminal button" and the panning of panels.
However ... Today I needed to access a filesystem on a remote server via ssh ... And unfortunately it does not do it directly.
My solution:
I have used (learned) sshfs(1). I just put the remote file in a directory that I have access to and navigate through it using Xfe.
Simple and practical.
In this case I did not use the 'user@' before remote.server because I have direct access to the remote sshd.
The bottom line is that when we try to solve this kind of common problem, we end up looking for "advanced features" when the solution is simpler than installing a super-dupper-bloated utility to do our brainwork.
Result:
This is not a sophisticated environment like modern KDE, Gnome, Xfce ... But it's an environment that has had its days of glory and sophistication.
Some tools help give a more "techno" feel to this file manager.
One such tool is Xfe - a very lightweight and simple file manager that follows the MC approach (Norton Commander for unices).
It does not have many sophistications, but it has some features that help like the "terminal button" and the panning of panels.
However ... Today I needed to access a filesystem on a remote server via ssh ... And unfortunately it does not do it directly.
My solution:
I have used (learned) sshfs(1). I just put the remote file in a directory that I have access to and navigate through it using Xfe.
Simple and practical.
me@local$ sshfs remote.server:/home/target /local/mountpoint
In this case I did not use the 'user@' before remote.server because I have direct access to the remote sshd.
The bottom line is that when we try to solve this kind of common problem, we end up looking for "advanced features" when the solution is simpler than installing a super-dupper-bloated utility to do our brainwork.
Result: