Skip to contentSkip to conversation

dracut --reproducible by default

DISCUSSION Giuseppe Scrivano 2 participants 6 messages Aug 19, 2015 – Nov 3, 2015 5 messages not in the archive

lore
Share & tools
lore
#0 lore raw

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/

#2 lore raw
In reply to a message not in the archive

ping?

Quoted 17 lines · 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/

#4 lore raw
In reply to a message not in the archive
Quoted 21 lines · Giuseppe Scrivano

ping?

Quoted 17 lines · 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/

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

#6 lore raw
In reply to a message not in the archive
Quoted 17 lines · Harald Hoyer
Quoted 16 lines · Giuseppe Scrivano

ping?

Quoted 12 lines · 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?

Quoted 8 lines
Quoted 5 lines
Quoted 5 lines

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

#8 lore raw
In reply to a message not in the archive
Quoted 25 lines · Giuseppe Scrivano
Quoted 23 lines · Harald Hoyer
Quoted 21 lines · Giuseppe Scrivano

ping?

Quoted 17 lines · 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/

Quoted 9 lines
Quoted 2 lines

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.

#10 lore raw
In reply to a message not in the archive

Hi Harald,

Quoted 8 lines · Harald Hoyer
Quoted 6 lines

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