From: Denys Dmytriyenko <denis@denix.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image_types: use compress framework to produce checksums for images
Date: Thu, 14 Apr 2016 14:33:51 -0400 [thread overview]
Message-ID: <20160414183351.GD16135@denix.org> (raw)
In-Reply-To: <20160410184953.GH16135@denix.org>
On Sun, Apr 10, 2016 at 02:49:53PM -0400, Denys Dmytriyenko wrote:
> On Thu, Mar 24, 2016 at 02:14:36PM -0700, Andre McCurdy wrote:
> > On Thu, Mar 24, 2016 at 1:45 PM, Alexander Kanevskiy <kad@kad.name> wrote:
> > > On Thu, Mar 24, 2016 at 10:32 PM, Andre McCurdy <armccurdy@gmail.com> wrote:
> > >>
> > >> On Thu, Mar 24, 2016 at 1:16 PM, Alexander D. Kanevskiy <kad@kad.name>
> > >> wrote:
> > >> > Existing compress framework for producing various compressed versions
> > >> > of images is powerfull enough to be extended for other uses, e.g. to
> > >> > convert types of images.
> > >> >
> > >> > It is possible to use it also to produce image checksums at the time
> > >> > of image generation. This commit adds support for all supported
> > >> > at the moment coreutils hashing algorithms: md5, sha1, sha224,
> > >> > sha256, sha384 and sha512
> > >> >
> > >> > Usage:
> > >> > IMAGE_FSTYPES_append = " hddimg.sha256sum"
> > >>
> > >> I guess a common requirement is for hashes of the compressed images,
> > >> not only the uncompressed image.
> > >
> > > you can easily chain them.
> > > " hddimg.sha256sum hddimg.xz hddimg.xz.sha256sum"
> >
> > OK. Great. Didn't realise that was going to work!
>
> Well, unless something has been changed/fixed recently (and I believe it was
> Richard's do_rootfs fixes), it didn't use to work as easy as you'd expect and
> it would break in do_rootfs, when trying to nest image types directly, hence
> the implementations like these:
>
> http://cgit.openembedded.org/openembedded-core/tree/meta/classes/image_types_uboot.bbclass
> http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-distro/classes/image_types_md5.bbclass;hb=HEAD
>
> BTW, at least for md5sum (not sure about sha*), isn't the de-facto standard
> extension .md5 and not .md5sum? Can we change it?
Ping? Any comments on the last part about the standard .md5 file extension?
--
Denys
next prev parent reply other threads:[~2016-04-14 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 20:16 [PATCH] image_types: use compress framework to produce checksums for images Alexander D. Kanevskiy
2016-03-24 20:28 ` Burton, Ross
2016-03-24 20:32 ` Andre McCurdy
2016-03-24 20:45 ` Alexander Kanevskiy
2016-03-24 21:14 ` Andre McCurdy
2016-04-10 18:49 ` Denys Dmytriyenko
2016-04-14 18:33 ` Denys Dmytriyenko [this message]
2016-04-14 19:53 ` Burton, Ross
2016-04-14 19:59 ` Otavio Salvador
2016-04-14 20:12 ` Denys Dmytriyenko
2016-04-14 20:31 ` Otavio Salvador
2016-04-14 21:26 ` Denys Dmytriyenko
2016-04-14 20:16 ` Denys Dmytriyenko
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=20160414183351.GD16135@denix.org \
--to=denis@denix.org \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.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