How Google got to rolling Linux releases for Desktops
cloud.google.com
How Google got to rolling Linux releases for Desktops
1–10 of 167 posts
Re: How Google got to rolling Linux releases for Desktops
#2The more important question is where is this magical Google-blessed rolling release Debian available to download? We've all heard rumors of this internal Google distro and what I'm reading is their intent to give back. You can use Microsoft's CBL-Mariner today.
Where is Google's?
Re: How Google got to rolling Linux releases for Desktops
#3The more important question is where is this magical Google-blessed rolling release Debian available to download? We've all heard rumors of this internal Google distro and what I'm reading is their intent to give back. You can use Microsoft's CBL-Mariner today. Where is Google's?
Why yes, they could share Goobuntu with the world. But they don't have to, and so they won't.
Re: How Google got to rolling Linux releases for Desktops
#4The more important question is where is this magical Google-blessed rolling release Debian available to download? We've all heard rumors of this internal Google distro and what I'm reading is their intent to give back. You can use Microsoft's CBL-Mariner today. Where is Google's?
It seems like they are just using Debian testing with periodic version freezes. It's very likely not all that different from just running testing.
Re: How Google got to rolling Linux releases for Desktops
#5personally I'm a pretty big fan of opensuse tumbleweed for a rolling distribution because they ship fully tested snapshots each day rather than individual packages. If I understand the article correctly Google's Sieve is similar to the Opensuse Build Service in that regard.
It seems like they went for Debian because of the proximity to Ubuntu but I wonder if they ever considered Suse, the ecosystem is pretty good.
Re: How Google got to rolling Linux releases for Desktops
#6Can I ask the following as this what Google did is literally what I try to achieve on a Raspberry Pi:
I have configured unattended-upgrades (the package from apt) on a Raspberry Pi on Raspbian 10, but no security updates seem to ever be released. Is there a gotcha I’m missing resp. is there a better way of configuring an always-on computer and keep it secure?
Re: How Google got to rolling Linux releases for Desktops
#7Can I ask the following as this what Google did is literally what I try to achieve on a Raspberry Pi: I have configured unattended-upgrades (the package from apt) on a Raspberry Pi on Raspbian 10, but no security updates seem to ever be released. Is there a gotcha I’m missing resp. is there a better way of configuring an always-on computer and keep it secure?
The article mentions:
> We build packages in package groups, to take into account separate packages that need to be upgraded together. Once the whole group has been built, we run a virtualized test suite to make sure none of our core components and developer workflows are broken. Each group is tested separately with a full system installation, boot and local test suite run on that version of the operating system.
> We then proceed to carefully guide this release to the fleet utilizing SRE principles like incremental canarying and monitoring the fleet health.
Re: How Google got to rolling Linux releases for Desktops
#8Just use Arch
Re: How Google got to rolling Linux releases for Desktops
#9Just use Arch
Or NixOS unstable hehe
Re: How Google got to rolling Linux releases for Desktops
#10personally I'm a pretty big fan of opensuse tumbleweed for a rolling distribution because they ship fully tested snapshots each day rather than individual packages. If I understand the article correctly Google's Sieve is similar to the Opensuse Build Service in that regard. It seems like they went for Debian because of the proximity to Ubuntu but I wonder if they ever considered Suse, the ecosystem is pretty good.
Thanks for your comment. I have been thinking about Tumbleweed or Manjaro to try out a rolling release. Not sure yet which to choose, as they seem quite different in a lot of ways.