The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Mary Ann Horton Gmail <mah@mhorton.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Floppy to modern files for Usenet maps
Date: Tue, 9 Jul 2019 16:14:33 -0700	[thread overview]
Message-ID: <14fdf8e6-3e75-404b-29ec-ad93be2412ff@mhorton.net> (raw)
In-Reply-To: <11ba7ef8-a007-2349-5044-bae553019589@spamtrap.tnetconsulting.net>

Well, my intent is to print a packet of Usenet maps to hand out at 
Wednesday night's 50th UNIX Anniversary event in Seattle. I have 15 
copies and a link to the PDF file on stargatemuseum.org. If possible, 
I'd like to add 1 or 2 or 3 of these graphical maps to the packet.

It would also be helpful to have an archived copy of the full UUCP map.  
Stan Barber sent me one some time ago but I misplaced it, and it's not 
coming to his fingertips either. That would obviously be a project for 
later, not a paper handout, but to save on the museum web site.

However, doing a graphical map based on the UUCP map, or even a Usenet 
map after 1987, would likely produce a completely black piece of paper :)

Thanks,

     Mary Ann

On 7/9/19 3:44 PM, Grant Taylor via TUHS wrote:
> On 7/9/19 4:01 PM, Mary Ann Horton Gmail wrote:
>> Thank you, Grant!
>
> You're welcome.
>
>> I have added these to the archive on stargatemuseum.org/maps.  I will 
>> add images from Henry as well.
>
> I'm doing some digging on this.  I'm curious to learn how the data 
> gets used.  My intention, if possible, is to take the most recent data 
> from the UUCP mapping project (currently September '98) and see if 
> it's possible to build updated data sets to generate maps from.  }:-)
>
> I'm guessing that the data from the #N, #O, and #L lines will help 
> with this.  :-D
>
> I do see multiple blank #L lines in the data I'm looking at. Maybe it 
> will be possible to extract something from the #P lines and convert it 
> to pseudo #L lines that can be used.  }:-)
>
>
>

  reply	other threads:[~2019-07-09 23:15 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23 23:10 Mary Ann Horton Gmail
2019-06-23 23:52 ` Arthur Krewat
2019-06-24  0:02   ` Grant Taylor via TUHS
2019-06-24  0:35     ` Mary Ann Horton Gmail
2019-06-24  0:53       ` Arthur Krewat
2019-06-24  0:56         ` Larry McVoy
2019-06-24  1:12           ` Arthur Krewat
2019-06-24  1:31             ` William Pechter
2019-06-24  1:51               ` Arthur Krewat
2019-06-24  1:40         ` Bakul Shah
2019-06-24  3:20           ` Grant Taylor via TUHS
2019-06-24  0:50     ` Arthur Krewat
2019-06-24 21:07     ` Michael Kjörling
2019-06-24 21:30       ` Steve Nickolas
2019-06-24 21:59         ` Gregg Levine
2019-06-23 23:57 ` Grant Taylor via TUHS
2019-06-24  0:40   ` Mary Ann Horton Gmail
2019-06-24  1:37     ` William Pechter
2019-06-24  3:17     ` Jason Stevens
2019-06-24  1:57   ` Steve Nickolas
2019-06-24  2:09     ` pechter
2019-06-24  0:03 ` Theodore Ts'o
2019-06-24  0:19 ` Seth Morabito
2019-06-24  0:33 ` Larry McVoy
2019-06-24  1:58   ` Steve Nickolas
2019-06-25  3:54 ` Jonathan Gevaryahu
2019-06-25 11:21   ` ckeck
2019-07-09 16:28 ` Mary Ann Horton Gmail
2019-07-09 16:53   ` KatolaZ
2019-07-09 17:12   ` Henry Bent
2019-07-09 17:25     ` Seth Morabito
2019-07-09 17:34       ` Henry Bent
2019-07-09 19:19         ` Henry Bent
2019-07-09 19:41           ` Richard Salz
2019-07-09 20:09           ` Grant Taylor via TUHS
2019-07-09 20:58             ` Henry Bent
2019-07-09 20:54           ` Mary Ann Horton Gmail
2019-07-09 21:30             ` Grant Taylor via TUHS
2019-07-09 21:35               ` Grant Taylor via TUHS
2019-07-09 21:37             ` Grant Taylor via TUHS
2019-07-09 21:46               ` Henry Bent
2019-07-09 22:02                 ` Henry Bent
2019-07-09 23:23                   ` Mary Ann Horton Gmail
2019-07-10  0:06                     ` Dan Cross
2019-07-10  0:26                       ` Grant Taylor via TUHS
2019-07-10  0:38                         ` Dan Cross
2019-07-10  0:49                           ` Larry McVoy
2019-07-10  0:57                             ` Clem Cole
2019-07-10  1:26                               ` [TUHS] V0 B Compiler Warren Toomey
2019-07-10  1:29                                 ` Clem Cole
2019-07-10  1:32                                   ` [TUHS] Plot 10 Sources Clem Cole
2019-07-10  2:51                                     ` Charles Anthony
2019-07-10  3:00                                       ` Charles Anthony
2019-07-10  3:01                                       ` Clem Cole
2019-07-10 12:51                                     ` Nelson H. F. Beebe
2019-07-10 14:34                                       ` Clem cole
2019-07-10  1:02                             ` [TUHS] Floppy to modern files for Usenet maps Arthur Krewat
2019-07-10  1:19                               ` Larry McVoy
2019-07-10  1:34                                 ` Dave Horsfall
2019-07-10  0:28                       ` Mary Ann Horton Gmail
2019-07-09 22:01               ` Mary Ann Horton Gmail
2019-07-09 22:44                 ` Grant Taylor via TUHS
2019-07-09 23:14                   ` Mary Ann Horton Gmail [this message]
2019-07-10  0:24                     ` Grant Taylor via TUHS
2019-07-10  1:13                       ` Mary Ann Horton Gmail
2019-07-09 17:33     ` Clem Cole
2019-07-15  3:21   ` [TUHS] Historical " Mary Ann Horton Gmail

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=14fdf8e6-3e75-404b-29ec-ad93be2412ff@mhorton.net \
    --to=mah@mhorton.net \
    --cc=tuhs@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).