If the "secure" part of scp is bothering you, Richard, you can use rcp instead. But, really it's all the same thing and the normal way of copying files over a network for the last couple decades. You are *always* going to request that a copy happen from one side. In the scp/rcp context, that side going to be the "client", and the automated software that responds to that request on the other side will be the "server", but the server might be receiving the file or sending it. Unless you hire some morse operators to send data back and forth, that's probably about as serverless as you are going to get.
On Mon, Aug 12, 2019 at 12:37 PM Galen Seitz <gal...@seitzassoc.com> wrote: > On 8/12/19 11:43 AM, Richard Owlett wrote: > > > > My post declared SERVER/CLIENT relationships are [expletives deleted ;] > > And I bet your desktop is running an X *server*. Oh, the horrors! > > If you really want to compute like it's 1975, there's always uucp, but I > think you would be much better served (pun intended) by learning how to > use scp or nfs/samba. > > > galen > -- > Galen Seitz > gal...@seitzassoc.com > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
