From: Giuseppe Scrivano <gscrivan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: dracut --reproducible by default
Date: Tue, 25 Aug 2015 15:51:18 +0200 [thread overview]
Message-ID: <87vbc3fpd5.fsf@foo.bar.baz> (raw)
In-Reply-To: <87a8tnvhs0.fsf-QWOdrvsUieXjVZl2hYKjvQ@public.gmane.org> (Giuseppe Scrivano's message of "Wed, 19 Aug 2015 09:50:23 +0200")
ping?
Giuseppe Scrivano <gscrivan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:
> Hi,
>
> We are currently considering to feed Dracut with --reproducible in the
> rpm-ostree[1] project when creating a new OStree[2] tree image. In this
> way there won't be need to store an additional file when the new initrd
> file matches an older one. Everything works very well (except the
> additional step of providing a patched GNU cpio for now).
>
> Reproducible images seem to make a lot of sense, also for users that
> don't know about the --reproducible option. Is there any reason why
> this is not done by default?
>
> Thanks,
> Giuseppe
>
> 1) https://github.com/projectatomic/rpm-ostree
> 2) https://github.com/GNOME/ostree/
next prev parent reply other threads:[~2015-08-25 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 7:50 dracut --reproducible by default Giuseppe Scrivano
[not found] ` <87a8tnvhs0.fsf-QWOdrvsUieXjVZl2hYKjvQ@public.gmane.org>
2015-08-25 13:51 ` Giuseppe Scrivano [this message]
[not found] ` <87vbc3fpd5.fsf-QWOdrvsUieXjVZl2hYKjvQ@public.gmane.org>
2015-09-02 10:16 ` Harald Hoyer
[not found] ` <55E6CC75.5080206-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-02 12:11 ` Giuseppe Scrivano
[not found] ` <87vbbtyqac.fsf-QWOdrvsUieXjVZl2hYKjvQ@public.gmane.org>
2015-09-02 12:12 ` Harald Hoyer
[not found] ` <55E6E79E.1060800-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-11-03 9:33 ` Giuseppe Scrivano
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=87vbc3fpd5.fsf@foo.bar.baz \
--to=gscrivan-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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