public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Ethan Benson <erbenson@alaska•net>
To: linuxppc-dev@lists•linuxppc.org
Subject: Re: do md5sums differ across architectures?
Date: Thu, 22 Feb 2001 06:49:14 -0900	[thread overview]
Message-ID: <20010222064913.N18058@plato.local.lan> (raw)
In-Reply-To: <200102221524.f1MFO2709134@ashley.ivey.uwo.ca>; from khendricks@ivey.uwo.ca on Thu, Feb 22, 2001 at 10:24:01AM -0500

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

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/

[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]

  reply	other threads:[~2001-02-22 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 15:24 do md5sums differ across architectures? Kevin B. Hendricks
2001-02-22 15:49 ` Ethan Benson [this message]
  -- 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 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

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=20010222064913.N18058@plato.local.lan \
    --to=erbenson@alaska$(echo .)net \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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