dracut --reproducible by default

dracut --reproducible by default

[Giuseppe Scrivano]

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/

Re: dracut --reproducible by default

[Giuseppe Scrivano]

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/

Re: dracut --reproducible by default

[Harald Hoyer]

On 25.08.2015 15:51, Giuseppe Scrivano wrote:
> 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/

No significant reason, except the penalty of the extra step, which fixes all
the timestamps.

Re: dracut --reproducible by default

[Giuseppe Scrivano]

Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:

> On 25.08.2015 15:51, Giuseppe Scrivano wrote:
>> 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/
>
> 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

Re: dracut --reproducible by default

[Harald Hoyer]

On 02.09.2015 14:11, Giuseppe Scrivano wrote:
> Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:
> 
>> On 25.08.2015 15:51, Giuseppe Scrivano wrote:
>>> 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/
>>
>> 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
> 

I think, I'll make it the default.

Re: dracut --reproducible by default

[Giuseppe Scrivano]

Hi Harald,

Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:

>> 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
>> 
>
> I think, I'll make it the default.

is there any version of Dracut that has it as the default so I can start
testing it with rpm-ostree?

Regards,
Giuseppe