Google and Samsung soar into list of top 10 Linux contributors
arstechnica.com
arstechnica.com
How far is it from production?
Few companies can call themselves an authority on NAND flash memory and Samsung is definitely at the top of that list.
The performance of RFS once the filesystem became somewhat populated was horrible and was the one single bottleneck for every single operation on the phone. It made otherwise top-end hardware (for the time) unbearably slow, bordering on useless.
Think 10 seconds lag to go back from an email to the email-listing. Those were real delays. Real problems. Caused by RFS.
I have personally experienced people thank me for giving them "a completely new phone" (quote end) when I rooted the phones and converted all RFS-partitions to EXT4. All those problems went away and you finally got the phone you thought you bought in the first place.
Given this, touching any filesystem by Samsung is something I will give serious second thoughts.
To give Samsung credit, they ditched RFS entirely for their second line of Galaxy S phones. The Galaxy S2 used standard Linux filesystems and RFS has yet to resurface anywhere near civilized folks.
And why can't you wait? What will that buy you? Do you have a read/write heavy workflow with Android?
"The Moto X’s pseudo-stock Android 4.2.2 uses ext4 for all partitions with the exception of user data storage, which uses F2FS (Flash Friendly File System)"
Can someone in the know say what this replacement is?
Canonical contributed 548 changes in the period studied in today's report and would have cracked the top 30 if the foundation hadn't included "none" and "unknown" in the rankings. The maker of Ubuntu has been criticized for years for not contributing more to the kernel (and recently clashed with Intel over patches submitted to the company's graphics driver), but Zemlin [Linux Foundation Executive Director] isn't upset. "I am not at all mad at them. I think they do good work," he said. "You just kind of choose what's important to your org and where you can add the most value to the project and how it intersects with your business. They choose to focus a lot of their time and energy at higher levels of the software stack."
Canonical's contribution is more to the desktop and OS itself than to the kernel. The majority of desktop installations are either Ubuntu or Ubuntu-based, and Ubuntu is quickly becoming the server of choice as well.
Ubuntu is leading GNU/Linux adoption worldwide, which in itself is a huge contribution to the ecosystem, as it gets more programmers interested in various open source projects.
Unless you are using unity, I don't see why a distribution should be called ubuntu based instead of debian based. A lot of "Ubuntu derivatives" are not based on unity.
Sure Ubuntu has a betteer installer and pretty themes, but the base is undeinably debian.
Because Ubuntu is more than Unity. I mean, by the "Unity or its not Ubuntu-based" standard you propose, Kubuntu (which is exactly Ubuntu -- sharing all the same repos -- with the KDE desktop and apps installed by default) wouldn't be an "Ubuntu-based distribution".
Heck, Ubuntu Server, since it doesn't have a default DE at all, wouldn't be an "Ubuntu-based distribution", either.
Ubuntu maintains a set of repositories for each version of Ubuntu, which (even when the same--by name--software is in Debian's official repositories, will often be different versions or otherwise different contents than Debian repos).
Kubuntu uses entirely software from the Ubuntu repos from the corresponding version number (e.g., Kubuntu 12.04 uses exactly the same set of repos as Ubuntu 12.04.) You can, in effect, switch from Kubuntu to Ubuntu, or vice versa, just using the apt package manager without changing the base repositories, just installing and removing the right packages from the ubuntu repos.
The difference between Kubuntu 12.04 and Ubuntu 12.04 is entirely in which packages, from the Ubuntu "precise" repositories are installed by default. The difference between either and any version of Debian is much greater.
The whole "unity or you have to call it 'Debian-based' instead of 'Ubuntu-based'" idea is nonsense.
Your choice of distro really just boils down to your package-manager preference.
Highly debatable. "Most accessible" installer perhaps, but as far as I am concerned, Debian's netinst has yet to be beat. Style isn't exactly high on my list of priorities during installation, it's not like that is something I do to show off in coffee-shops.
http://archive.ubuntu.com/ubuntu/dists/raring/main/installer...
or
http://archive.ubuntu.com/ubuntu/dists/raring/main/installer...
Source?
A quick Google search will produce this information. Furthermore, I think a survey of new server deployments would be even more in Ubuntu's favour, though gathering such information is no doubt difficult.
In the article it does mention that Ubuntu is the most popular distro for Amazon deployments...
Having been on the inside (EC2) and seen the numbers, I can confidently say that Ubuntu's AMIs are the most popular AMIs deployed on EC2. The stock AMIS take the top spots by an overwhelming majority, and most of the lower spots are filled with derivatives of the original Ubuntu AMIs.
Ubuntu's been working hard in the server/cloud space for a while, between the JeOS effort and subsequent, excellent tools for building customized installations around it. It's not just a brand or that makes them popular; with Ubuntu you get a sane system, style, and toolset for your system images.
SoCs are all mostly Qualcomm or Samsung, radio chipsets are mostly Qualcomm, LCDs are Sony/Samsung/Sharp/LG and a few others, AMOLED are all Samsung as far as I know, GPUs are mostly Qualcomm/PowerVR/Nvidia.
Much of the time, the Android modding community ports newer versions of Android to other devices simply by hoping some OEM releases a newer version of Android for another device that happens to have some identical hardware component so they can either drop that particular driver into the other device or tweak it a bit. Porting the OS is never really the problem. The problems generally lie in outdated proprietary drivers no longer working with the newer version of Android (Camera/Bluetooth/Radio/sometimes GPU are the most likely candidates to break).
Not to worry: the same code can get used over and over without being consumed.
And even with all of the experienced eyes, there have to be changes that have crept in that they didn't realize could be misused, and may still not know.
I appreciate that corporations are the biggest donators, and that is extremely important, but is there any point in which we say, "Get your own project?"
(Regardless, I'm not even sure how number of contributions would make any contributor "unstoppable".)
They don't even have to contribute drivers, they certainly shouldn't be expected to go above and beyond that.