From: lyndon@orthanc.ca (Lyndon Nerenberg)
Subject: [TUHS] UUCP "bag" files
Date: Thu, 10 May 2018 20:58:18 -0700 [thread overview]
Message-ID: <AF685A3D-CD03-4FB2-B5F7-16C4CF14A477@orthanc.ca> (raw)
In-Reply-To: <3d317540-757f-7a24-941d-b8f0ced91e87@spamtrap.tnetconsulting.net>
> On May 10, 2018, at 8:42 PM, Grant Taylor via TUHS <tuhs at minnie.tuhs.org> wrote:
>
> On 05/10/2018 05:38 PM, Lyndon Nerenberg wrote:
>> We always referred to them as "rnews batches," since that's what they were.
>
> Not if there's also email / commands / files transfers in the batch. ;-)
UUCP would transfer many batch jobs in a single session, Each job was a single command. So you would have a mix of 'uux remote!rmail' and 'uux remote!rnews' all stacked up in the job queue to be transferred and executed on the remote host.
'uucp' and 'uux' just created remote batch jobs in a queue directory. When 'uucico' eventually fired off, it would send the command files over, along with any associated data files.
You could 'uucp' and 'uux' anything you liked, modulo restrictions placed upon you by the administrators of the local and remote hosts.
--lyndon
next prev parent reply other threads:[~2018-05-11 3:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 3:49 Grant Taylor
2018-05-10 3:51 ` Lyndon Nerenberg
2018-05-10 4:53 ` Grant Taylor
2018-05-10 5:03 ` Bakul Shah
2018-05-10 15:46 ` Mary Ann Horton
2018-05-10 16:08 ` Chet Ramey
2018-05-10 14:25 ` Chet Ramey
2018-05-10 15:28 ` Grant Taylor
2018-05-10 16:03 ` Dan Cross
2018-05-10 16:24 ` Grant Taylor
2018-05-10 14:10 ` John P. Linderman
2018-05-10 23:38 ` Lyndon Nerenberg
2018-05-11 0:24 ` John P. Linderman
2018-05-11 3:51 ` Grant Taylor
2018-05-11 3:42 ` Grant Taylor
2018-05-11 3:58 ` Lyndon Nerenberg [this message]
2018-05-11 4:09 ` Grant Taylor
2018-05-11 4:18 ` Lyndon Nerenberg
2018-05-12 4:39 ` Grant Taylor
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=AF685A3D-CD03-4FB2-B5F7-16C4CF14A477@orthanc.ca \
--to=lyndon@orthanc.ca \
/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).