md5sum arguments
Sascha Hauer
s.hauer at pengutronix.de
Tue Jul 1 22:42:44 PDT 2014
On Tue, Jul 01, 2014 at 09:14:47PM +0400, Antony Pavlov wrote:
> Hi All!
>
> Current 'md5sum' command gets FILE|AREA argument, e.g.
>
>
> barebox:/ help md5sum
>
> md5sum - calculate MD5 checksum
>
> Usage: md5sum FILE|AREA...
>
> Calculate a MD5 digest over a FILE or a memory area.
>
> The *nix 'md5sum' gets [FILE]... argument.
> This behavour can be misleading. E.g. today I have tryed this command sequence on
> my qemu-malta machine:
>
> barebox:/ memcpy -s /dev/zero -d 1M 0 0 0x100000
> barebox:/ md5sum 1M
>
> md5sum just hangs!
This is beacuse size is initialized with ~0 and thus the command will
create a md5sum over the whole memory space.
This works:
md5sum 1M+0x100000
> But this command sequence works fine:
>
> barebox:/ memcpy -s /dev/zero -d zeros 0 0 0x100000
> barebox:/ md5sum zeros
> b6d81b360a5672d80c27430f39153e2c zeros 0x00000000 ... 0xffffffffffffffff
>
>
> Do we really need this?
Personally I don't need this, but since we have this feature and it's
not really expensive, why should we remove it?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox
mailing list