From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: md5sum arguments
Date: Wed, 2 Jul 2014 07:42:44 +0200 [thread overview]
Message-ID: <20140702054244.GS14257@pengutronix.de> (raw)
In-Reply-To: <20140701211447.9e543b8e172d37c32d630091@gmail.com>
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-07-02 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 17:14 Antony Pavlov
2014-07-02 5:42 ` Sascha Hauer [this message]
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=20140702054244.GS14257@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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