From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] UUCP "bag" files
Date: Wed, 9 May 2018 22:53:01 -0600 [thread overview]
Message-ID: <042d9aff-82df-d267-e585-3dfe57b06252@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <9D7839FC-A3EB-4211-887D-BCE67229E1D6@orthanc.ca>
On 05/09/2018 09:51 PM, Lyndon Nerenberg wrote:
> What are they to begin with? Having run some "major" UUCP hubs in the
> day, I have no clue what a UUCP "bag" is ...
I see them in the context of Usenet via UUCP, so rnews.
The best that I can tell is that they are simply the messages that need
to be sent written into a single file that is then transferred via some
mechanism, ftp being a common one.
It looks like it might be the output of nntpsend or send-nntp. Or
perhaps output of downstream / related UUCP commands.
I often see it mentioned in close proximity of DNews.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3982 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180509/0da7803a/attachment.bin>
next prev parent reply other threads:[~2018-05-10 4:53 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 [this message]
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
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=042d9aff-82df-d267-e585-3dfe57b06252@spamtrap.tnetconsulting.net \
--to=gtaylor@tnetconsulting.net \
/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).