The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lyndon@orthanc.ca (Lyndon Nerenberg)
Subject: [TUHS] UUCP "bag" files
Date: Thu, 10 May 2018 21:18:23 -0700	[thread overview]
Message-ID: <3FA3D7C3-CFD1-4FD3-803A-A93B2F5A6F1D@orthanc.ca> (raw)
In-Reply-To: <5f6aa9eb-d56e-7a42-5d61-53d60ed9eefd@spamtrap.tnetconsulting.net>


> On May 10, 2018, at 9:09 PM, Grant Taylor via TUHS <tuhs at minnie.tuhs.org> wrote:
> 
> It's my understanding that bag files were an aggregation / collection of what uucico (or something closely related) would typically write to the modem connected to the remote system.  This output was redirected to a single, monolithic file, called a bag.

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.

There were no "bags."

But there were patches to BSD's UUCP that allowed rnews batching to take place in a 'streaming' manner, avoiding the need to stack up the data files in /var/spool/uucp.  I remember applying patches to the patches running on 'alberta' (U of Alberta) that solved some backlog problems they were having with downstream sites (one of which was mine).

--lyndon



  reply	other threads:[~2018-05-11  4:18 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 [this message]
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=3FA3D7C3-CFD1-4FD3-803A-A93B2F5A6F1D@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).