The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] UUCP "bag" files
Date: Fri, 11 May 2018 22:39:03 -0600	[thread overview]
Message-ID: <3b2c9232-055f-af38-f94b-8c91702599f5@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <3FA3D7C3-CFD1-4FD3-803A-A93B2F5A6F1D@orthanc.ca>

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

On 05/10/2018 10:18 PM, Lyndon Nerenberg wrote:
> Yes, but rnews understood batching from day one.  It would have been 
> insane to execute rnews on each and every article sent across.  (I made 
> that mistake in a config file once; that the remote host didn't completely 
> die was a testament to CTIX.)  That's why every news transport batched 
> up multiple articles into a single 'uux remote!rnews' job.  This existed 
> from at least the bnews software, and we always called them "news batches" 
> or similar.

Well, I don't know what to say.  After a LOT of research, extracting old 
archives, digging through a LOT of things, I can only come to the 
conclusion that what have been called "bag" files in the circles that 
I've traveled in are in fact the output of batcher, thus standard "#! 
rnews <length>" files.

I think part of my confusion was that I was working with using UUCP at 
the same time to transport files via sneaker net using something similar 
to batcher / rnews files.  I guess I conflated the two things.

I'm sorry for the confusion.

> There were no "bags."

They might not have been a different format (like I thought) but there 
were most definitely referred to as "bag" files in the circles that I've 
traveled.

I have repeatedly found reference to them, around DNews, and being 
called "bag" files because of the ".bag" file extension that they had.

I haven't been able to find anything to indicate if the nickname came 
from the file extension or if the file extension came from the nickname.

chicken ("bag") <-> egg (.bag extension) ¯\_(ツ)_/¯

Thank you all for your input.

I'm sorry for the confusion.



-- 
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/20180511/b3043b4c/attachment.bin>


      reply	other threads:[~2018-05-12  4:39 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
2018-05-11  4:09           ` Grant Taylor
2018-05-11  4:18             ` Lyndon Nerenberg
2018-05-12  4:39               ` Grant Taylor [this message]

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=3b2c9232-055f-af38-f94b-8c91702599f5@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).