Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
posted by Fnord666 on Tuesday January 23 2018, @07:10PM   Printer-friendly
from the goocafeteria-serves-googurt dept.

For years, Google used an in-house Linux distribution called Goobuntu (based on Ubuntu LTS releases), as its development platform. No more.

After more than five years with Ubuntu, Google is replacing Goobuntu with gLinux, a Linux distribution based on Debian Testing.

[...] As MuyLinux reports, gLinux is being built from the source code of the packages and Google introduces its own changes to it. The changes will also be contributed to the upstream.

[...] How does Google plan to move to Debian Testing? The current Debian Testing release is upcoming Debian 10 Buster. Google has developed an internal tool to migrate the existing systems from Ubuntu 14.04 LTS to Debian 10 Buster. Project leader Margarita claimed in the Debconf talk that tool was tested to be working fine.

Google also plans to send the changes to Debian Upstream and hence contributing to its development.

[...] Back in 2012, Canonical had clarified that Google is not their largest business desktop customer. However, it is safe to say that Google was a big customer for them. As Google prepares to switch to Debian, this will surely result in revenue loss for Canonical.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Tuesday January 23 2018, @11:54PM

    by Anonymous Coward on Tuesday January 23 2018, @11:54PM (#626864)

    How would that help anyone? Systemd is fantastic for containerised, headless or rapid spin-up and spin-down deployments, the kind that Google would be using.

    Not just due to boot speed (which is almost entirely irrelevant), it starts things, isolates things and makes sure they're running - all from a single unified configuration. You don't need to mess around with supervisord and so on to build something decently robust and resilient.

    Plus, many current container management stacks do depend on parts of systemd in the host environment.