From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] UUCP on macOS / *BSD
Date: Sun, 28 Jun 2020 18:50:27 -0600 [thread overview]
Message-ID: <e74ccf48-2eb7-3f4f-856b-4098ad7cc1cc@tnetconsulting.net> (raw)
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
-------------- 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/20200628/41c730f3/attachment.bin>
next reply other threads:[~2020-06-29 0:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 0:50 gtaylor [this message]
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
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=e74ccf48-2eb7-3f4f-856b-4098ad7cc1cc@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).