From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] UUCP on macOS / *BSD
Date: Mon, 29 Jun 2020 21:50:07 -0600 [thread overview]
Message-ID: <3c997004-f77c-1691-380e-4662375d46d8@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20200630034627.GC21942@tau1.ceti.pl>
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: <http://minnie.tuhs.org/pipermail/coff/attachments/20200629/3f91e63f/attachment.bin>
next prev parent reply other threads:[~2020-06-30 3:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 0:50 gtaylor
2020-06-29 15:37 ` lm
2020-06-29 16:13 ` gtaylor
2020-07-05 6:30 ` dave
2020-06-29 15:53 ` arrigo
2020-06-29 16:42 ` gtaylor
2020-06-29 17:20 ` clemc
2020-06-29 20:06 ` gtaylor
2020-06-29 20:59 ` clemc
2020-06-30 2:26 ` rtomek
2020-06-30 3:19 ` gtaylor
2020-06-30 3:26 ` rtomek
2020-06-30 3:46 ` rtomek
2020-06-30 3:50 ` gtaylor [this message]
2020-06-30 3:47 ` gtaylor
2020-06-29 17:22 ` arrigo
2020-06-29 20:18 ` gtaylor
2020-06-29 20:31 ` gtaylor
2020-07-01 17:32 ` gtaylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c997004-f77c-1691-380e-4662375d46d8@spamtrap.tnetconsulting.net \
--to=coff@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).