Even USB operates on a client/server model. Users who do not see the negotiations that occur behind the scene are, by definition, consumers of the standard.
<sales-pitch> Hello Mr/Mrs. Future Customer! For $50 I'll write you a program* that initiates peer-to-peer** data transfer over wifi. I also offer phone support for the app! If you lock in your contract now this service will be made available for the low price of $0.20/min*** Buy now before I realize that I already have a better job! *shell script **not actually P2P ***offer only valid as long as it interests me </sales-pitch> For real though, I wonder how much I could get paid for a BASH script that issues a sequence of commands to connect to a wifi network, transfer a file, and then immediately disconnect from said wifi network. It would be like MAGIC. On Mon, Aug 12, 2019 at 2:50 PM Rodney W. Grimes <free...@gndrsh.dnsmgr.net> wrote: > > On 08/12/2019 11:51 AM, Rodney W. Grimes wrote: > > >> On 08/12/2019 08:28 AM, Bill Barry wrote: > > >>> On Mon, Aug 12, 2019 at 7:57 AM Richard Owlett <rowl...@cloud85.net> > wrote: > > >>>> > > >>>> On 08/11/2019 10:04 AM, Nat Taylor wrote: > > >>>>> so, you don't want to use the "ip" command to set your network > addresses > > >>>>> then use scp to copy files between the machines? > > >>>> > > >>>> Browsing the man page for scp suggests it is massive overkill for a > > >>>> 2-node LAN of "trusted" machines. [The WiFi may be vulnerable, but > the > > >>>> two laptops have only a minimal Debian installation and have > _*NOTHING*_ > > >>>> on them that did not come from the installation DVD ;] > > >>> > > >>> You could use ftp > > >>> > https://linuxconfig.org/how-to-configure-ftp-server-on-debian-9-stretch-linux > > >>> but I don't think it is much easier to configure than ssh/scp. > > >> > > >> It's not a complexity issue so much as suitable topology. > > >> A 2-node LAN has to be as close as possible to a peer2peer network. > > >> I keep being referred to tools suitable for a client/server model > > >> capable of handling a massive multiplicity of nodes. > > >> > > >> I've been a computer *consumer* since ~1961. Became much more involved > > >> with system details when introduced to Debian 6. > > > > > > Simply nfs share the systems disks with each other in a softmount > > > situation (need softmounts/backgroundmounts to prevent deadly embrace > > > during boot(s)) > > > > > > You may even want to -maproot=root. > > > > > > man exports > > > and anything in that man pages SEE ALSO section. > > > > > > > https://manpages.debian.org/buster/nfs-kernel-server/exports.5.en.html > > *EXPLICITLY* refers to a *SERVER* > > > > My post declared SERVER/CLIENT relationships are [expletives deleted ;] > > Then I say your in /dev/null land, your simply NOT > going to find anything that does not mention client > or server AND does mention the types of things your > looking for. > > If it uses a network it is very likely to say someplace > server or client, even though often these words are used > incorrectly or not of correct normative form. > > One side must initiate the connection or start the > information flow, in networking that is almost always > going to be refered to as the client, and the entity > it decides to contact is almost always going to > be called a server. > > Now, rather than having us be your google engine.... > And rather than scream that our answers did not meet your criteria... > > -- > Rod Grimes > rgri...@freebsd.org > _______________________________________________ > 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
