Microsoft and Canonical Make Custom Linux Kernel (neowin.net)
Billly Gates writes: Microsoft and Canonical's relationship is getting closer besides Ubuntu for Windows. Azure will soon be offering more customized Ubuntu containers with a MS optimized kernel. Uname -r will show 4.11.0-1011-azure for Ubuntu cloud based 16.04 LTS. If you want the non MS kernel you can still use it on Azure by typing:
$ sudo apt install linux-virtual linux-cloud-tools-virtual
$ sudo apt purge linux*azure
$ sudo reboot
The article mentions several benefits over the generic Linux kernel for Azure
$ sudo apt install linux-virtual linux-cloud-tools-virtual
$ sudo apt purge linux*azure
$ sudo reboot
The article mentions several benefits over the generic Linux kernel for Azure
Such as native hooks for telemetry?
If you want the non MS kernel you can still use it by not using Microsoft's cloud platform in the first place
There. FTFY.
Now, this is a serious question, but what reason could someone have for running Linux on Azure? Are there not any of a multitude of other better platforms out there for running Linux? I mean, I certainly understand if you are all in for Microsoft with things like Exchange, SQL server, AD, Sharepoint, etc., their cloud platform sort of make sense. But this, Ubuntu (or any other Linux) on Azure is something that simply does not make sense to me.
Hruh? Hu hon de Cannoical Linuces
1. Embrace
2. Extend
thegodmovie.com - watch it
Which part of embrace, extend, and extinguish is this?
I'm assuming we're well past the "embrace" part, considering they've got a bash shell for Windows 10. I guess that means we're onto the extend part. What proprietary bits does this kernel contain that can't be found anywhere else?
Extend. Check.
Will give you three guesses for what comes next.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Teh splleing si mxied pu.
and no back doors. We promise!
MuckUsoft Winux.. it sucks.
s3
Get an axe!
F*** that distro.
Microsoft and Canonical's relationship is getting closer besides Ubuntu for Windows.
Microsoft to buy Canonical. The end of Ubuntu.
Sent as ripples into the electromagnetic field. No single photon has been harmed in the process.
This isn't the first time that Canonical have produced a custom kernel for a cloud provider platform. Earlier in the year they came out with a custom Ubuntu kernel for the same for AWS so it sounds like strategy they're pursuing in general. Other than the reduced size I'd hope these improvements end up in the mainline kernel in the end (perhaps these changes already have and these are just backports?)...
and always remember what happened to Nokia (just the last in a long, long line).
If you go to bed with a crocodile, you don't need to wonder why, next morning, your right leg is missing.
does that count as microkernel?
There aren't really any changes so much as reconfiguration...
A generic kernel needs a complete set of drivers for all the hardware it *might* be installed on, whereas a cloud hypervisor is a fixed target. You can safely remove support for physical devices, and for older processors than those used by the cloud host which results in a smaller better optimized kernel. I've done exactly the same thing, albeit on a smaller scale, as i have 100+ vm images running on the same hypervisor and underlying physical machines.
http://spamdecoy.net - free throwaway anonymous email - avoid spam!
Seriously, one of the first things I did on my first Linux computer was to compile a kernel that was tailored for the hardware.
Why waste Memory on drivers and features that will never be used in a VM?
Ah, so they want Linux solutions to require Windows.
... That the next Windows version will be a Linux distro called WinDux?
For years I've joked about Microsoft coming out with their own version of Linux... and now it has come to pass. Make no mistake- this is the *beginning of the end for pure, unencumbered Linux as we know it.
Amusingly, this is the "cancer" that Steve Ballmer was alluding to, where Microsoft embraces, extends, and extinguishes stuff. It won't be extinguished though, it'll be polluted with Microsoft's "improvements".
First it'll be fairly benign...then later it'll start to have "special features" that are MS-specific (that is, "Microsoft ONLY") and from there it'll be a relentless poisoning of Linux, bit by bit.
You laugh now, but you'll see. I was right all along, and this is just the opening move by Microsoft to fuck up Linux for the foreseeable future.
Never forget that Microsoft always, always, ALWAYS has its eye on the Long Game. If it takes them 10 or 15 years to pollute, ruin, and fragment Linux, so be it. They have the time and the money, everything else is just detail.
Just cruising through this digital world at 33 1/3 rpm...
And we all know the Final Phase...
(Final Solution)
"a MS optimized kernel" -> "an MS-optimized kernel"
Extend - in process. Extinguish - next in line.
The Ubuntu kernel for AWS also includes the ENA (Elastic Network Adapter) driver (source code: https://github.com/amzn/amzn-d...), which allows you to get 20Gbps networking on certain instance types (https://aws.amazon.com/about-aws/whats-new/2016/06/introducing-elastic-network-adapter-ena-the-next-generation-network-interface-for-ec2-instances/).
I believe RHEL 7.4 also added the ENA driver, and the Amazon Linux image has it of course.
Is it configurable by .config in the real linux kernel sources, or is it all unaccepted patches?
MS shipping a specific Linux kernel ?
What can possibly go wrong ?
aaaaaaa
Whatever twisted love child these two manage to barf out, I'll take it over systemd any day of the week. It hasn't managed to successfully halt my laptop once since I installed U17.10 a week ago! So bad it's cute and cuddly. Trouble is, I like cute and cuddly. It's fun.
#Moo
M$ astroturfers are one again using sock puppet accounts to shill for M$ and get the $lashdot populace to believe that, as most like astroturfer TrekkieGod have, M$ has changed. After all, $lashdot is now a shill piece for M$. M$ still uses their "embrace, extend, extinguish" tactics despite what trekkiegod would have any of you believe. The only thing M$ has changed was their methods of executing their tactics.
--
Friends don't help friends install M$ junk.
Friends do assist M$ addicted friends in committing suicide.
Yet another stage of embrace extend extinguish.
You can lead a man with reason but you can't make him think.
Yes.
But this isn't really any news, MS has provided custom canonical distributions for Azure deployment for years, and the image MS already provides as their recommenced/default distribution for azure VMs already contains several telemetry and remote management daemons, to facilitate better integration with Azure. The image is also configured to trust ms' own apt repo source.
The code for the telemetry daemon is even open source on github.
https://github.com/Microsoft/OMS-Agent-for-Linux
There has been a few bugs in these daemons, most significant is the bug which starts shell scripts which doesn't terminate, i.e. the server becomes super slow after a few days due to thousands of running processes. Google on "OMSConsistencyInvoker".
Yes.
But this isn't really any news, MS has provided custom canonical distributions for Azure deployment for years, and the image MS already provides as their recommenced/default distribution for azure VMs already contains several telemetry and remote management daemons, to facilitate better integration with Azure monitoring. The image is also configured to trust ms' own apt repo source.
The code for the telemetry daemon is even open source on github.
https://github.com/Microsoft/O...
There has been a few bugs in these daemons, most significant is the bug which starts shell scripts which doesn't terminate, i.e. the server becomes super slow after a few days due to thousands of running processes. Google on "OMSConsistencyInvoker".
You can actually see the lists of changes in the Ubuntu kernel git repos:
The changes range from configuring things off for hardware that will never exist on that platform, forcing certain options to speed up things like boot times, additional new drivers that aren't (yet) upstream (in one case the driver added was actually rejected by the mainline kernel maintainers and was pulled out of the Ubuntu tree later), backports of tweaks that were made in later kernels that help that platform etc.
One downside is that this makes a bit more likely that people running on cloud platforms could see different problems to "bare metal" setups (and vice versa) thus splintering the test effort a bit and increasing Canonical's maintenance burden. Also porting a VM with optimized kernel means you have to remember to switch kernel package (but if you know what you're doing then injecting packages into an offline VM is easy). I guess the benefits outweigh the costs...