From: Robert Brockway <robert@timetraveller.org>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: CRC calculation in the 1980s
Date: Tue, 19 Sep 2023 09:34:14 +1000 (AEST) [thread overview]
Message-ID: <ba59189c-ed74-1279-eeb7-293f47dd4f09@timetraveller.org> (raw)
In-Reply-To: <87246EC9-0AC8-404E-A8DD-508AB046018B@planet.nl>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
On Tue, 19 Sep 2023, Paul Ruizendaal wrote:
> Any suggestions as to why the on-the-fly algorithm did not catch on more
> in the 1980’s? Maybe it was simply less well known than I think?
Could it have been the per-cpu-second billing that was (fairly?) common at
the time. I was only getting in to Unix in the early 90s but saw the tail
end of that.
Cheers,
Rob
next prev parent reply other threads:[~2023-09-18 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 23:02 [TUHS] " Paul Ruizendaal
2023-09-18 23:34 ` Robert Brockway [this message]
2023-09-19 0:02 ` [TUHS] " segaloco via TUHS
2023-09-19 15:34 ` Paul Winalski
2023-09-19 15:50 ` Dan Cross
2023-09-19 16:22 ` Paul Winalski
2023-09-19 11:42 Noel Chiappa
2023-09-19 12:54 ` Lars Brinkhoff
2023-09-19 16:00 ` Paul Ruizendaal
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=ba59189c-ed74-1279-eeb7-293f47dd4f09@timetraveller.org \
--to=robert@timetraveller.org \
--cc=pnr@planet.nl \
--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).