RE: Linux v. Microsoft MD5SUMS
On 25 May 2000, Brooks R. Robinson wrote:
The problem is that under MSDog/Windoze md5sum is calculating the
MD5SUM on the .exe as if it was a text file, where as Linux
recognizes that it is a binary file and calculates the binary hash.
force msdog to calculate the binary hash with -b eg.
MD5SUM -b md5sum.exe
> Under Windows NT Workstation, I get:
> a75c7207e00a30f97a3cc4107fc5d88e md5sum.exe
> Under an i386 Potato box I get:
> 799812dfc33eeeb8c28d53b7469f7197 md5sum.exe
> > -----Original Message-----
> > From: J.A. Bezemer [mailto:email@example.com]
> > Sent: Wednesday, May 24, 2000 2:57 PM
> > To: Brooks R. Robinson
> > Cc: Debian-Cd
> > Subject: Re: Linux v. Microsoft MD5SUMS
> > On Wed, 24 May 2000, Brooks R. Robinson wrote:
> > > Greetings,
> > > Since I don't have a ROM burner at home, and I have access
> > to one at work,
> > > I burn all my images at work. Consequently, I am relegated to
> > the Microsoft
> > > Environment. So, when I resync my images, it's done under NT
> > workstation.
> > > I don't know much about MD5SUMS, but they seems to be different
> > given Linux
> > > v. Microsoft? Why is this? Is there something to compensate?
> > This should not be. I suppose you use the `md5sum.exe' of the
> > Pseudo-Image Kit
> > (http://cdimage.debian.org/~costar/pseudo-image-kit/), and otherwise
> > you should try that one. For example `md5sum md5sum.exe' should give
> > exactly the same result on Linux and Windows. If it doesn't, please
> > report back and tell me both md5sum outputs.
> > Regards,
> > Anne Bezemer