SoylentNews is people
SoylentNews
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.
(Score: 5, Informative) by frojack on Tuesday January 23 2018, @07:30PM (22 children)
That Google pays canonical for anything is simply Google's way of buying influence, and supporting FOSS. Apparently that influence wasn't forthcoming, and Google already does a great deal of FOSS support in other ways. If Google could use its influence (and money) to quell some of the self inflicted drama that Debian always seems to have simmering it would be great.
Google doesn't need any help from Canonical to install, update, maintain, and enhance their internal version of Ubuntu. Probably Google could teach Canonical a whole bag of tricks, especially with regard to reducing extraneous packages and making servers very efficient,
Because Google doesn't market their internal distro, they don't have to return anything they develop.
No, you are mistaken. I've always had this sig.
(Score: 1, Insightful) by Anonymous Coward on Tuesday January 23 2018, @07:55PM (2 children)
My experience suggests that Google knows nothing about such efficiency; Google's solution is to throw more computing, more contractors, and more money at any problem that gets in the way. Code monkeys to the rescue!
(Score: -1, Spam) by Anonymous Coward on Tuesday January 23 2018, @08:20PM
He was a relatively unknown magician who finally stumbled upon the opportunity to perform in front of a large audience. He did not intend to waste this chance, so he decided to pull out all the stops...
The obese magician pointed at a little boy in the audience to signify that he would be the volunteer for this trick. The boy's parents encouraged him to get up on stage, and so he did. There were no props or tools to be seen, so the audience began wondering what sort of trick would be performed. Then, the red curtains closed, thereby concealing the boy and the magician. 'Just what kind of trick is this?' the audience thought to themselves.
Soon after the curtains closed, the audience heard the man telling the boy to take off his clothes. This was followed by the boy sobbing and telling the magician that he didn't want to. Next, the man screamed at the boy to follow his orders. It wasn't long before the audience could hear slapping sounds, as though flesh was colliding with flesh repeatedly. In addition, the sound of a man moaning could be heard. Several minutes later, the curtains began to open...
What the audience witnessed next was beyond their ability to comprehend. Was it really a trick, or was it true magic!? Marvelous! The audience saw the boy naked and lying in a pool of his own blood, utterly motionless. The magician was sweating heavily and looked like he was in a state of euphoria. The magician then said "Tadaaaaaaaaaaaaaaaaaaaaaaa!" 'How did he do it!?' the audience thought to themselves. Then, every single person who bore witness to this magnificent event - including the boy's parents - gave the performer a standing ovation. Someone shouted, "How did you do it!? I need to know how this amazing trick was performed!" The magician smiled and said simply, "A magician doesn't reveal his tricks." Everyone laughed.
(Score: 0) by Anonymous Coward on Wednesday January 24 2018, @03:07AM
From what I've seen google do it's not even that, they just add more PRNG iterations to their various AI (bruteforce by another name) algorithms which nobody there actually understands anymore.
(Score: 1, Informative) by Anonymous Coward on Tuesday January 23 2018, @07:59PM
https://en.m.wikipedia.org/wiki/Goobuntu [wikipedia.org]
(Score: 1) by bobthecimmerian on Tuesday January 23 2018, @08:29PM
I'd be curious whether Google actually did ever pay Canonical much. Google has their own colossal set of engineers and admins, why would they pay an outside company for support?
And to be fair to Canonical, Google has to support their own internal services and tools. They don't have to support thousands of packages in thousands of combinations by all kinds of users. Don't get me wrong, whether you love Google or hate them the company is an engineering powerhouse. But I'm sure Google isn't maintaining twelve different mp3 tag editors and nineteen file managers and Ada compilers (for example) on its internal Linux distributions. They have harder 'Big Data' problems to solve but easier distribution management problems.
(Score: 5, Insightful) by Nuke on Tuesday January 23 2018, @08:52PM (16 children)
It is a shame they did not pick Devuan instead of Debian. Same flavour but without systemd.
(Score: 2) by takyon on Tuesday January 23 2018, @09:14PM (3 children)
Why does it matter? It's Google. How does it affect you? Do you just want them to hand Devuan devs some $$$?
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
(Score: 2, Touché) by Anonymous Coward on Tuesday January 23 2018, @10:45PM (2 children)
yes
(Score: 0) by Anonymous Coward on Wednesday January 24 2018, @05:05AM (1 child)
Anything that google invest money into (mozilla etc) inevitably turns to shit. You must not like devuan very much.
(Score: 2) by Freeman on Wednesday January 24 2018, @03:54PM
Google hasn't had much incentive to make Mozilla better ever since they started making their own web browser.
Joshua 1:9 "Be strong and of a good courage; be not afraid, neither be thou dismayed: for the Lord thy God is with thee"
(Score: 2) by DannyB on Tuesday January 23 2018, @09:25PM (5 children)
In principle: I don't like systemd!
I think the problems systemd solves could have been better solved in a more modular way instead of one giant MCP from Tron.
Being pragmatic, if systemd is going to be rammed down my throat, then I sure do want it to work well. Having lots of development resources, like Google engineers, helps make that happen.
In the end, we'll end up with more standards across more distributions -- which I think can only make things better. Why can't services be handled in a standard way? Have a standard system message bus. Have only one type of "script" or "config" file you have to write to get your server daemon to run on any distribution. Wouldn't that be nice?
Now if we could have only one packaging format. And one package dependency graph more like Docker containers. I suppose these things might come one day, but it just seems to take so darn long compared to how proprietary companies can simply dictate how things will work. Not that I want to use closed source instead. Police work is also easy in a police state -- and I don't want to live there.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 1, Redundant) by frojack on Tuesday January 23 2018, @09:40PM (1 child)
Man who rants about police state demands single packaging tool. Film at 11.
Bitches about Giant MCP, having never looked at the code, then dreams about all the things systemd already does, and says wistfully "Wouldn't that be nice".
No, you are mistaken. I've always had this sig.
(Score: 1, Informative) by Anonymous Coward on Tuesday January 23 2018, @09:49PM
Reading comprehension, do you need a refresher course?
(Score: 2) by maxwell demon on Tuesday January 23 2018, @09:45PM (1 child)
What would be the point of different distributions if they were all essentially the same with only cosmetic differences?
The Tao of math: The numbers you can count are not the real numbers.
(Score: 2) by DannyB on Tuesday January 23 2018, @10:47PM
It can be more than cosmetic differences.
First, the "cosmetics". Different desktop environments do have real, material usability differences. Users have strong preferences for different ways of working. Distributions can be focused on different primary users based on default applications.
Second, looking beneath the desktop environment (if any!). Some distributions might be focused on being extremely lightweight. (Alpine) Which makes them a good starting point for, example, Docker containers. Or focused on being a server without any desktop. Or distributions focused on being the best desktop.
Standardization is a GOOD thing to the extent that it makes it possible for package developers to make ONE build and have it work on all distributions.
Distributions could focus on security. Or running everything in a container.
It seems to me that having more standardization doesn't kill having lots of distributions. But maybe it kills having a pointlessly large number of incompatible distributions. And hey, it's open source, nobody is stopping anybody from building whatever they think is best.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 0) by Anonymous Coward on Wednesday January 24 2018, @10:03PM
i would like it if most distros could agree on some kind of upstream source standard so any distro's package manager can automatically build any upstream project. distros could focus on security, user facing features, the packaging systems themselves, or whatever they cared about, instead of just manual maintenance of packages.
(Score: 4, Interesting) by frojack on Tuesday January 23 2018, @09:28PM (4 children)
Companies of Google scale are exactly the benefactors of systemd.
That said, I haven't had any significant problems with systemd. The docos are readable, the source code is easily perused, and writing you own systemd services is drop dead simple.
I now groan when I have to maintain older systems.
And yeah, I was originally against systemd in the beginning when it was barely functional.
No, you are mistaken. I've always had this sig.
(Score: 1, Insightful) by Anonymous Coward on Tuesday January 23 2018, @10:00PM (1 child)
Reserve a little paranoia for systemd now making it really easy to hide backdoors that now get pushed to all Linux systems.
(Score: 2) by DannyB on Tuesday January 23 2018, @10:53PM
True. But there are lots of places to hide backdoors into large numbers of Linux systems.
And the whole "trusting trust" type of compromise / paranoia.
Compromise is possible in the boot loader.
And in the firmware. (And ability to lock you out of even booting!)
And thanks to Intel Management Engine, in the microprocessor itself. Compromise baked right into the hardware!
And Spectre and Meltdown.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 2) by DannyB on Tuesday January 23 2018, @10:50PM
Yep. I was originally a complainer about systemd. I haven't had any trouble with it. It seems to work. As you say about services.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 0) by Anonymous Coward on Tuesday January 23 2018, @11:39PM
THERE ARE NO DOCS.
It is by design that the design is not visible to the public.
(Score: 0) by Anonymous Coward on Tuesday January 23 2018, @11:54PM
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.