From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] invalid md5/sha1 on plan9port.tgz
Date: Wed, 2 Mar 2005 21:52:10 -0500 [thread overview]
Message-ID: <ee9e417a050302185271d9b8a0@mail.gmail.com> (raw)
In-Reply-To: <20050303020008.GB27404@mero.morphisms.net>
You have the right file. There was a bug in my checksum script.
It was supposed to use mk to update the checksums on demand,
but mk moved and my script didn't get updated.
As William noted, the checksums hadn't been updated in a month,
so no one had actually checked them in a month. I guess that
confirms my suspicion that most people don't care.
> It isn't as if the hash really helps since
> the hash and the distribution are sitting on the same
> filesystem in the first place.
The hash is to allow people to check for network errors during
download, not swtch.com file system corruption.
Russ
next prev parent reply other threads:[~2005-03-03 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 21:27 Matthias Wenzel
2005-03-02 22:23 ` William Josephson
2005-03-02 22:53 ` Matthias Wenzel
2005-03-03 2:00 ` William Josephson
2005-03-03 2:52 ` Russ Cox [this message]
2005-03-03 3:01 ` William K. Josephson
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=ee9e417a050302185271d9b8a0@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
/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).