From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] [simh] 2bsd tarball
Date: Wed, 12 Aug 2020 09:55:49 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2008120942280.10877@aneurin.horsfall.org> (raw)
In-Reply-To: <2d723104-6461-08ba-9235-99b06622f9fa@softjar.se>
On Wed, 29 Jul 2020, Johnny Billquist wrote:
> However, seek times on DECtape aren't really comparable to magtape
> either. Because DECtape deals with absolute block numbers. So you can
> always, no matter where you are, find out where you are, and how far you
> will need to move to get to the correct block.
>
> With magtapes, this is pretty much impossible. You'll have to rewind,
> and then start seeking.
Not if you used 512-byte blocks, and mounted it read-only; that way, you
could use it as a file system (and I did, just for fun). Oh, you also
needed a clever tape driver, of course. And the IRG was a bit of a
problem, chewing up a lot of tape space.
I posted this here a while back, and some idiot (his name is not
important) practically called me a liar, until he was handed his arse
on a plate by someone else with better knowledge than him.
-- Dave
next prev parent reply other threads:[~2020-08-11 23:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 23:03 [TUHS] " Will Senn
2020-07-29 0:09 ` Warner Losh
2020-07-29 0:19 ` Clem Cole
2020-07-29 0:45 ` Will Senn
2020-07-29 0:46 ` Will Senn
2020-07-29 0:21 ` Clem Cole
2020-07-29 9:50 ` [TUHS] [simh] " Johnny Billquist
2020-07-29 13:52 ` John Cowan
2020-07-29 14:30 ` Johnny Billquist
2020-08-11 23:41 ` Dave Horsfall
[not found] ` <5A12E0BB-4FFF-4C3E-B486-D4E852FAA97F@comcast.net>
2020-07-29 14:29 ` Johnny Billquist
2020-08-11 23:55 ` Dave Horsfall [this message]
2020-07-29 13:42 ` [TUHS] 2bsd tarball -> pdtar, with a side of uuslave John Gilmore
2020-07-29 15:40 ` Clem Cole
2020-07-29 19:34 ` Richard Salz
2020-07-29 19:42 ` Warner Losh
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=alpine.BSF.2.21.9999.2008120942280.10877@aneurin.horsfall.org \
--to=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).