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.
1. Embrace
2. Extend
thegodmovie.com - watch it
Extend. Check.
Will give you three guesses for what comes next.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
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?)...
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!