Andy Green wrote:
On 01/07/11 14:51, Somebody in the thread at some point said:
>>>> Can anybody with a clean F12 vanilla copy check if they can reproduce
>>>> the problem?
>>> No problem here.
> Have you god an md5sum of the sha512 binary? Mine is:
> [root@sheeva ~]# md5sum /vservers/f12/usr/bin/sha512sum
> 7667ac4b53249e53533860518e916719 /vservers/f12/usr/bin/sha512sum
[root@ivmon ~]# md5sum `which sha512sum`
0b45bcdf989568fc1dfcc38a7063651a /usr/bin/sha512sum
[root@ivmon ~]# ls -l `which sha512sum`
-rwxr-xr-x 1 root root 103456 Oct 8 2009 /usr/bin/sha512sum
On the face of the checksum I thought it was just a corrupted binary.
But the size is different, too!
[root@sheeva ~]# ls -l /vservers/f12/usr/bin/sha512sum
-rwxr-xr-x 1 root root 100636 Oct 8 2009 /vservers/f12/usr/bin/sha512sum
This makes me wonder where my binary came from. So I re-downloaded the
rootfs from here:
http://ftp.linux.org.uk/pub/linux/arm/fedora/rootfs/rootfs-f12.tar.bz2
(because it's linked from here:
http://fedoraproject.org/wiki/Architectures/ARM/BeagleBoardxMSDCard )
extracted it, and:
[root@sheeva /usr/src/arm/rootfs-f12]# ls -la usr/bin/sha512sum
-rwxr-xr-x 1 root root 100636 Oct 8 2009 usr/bin/sha512sum
[root@sheeva /usr/src/arm/rootfs-f12]# md5sum usr/bin/sha512sum
7667ac4b53249e53533860518e916719 usr/bin/sha512sum
That means that the sha512sum binary that ships in the f12 rootfs is
broken. Where did your rootfs-f12 image come from? Did you build the
coreutils yourself?
Gordan