The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: 5ESS UNIX RTR Reference Manual - Issue 10 (2001)
Date: Mon, 10 Jun 2024 23:59:38 -0700	[thread overview]
Message-ID: <CAK7dMtBqRFYisz0nDd+T-0YkGsk9DQ2K3L6xmnUyKK-_7wkxUQ@mail.gmail.com> (raw)
In-Reply-To: <cww_1ZN0m6uWo5KS8YWdGxFx1D-ReUQwnw9Hlu-yrh3dOZ4Cv-D3uf7zjbsXFytMQrFDhgEjczFlaiyYJVSGRyFJ-7Qfd_yyevuTDzS9QHA=@protonmail.com>

On Mon, Jun 10, 2024 at 11:06 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
>
> Good evening, while I'm still waiting on the full uploads to progress (it's like there's a rule any >100MB upload to archive.org for me has to fail like 5 times before it'll finally go...) I decided to scrape out the UNIX RTR manual from a recent trove of 5ESS materials I received and tossed it up in a separate upload:
>
> https://archive.org/details/5ess-switch-unix-rtr-operating-system-reference-manual-issue-10
>
> This time around I've got Issue 10 from December 2001.  The last issue of this particular manual I found on another 5ESS disc is Issue 7 from 1998 which I shared previously (https://ia601200.us.archive.org/view_archive.php?archive=%2F12%2Fitems%2F5ess-switch-dk5e-cd-1999-05%2F5ESS-DK5E.zip&file=5EDOCS%2F93447.PDF)
>
> The manual is in "DynaText" format on the CD in question, unlike Issue 7 which was already a PDF on its respective CD.  I used print-to-PDF to generate the above linked copy.  Given that the CD itself is from 2007, this may point to UNIX RTR having no significant user-visible changes from 2001 to 2007 that would've necessitated manual revisions.
>
> In any case, I intend to upload bin/cue images of all 7 of the CDs I've received which span from 1999 to 2007, and mostly concern the 5ESS-2000 switch from the administrative and maintenance points of view.  Once I get archive.org to choke these files down I also intend to go back around to the discs I've already archived and reupload them as proper bin/cue rips.  I was in a hurry the last time around and simply zipped the contents from the discs, but aside from just being good archive practice, I think bin/cue is necessary for the other discs as they seem to have control information in the disc header that is required by the interactive documentation viewers therein.
>

I have some of these CDs already and can compare notes with you:
DK5E-CD from 2004, OA&M from 2008.

I think you can just copy the SGML files to a HDD once you have
DynaText installed, so whatever is funky about the CDs is not terribly
important for use aside from the fidelity of your archival.  Some of
my CDs also use something called Eloquent Presenter which seems like a
HyperCard style program.  All the docs that aren't SGML are PDF,
including most of the schematics, plenty which look like scans of
originals.

> All that to say, the first pass will result in bin/cues which aren't easily readable through archive.org's interface, but I intend to also swing back around on these new discs and provide zips of the contents as well to ensure the archives are both correct (bin/cue) and easily navigable (zip).
>
> As always, if you have any such documentation or leads on where any may be awaiting archival, I'm happy to take on the work!

FWIW I have a fully working 5ESS that I turned off last week (actually
a 7 R/E - 3B21D, CM3 (Global Message Server), 20k lines a mix of POTS,
ISDN, PRI trunks) and it is coming home with me at the end of the
month.  Small matters of loading, unloading, AC PDU and getting a
sizable DC power plant and unbounded wiring are in my future.  Why? I
dunno but full send.  I need to have a think on how to be public with
all this going forward, I do want to share the system and the goal is
historical preservation and learning with interested parties.

> - Matt G.

  reply	other threads:[~2024-06-11  7:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  6:06 [TUHS] " segaloco via TUHS
2024-06-11  6:59 ` Kevin Bowling [this message]
2024-06-12  1:37 ` [TUHS] " Jim Carpenter
2024-06-12  3:34   ` segaloco via TUHS
2024-06-12  5:43     ` Andrew Warkentin
2024-06-12  7:01       ` Wesley Parish
2024-06-12  8:12       ` Ralph Corderoy
2024-06-12  8:41         ` Arno Griffioen via TUHS
2024-06-12 16:30           ` segaloco via TUHS

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=CAK7dMtBqRFYisz0nDd+T-0YkGsk9DQ2K3L6xmnUyKK-_7wkxUQ@mail.gmail.com \
    --to=kevin.bowling@kev009.com \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@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).