From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: Ethan Benson <erbenson@alaska.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: do md5sums differ across architectures?
Date: Thu, 22 Feb 2001 11:03:45 -0500 [thread overview]
Message-ID: <200102221603.f1MG3k716096@ashley.ivey.uwo.ca> (raw)
Hi,
No, ftping in binary.
I am running textutils-2.0e6 rpm (the latest) from www.linuxppc.org which supplies
md5sum
I will check what I am running on Solaris.
hmm, I wonder which one is broken?
Thanks,
Kevin
On Thursday, February 22, 2001, at 10:49 AM, Ethan Benson wrote:
> On Thu, Feb 22, 2001 at 10:24:01AM -0500, Kevin B. Hendricks wrote:
> >
> > Hi,
> >
> > I ran md5sum on a big bz2 archive on my ppc linux box and then
> > ftp'd it to my Sun Solaris 7 box at work.
> >
> > I checked it with md5sum on that machine and it differed.
> >
> > Okay I thought, a bad packet during upload.
> >
> > So I tried again, same result.
> >
> > I then passed back and forth (known good archives) and the md5sums
> > were different.
> >
> > Okay, I thought maybe an endian issue but both Solaris Sparc and PPC
> > Linux are big endian.
> >
> > Should these sums be different?
>
> no, that would rather defeat the purpose of md5sum hashes. one of
> your md5sum programs is broken.
>
> or perhaps you ftp'd in text mode instead of binary mode.
>
> --
> Ethan Benson
> http://www.alaska.net/~erbenson/
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-02-22 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 16:03 Kevin B. Hendricks [this message]
2001-02-22 17:12 ` do md5sums differ across architectures? mod+linuxppc-embedded
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 18:57 Kevin B. Hendricks
2001-02-22 20:09 ` Jeffrey Hawkins
2001-02-22 21:13 ` Kevin B. Hendricks
2001-02-22 22:12 ` Kevin B. Hendricks
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=200102221603.f1MG3k716096@ashley.ivey.uwo.ca \
--to=khendricks@ivey.uwo.ca \
--cc=erbenson@alaska.net \
--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).