From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: do md5sums differ across architectures?
Date: Thu, 22 Feb 2001 13:57:33 -0500 [thread overview]
Message-ID: <200102221857.f1MIvW706290@ashley.ivey.uwo.ca> (raw)
Hi,
Just to have a bit of fun, how about this (3 different systems)
Each generates a different md5sum but all generate the same cksum!
(and adding -b to md5sum makes no difference)
Darwin khendricksmac 1.2 Darwin Kernel Version 1.2: Wed Aug 30 23:32:53 PDT 2000; root:xnu/xnu-103.obj~1/RELEASE_PPC Power Macintosh powerpc
[khendricksmac:~] kbhend% md5sum oo619b_src.tar.bz2
9c6a44ad66572c834e282eb1ec665374 oo619b_src.tar.bz2
[khendricksmac:~] kbhend% cksum oo619b_src.tar.bz2
2458761606 56057947 oo619b_src.tar.bz2
SunOS crunch 5.7 Generic_106541-04 sun4u sparc SUNW,Ultra-250
kbhend$ md5sum oo619b_src.tar.bz2
278c21a764126027cba9cb685b7e96cf oo619b_src.tar.bz2
kbhend$ cksum oo619b_src.tar.bz2
2458761606 56057947 oo619b_src.tar.bz2
Linux localhost 2.2.17pre10-ben2 #3 Sun Aug 13 13:03:45 EDT 2000 ppc unknown
[kbhend@localhost /src2]$ md5sum oo619b_src.tar.bz2
c4a5d7bda6973f6b56e725295d1b3dfb oo619b_src.tar.bz2
[kbhend@localhost /src2]$ cksum oo619b_src.tar.bz2
2458761606 56057947 oo619b_src.tar.bz2
I guess md5sum is not a very reliable or consistent checksum measure for moving
files between ppc linux, MacOSX, and Solaris 7 Sparc.
Back to the old cksum for me.
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-02-22 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 18:57 Kevin B. Hendricks [this message]
2001-02-22 20:09 ` do md5sums differ across architectures? Jeffrey Hawkins
2001-02-22 21:13 ` Kevin B. Hendricks
2001-02-22 22:12 ` Kevin B. Hendricks
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 16:03 Kevin B. Hendricks
2001-02-22 17:12 ` mod+linuxppc-embedded
2001-02-22 15:24 Kevin B. Hendricks
2001-02-22 15:49 ` Ethan Benson
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=200102221857.f1MIvW706290@ashley.ivey.uwo.ca \
--to=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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).