Computer Old Farts Forum
 help / color / mirror / Atom feed
From: arrigo at alchemistowl.org (Arrigo Triulzi)
Subject: [COFF] UUCP on macOS / *BSD
Date: Mon, 29 Jun 2020 17:53:30 +0200	[thread overview]
Message-ID: <70723375-EF94-4F47-A7D1-54C958F85E9A@alchemistowl.org> (raw)
In-Reply-To: <e74ccf48-2eb7-3f4f-856b-4098ad7cc1cc@tnetconsulting.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]

On 29 Jun 2020, at 02:50, Grant Taylor via COFF <coff at minnie.tuhs.org> wrote:
> Does anyone have any experience with UUCP on macOS or *BSD systems that would be willing to help me figure something out?

I run UUCP on OpenBSD for some very remote sites connected with satellite modems (using UUCP-over-IP, not pure UUCP, where the dial-up script initiates the UUCP exchange). UUCP was recently removed from the base OpenBSD distribution but is still available as a package.

I honestly cannot see it work on macOS because I cannot even remotely imagine Apple having any interest whatsoever in ensuring that it works with the various changes they made to “standard Unix” (launchd, sandboxing, read-only /, etc.).

Are you trying to configure dial-up UUCP or UUCP-over-IP with uucpd?

Arrigo



  parent reply	other threads:[~2020-06-29 15:53 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 [this message]
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
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=70723375-EF94-4F47-A7D1-54C958F85E9A@alchemistowl.org \
    --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).