Sign up to save your podcasts
Or
Share R-B-OS (osc25)
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
R-B-OS (osc25)
During the last year, I have spent several months on a project, that was sponsored by a grant from the NLnet NGI0 initiative.
It is about an operating system, that only has packages that can be reproduced anywhere anytime bit-by-bit. I call it R-B-OS - the Reproducible-Builds-Operating-System.
Last year when we had https://events.opensuse.org/conferences/oSC24/program/proposals/4378 , most of the work was still ahead. Now it is completed and I can tell how it went.
I'll tell about the journey. And I'll tell about the result.
RBOS has some unique properties:
- The collection of sources are defined by a single hash, and so are the binaries produced from it. It is a 1->1 mapping.
- When I change a toolchain package (e.g. gcc), I can let it rebuild and see exactly what changed in other places.
Licensed to the public under https://creativecommons.org/licenses/by-sa/4.0/
about this event: https://c3voc.de
View all episodes
During the last year, I have spent several months on a project, that was sponsored by a grant from the NLnet NGI0 initiative.
It is about an operating system, that only has packages that can be reproduced anywhere anytime bit-by-bit. I call it R-B-OS - the Reproducible-Builds-Operating-System.
Last year when we had https://events.opensuse.org/conferences/oSC24/program/proposals/4378 , most of the work was still ahead. Now it is completed and I can tell how it went.
I'll tell about the journey. And I'll tell about the result.
RBOS has some unique properties:
- The collection of sources are defined by a single hash, and so are the binaries produced from it. It is a 1->1 mapping.
- When I change a toolchain package (e.g. gcc), I can let it rebuild and see exactly what changed in other places.
Licensed to the public under https://creativecommons.org/licenses/by-sa/4.0/
about this event: https://c3voc.de