From: Jim Carpenter <jim@deitygraveyard.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: Tue, 11 Jun 2024 21:37:42 -0400 [thread overview]
Message-ID: <CA+oaVqzBiKqe8BeOsxuS3Ekvff8K4jq973QW2+wrTEnsJJ814Q@mail.gmail.com> (raw)
In-Reply-To: <cww_1ZN0m6uWo5KS8YWdGxFx1D-ReUQwnw9Hlu-yrh3dOZ4Cv-D3uf7zjbsXFytMQrFDhgEjczFlaiyYJVSGRyFJ-7Qfd_yyevuTDzS9QHA=@protonmail.com>
On Tue, Jun 11, 2024 at 2:06 AM segaloco via TUHS <tuhs@tuhs.org> wrote:
> 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.
Bin/cue is a PITA. You've checked that a simple raw image isn't
adequate? Perhaps the viewer was just checking the volume label?
Jim
next prev parent reply other threads:[~2024-06-12 1:38 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 ` [TUHS] " Kevin Bowling
2024-06-12 1:37 ` Jim Carpenter [this message]
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=CA+oaVqzBiKqe8BeOsxuS3Ekvff8K4jq973QW2+wrTEnsJJ814Q@mail.gmail.com \
--to=jim@deitygraveyard.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).