From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giuseppe Scrivano Subject: Re: dracut --reproducible by default Date: Wed, 02 Sep 2015 14:11:23 +0200 Message-ID: <87vbbtyqac.fsf@foo.bar.baz> References: <87a8tnvhs0.fsf@foo.bar.baz> <87vbc3fpd5.fsf@foo.bar.baz> <55E6CC75.5080206@redhat.com> Mime-Version: 1.0 Return-path: In-Reply-To: <55E6CC75.5080206-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> (Harald Hoyer's message of "Wed, 2 Sep 2015 12:16:21 +0200") Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Harald Hoyer Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Harald Hoyer writes: > On 25.08.2015 15:51, Giuseppe Scrivano wrote: >> ping? >> >> Giuseppe Scrivano 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/ > > No significant reason, except the penalty of the extra step, which fixes all > the timestamps. do you think it makes sense to make --reproducible the default, or do you expect Dracut users, rpm-ostree in this case, to explicitly use it? Thanks, Giuseppe