From mboxrd@z Thu Jan 1 00:00:00 1970 From: gtaylor at tnetconsulting.net (Grant Taylor) Date: Mon, 29 Jun 2020 21:50:07 -0600 Subject: [COFF] UUCP on macOS / *BSD In-Reply-To: <20200630034627.GC21942@tau1.ceti.pl> References: <70723375-EF94-4F47-A7D1-54C958F85E9A@alchemistowl.org> <8dbc09dd-07be-a7ab-082e-edc2e74f0d67@tnetconsulting.net> <7aff4a42-0109-2278-c573-7e29e878cd57@tnetconsulting.net> <20200630022632.GA21942@tau1.ceti.pl> <76024752-a506-abf1-1990-0b66630bb7db@spamtrap.tnetconsulting.net> <20200630032647.GB21942@tau1.ceti.pl> <20200630034627.GC21942@tau1.ceti.pl> Message-ID: <3c997004-f77c-1691-380e-4662375d46d8@spamtrap.tnetconsulting.net> On 6/29/20 9:46 PM, Tomasz Rola wrote: > And BTW, looking how they did it on systems where things worked might > give you a clue, too. For example, when you install a package, there > might be a script setting thing up in a correct way. Agreed. I have four systems in this current micro UUCP network, one Ubuntu and three Gentoo, all working happily with each other. The macOS system that I am working on adding to the mix is the cranky one. And even then, it's only cranky if you don't sweet talk it. If you do sweet talk it, it works like it should. Here, sweet talk means adding "-r" to uuto and uucp, then calling uucico as the UUCP user. -- Grant. . . . unix || die -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4013 bytes Desc: S/MIME Cryptographic Signature URL: