The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Setting up an X Development Environment for Mac OS
Date: Sat, 28 Jan 2023 17:31:49 -0700	[thread overview]
Message-ID: <CAK7dMtCGLg47RdZ5n028t9OA=A_=K+twRpZYnRcsocLm9PdQMg@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2301290902050.61978@aneurin.horsfall.org>

I'm not sure about 8mm tape specifically but the Exabyte drives that
were common on 1990s UNIX systems failed a lot.

There was a large proliferation of tape technology in the 1980s and
1990s, many of them not great in any dimension.

DLT, LTO, and especially the "enterprise" ranges from StorageTek or
IBM from any time period are all extremely reliable.

On Sat, Jan 28, 2023 at 3:16 PM Dave Horsfall <dave@horsfall.org> wrote:
>
> On Fri, 27 Jan 2023, Larry McVoy wrote:
>
> [...]
>
> > I've never seen a more fragile system than those exabyte.  By
> > comparison, the old SCSI QIC 150s, while small, were industructible, I
> > think you could have used the tapes as hammers and they'd still read.
> > Same thing for 9 track.
>
> My experience with Exabytes was different; we used "data" tapes, not the
> cheaper "video" tapes and had no problems over many years.
>
> In fact, in https://en.wikipedia.org/wiki/Data8 we see:
>
>     ``The cassettes have the same dimensions and construction as the
>       cassettes used in 8 mm video format recorders and camcorders.''
>
> In other words, they are not the same thing...
>
> -- Dave

  reply	other threads:[~2023-01-29  0:33 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 20:38 Noel Chiappa
2023-01-25 21:25 ` Clem Cole
2023-01-26  6:30   ` Lars Brinkhoff
2023-01-26 10:56     ` Ralph Corderoy
2023-01-26 12:01       ` arnold
2023-01-26 13:25         ` Lars Brinkhoff
2023-01-26 15:28       ` [TUHS] " josh
2023-01-26 16:07         ` [TUHS] " segaloco via TUHS
2023-01-26 16:48           ` emanuel stiebler
2023-01-26 21:19             ` segaloco via TUHS
2023-01-26 22:51               ` Andy Kosela
2023-01-27  0:48                 ` segaloco via TUHS
2023-01-27  4:07                   ` Will Senn
2023-01-27 14:08                     ` Chet Ramey
2023-01-27 14:49                       ` Ron Natalie
2023-01-27 15:53                     ` Dan Cross
2023-01-27 16:12                       ` [TUHS] NEXTSTEP 486 [was " Charles H Sauer (he/him)
2023-01-27 14:17             ` [TUHS] " Ralph Corderoy
2023-01-27 13:56         ` Ralph Corderoy
2023-01-27 14:54           ` Ron Natalie
2023-01-27 16:10             ` Larry McVoy
2023-01-28 22:15               ` Dave Horsfall
2023-01-29  0:31                 ` Kevin Bowling [this message]
2023-01-29 11:07                   ` emanuel stiebler
2023-01-27 21:42             ` Tom Perrine
2023-01-28  2:18               ` Larry McVoy
2023-01-28  2:49                 ` Tom Perrine
2023-01-26  6:32 ` Lars Brinkhoff
2023-01-26  9:45 ` emanuel stiebler via TUHS
  -- strict thread matches above, loose matches on Subject: below --
2023-01-25  1:46 [TUHS] " Will Senn
2023-01-25  7:45 ` [TUHS] " segaloco via TUHS
2023-01-25  8:00   ` Lars Brinkhoff
2023-01-25 16:41   ` Rich Salz
2023-01-25 19:53     ` Theodore Ts'o
2023-01-25 20:04       ` Dan Cross
2023-01-25 20:23         ` Larry McVoy
2023-01-25 20:27           ` Chet Ramey
2023-01-27  4:49         ` Theodore Ts'o
2023-01-27 18:05           ` Henry Mensch
2023-01-27 18:24             ` Charles H Sauer (he/him)
2023-01-26 13:17       ` Marc Donner

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='CAK7dMtCGLg47RdZ5n028t9OA=A_=K+twRpZYnRcsocLm9PdQMg@mail.gmail.com' \
    --to=kevin.bowling@kev009.com \
    --cc=dave@horsfall.org \
    --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).