On 2024-02-26 15:15, Felix Miata wrote:
Carlos E. R. composed on 2024-02-26 14:29 (UTC+0100):
Felix Miata wrote:
Carlos E. R. composed on 2024-02-26 11:55 (UTC+0100):
Felix Miata wrote:
Ben T. Fender composed on 2024-02-25 21:12 (UTC-0500):
Any way to just open a file-mangler on both and drag files back and forth?
It's the only way I do it, mostly (sans mouse) using mc and fcl, which work with or without working GUI:
(man) nfs
for exporting native Linux filesystems (through /etc/exports), which can be mounted just like any other native mounting is done, using fstab entries or other methods for routine ones, and 'mount -t nfs' for the non-routine.
No, you can do it as well with ssh. With sshfs, actually.
"No" what?
That you do not "need" nfs :-)
What did I write that gave you an impression of an association between "need" and "nfs"? I simply use nfs for all accesses and transfers among different hosts on my LAN.
I said "need" instead of need. There is a little difference ;-)
Also with 'mc' but doesn't work fully right.
What doesn't work fully right with mc? With nfs, the LAN becomes, in effect, one native filesystem.
No.
What do you mean "no"? Nfs mounts go into a filesystem tree just like DVDs, USB sticks, NAS devices, RAID devices, etc.
I'm not even considering nfs. We are talking ssh.
There was a bug, years ago, and the "ssh" connection is gone. There is FTP, SFTP, and SMB. SSH (probably called fish elsewhere), is gone. And SFTP, in my experience, has problems each time I try it.
I would have to boot an old virtual install of openSUSE to find an old screenshot of 'mc' of ten years ago to see the differences.
Can you recall whether it was in an nfs or ssh context? There are no old virtual installs here, but there are real installs going as far back as SUSE 8.x, assuming those 20-25 years old PCs still boot. It's been I while since I tried booting any AT form factor K6/2.
Only talking of ssh.
And no, nfs is not the solution for every case.
It's a native one designed for the tasks of transferring and accessing files among hosts on a LAN.
Certainly, I use it. I'm very familiar with it. But it is slower to set it up (more difficult), it needs configuration changes on both sides, and fiddle with the firewalls if they are up. And, is not appropriate for use on internet. Whereas ssh comes installed by default, normally, you have to do nothing. And it is not by default, a simple tick on day zero and it is installed and ready to use. There are more problems, like not supporting translation of users between server and client. Transport not encrypted. No auth involved. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)