From: "Leonard Milcin, Jr" <thervoy@post.pl>
To: Stephen Satchell <list@fluent2.pyramid.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: (OT) md5sum proving to be an EXCELLENT memory test
Date: Sun, 20 Apr 2003 23:58:14 +0200 [thread overview]
Message-ID: <3EA317F6.2000504@post.pl> (raw)
In-Reply-To: <5.2.0.9.0.20030420132915.01d28c40@fluent2.pyramid.net>
Stephen Satchell wrote:
> (...)
> as perfect.) Perform md5sum on the files on the server and save the
> results, and the signatures would be different from run to run on the
> same files.
>
> Incompatible RAM.
> (...)
I had the same situation with some cheap mobo (ECS K7S5A+) of friend of
mine. You don't need to check md5sums. Why is MD5 better than any other
method? I just simply found, that when I copy file A to B, and then A to
C, it is possible that B and C differs. Most of the time with one byte.
The advice is to use some good memory test suite from time to time - it
will do better its job than you just checking signatures on large files.
Regards,
Leonard
next prev parent reply other threads:[~2003-04-20 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 3:11 Linux 2.5.68 Linus Torvalds
2003-04-20 4:57 ` Ben Collins
2003-04-20 13:23 ` irq balancing; kernel vs. userspace Sean Neakums
2003-04-20 18:31 ` Arjan van de Ven
2003-04-20 18:37 ` Kevin P. Fleming
2003-04-20 19:10 ` Arjan van de Ven
2003-04-20 18:55 ` Sean Neakums
2003-04-20 20:11 ` Zwane Mwaikambo
[not found] ` <Pine.LNX.4.50.0304201605360.17265-100000@montezuma.mastece nde.com>
2003-04-20 20:43 ` (OT) md5sum proving to be an EXCELLENT memory test Stephen Satchell
2003-04-20 21:58 ` Leonard Milcin, Jr [this message]
2003-04-20 23:45 ` Stephen Satchell
[not found] ` <3EA3EC75.35988618@gmx.de>
2003-04-21 13:46 ` Stephen Satchell
2003-04-23 19:33 ` 2.5.68: net/decnet/dn_route.c doesn't compile Adrian Bunk
2003-04-23 19:46 ` Steven Whitehouse
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=3EA317F6.2000504@post.pl \
--to=thervoy@post.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=list@fluent2.pyramid.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.