From: lm at mcvoy.com (Larry McVoy)
Subject: [COFF] UUCP on macOS / *BSD
Date: Mon, 29 Jun 2020 08:37:39 -0700 [thread overview]
Message-ID: <20200629153739.GH16252@mcvoy.com> (raw)
In-Reply-To: <e74ccf48-2eb7-3f4f-856b-4098ad7cc1cc@tnetconsulting.net>
So UUCP, depending which version, really needed a baby sitter. I think
the latest one was sort of reliable but my ancient memory is that you
had to unwedge things on a daily basis.
On Sun, Jun 28, 2020 at 06:50:27PM -0600, Grant Taylor via COFF wrote:
> Does anyone have any experience with UUCP on macOS or *BSD systems that
> would be willing to help me figure something out?
>
> I'm working on adding a macOS X system to my micro UUCP network and running
> into some problems.
>
> - uuto / uucp copy files from my non-root / non-(_)uucp user to the UUCP
> spool. But the (demand based) ""call (pipe over SSH) is failing.
> - running "uucico -r1 -s <remote system name> -f" as the (_)uucp user (via
> sudo) works.
> - I'm using the pipe port type and running things over an SSH connection.
> - The (_)uucp user can ssh to the remote system as expected without any
> problems or being prompted for a password. (Service specific keys w/ forced
> command.)
>
> I noticed that the following files weren't set UID or GID like they are on
> Linux. But I don't know if that's a macOS and / or *BSD difference when
> compared to Linux.
>
> /usr/bin/uucp
> /usr/bin/uuname
> /usr/bin/uustat
> /usr/bin/uux
> /usr/sbin/uucico
> /usr/sbin/uuxqt
>
> Adding the set UID & GID bits allowed things to mostly work.
>
> Aside: Getting the contemporary macOS so that I could edit the
> (/usr/share/uucp/) sys & port files was a treat.
>
> I figured that it was worth inquiring if anyone had any more experience /
> tips / gotchas before I go bending ~> breaking things even more.
>
> Thank you.
>
>
>
> --
> Grant. . . .
> unix || die
>
>
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2020-06-29 15:37 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 [this message]
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
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=20200629153739.GH16252@mcvoy.com \
--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).