Please wait...
Yeah, well, Ubuntu has tried a bunch of different things to make themselves non-standard. Most of them (Upstart and Unity are two examples) have failed.
It seems they're now making the switch from X11 to Wayland in the current version. Let's see how that works out. It should be interesting.
there. For all practical purposes, ISV's who actually produce
software instead of rolling craft beer distributions of Linux in
their spare time, only care about Fedora (CentOS, Red Hat) and Debian
(Ubuntu).
CoreOS might be much more common soon
Ok well ... from the CoreOS web site: "Within Container Linux, you will almost
exclusively use systemd to manage the lifecycle of your Docker containers."
So not only does CoreOS use systemd, but they have leveraged it as the framework for initializing and running containers.
It seems there's no additional problem here if CoreOS does become more common.
So not only does CoreOS use systemd, but they have leveraged it as the framework for initializing and running containers.
It seems there's no additional problem here if CoreOS does become more common.
...because if you're going to decouple components like that, you ought to do it with CORBA, right?
Amirite? ;)
Hello, is this thing on...?
This looks a bit too nifty:
https://www.howtogeek.com/56538/how-to-remotely-control-your-pc-even-when-it-crashes/
Some Intel chips have an extra MINIX OS built into the chip that allows you to do some entertaining things with the machine.
Cool. This type of functionality is of course available on most high end
servers which have a BMC on board (Cisco CIMC, HP iLO, Dell DRAC, etc). It
is interesting to see Intel building it into the chipset.
Although that article reads like an advertisement for the payware version of RealVNC.
Although that article reads like an advertisement for the payware version of RealVNC.
It does, although it was the only article I found (in my not-very-deep search) that provided any practical use for this information at all.
Tonight I stopped procrastinating, and got a home server running again. I
used my old netbook. :) With a basic Linux install and some extra disks
attached to it, it seems to be doing the job well.
My requirements are few:
* Offsite backups of my primary servers, which sit in a remote data center
* DLNA server, to serve audio and video to devices around the home
* Periodically update my dynamic DNS (my router doesn't support afraid.org)
While installing the OS, I was reminded how much I liked netbooks so much more than tablets. And when I booted up the 2009-era Linux that was previously installed on it, I was reminded how much better the GUI's were before *everyone* collectively decided to make everything ugly and unusable.
The netbook was a good choice because it has a low-power processor (an Atom), and I already had it so the cost was $0. Previously I was using a Raspberry Pi, but it kept crashing for some reason. I'm still not sure why.
My requirements are few:
* Offsite backups of my primary servers, which sit in a remote data center
* DLNA server, to serve audio and video to devices around the home
* Periodically update my dynamic DNS (my router doesn't support afraid.org)
While installing the OS, I was reminded how much I liked netbooks so much more than tablets. And when I booted up the 2009-era Linux that was previously installed on it, I was reminded how much better the GUI's were before *everyone* collectively decided to make everything ugly and unusable.
The netbook was a good choice because it has a low-power processor (an Atom), and I already had it so the cost was $0. Previously I was using a Raspberry Pi, but it kept crashing for some reason. I'm still not sure why.
I missed this when it was announced a couple of weeks ago.
[ http://tinyurl.com/amazon-is-hitler ]
Recent moves by Amazon suggest that they are preparing to ditch the Xen hypervisor and move to KVM.
The new hypervisor was mentioned in the release notes for a new "C5" instance type which is powered by Intel "Skylake" processors. (Read notes here: [ http://tinyurl.com/die-bezos-die ]). They go on to mention that "going forward, web'll use this hypervisor to power other instance types."
Although Amazon is bad, Amazon using KVM is good. The KVM hypervisor is really, really good. It's less cumbersome than Xen, makes more sense in the way it allocates resources using existing Linux facilities, and still manages to be a Type 1 hypervisor even though it shares memory management and other functions with the host OS's userland.
It will be interesting to see if Xen withers and dies at this point.
[ http://tinyurl.com/amazon-is-hitler ]
Recent moves by Amazon suggest that they are preparing to ditch the Xen hypervisor and move to KVM.
The new hypervisor was mentioned in the release notes for a new "C5" instance type which is powered by Intel "Skylake" processors. (Read notes here: [ http://tinyurl.com/die-bezos-die ]). They go on to mention that "going forward, web'll use this hypervisor to power other instance types."
Although Amazon is bad, Amazon using KVM is good. The KVM hypervisor is really, really good. It's less cumbersome than Xen, makes more sense in the way it allocates resources using existing Linux facilities, and still manages to be a Type 1 hypervisor even though it shares memory management and other functions with the host OS's userland.
It will be interesting to see if Xen withers and dies at this point.
Amazon will have to continue using Xen for many years to come, because they are committed to supporting paravirt-based images on most of their existing instance types.
Perhaps. pv-ops was designed to be hypervisor agnostic (even VMware supports
it!) so they could port things over if they really wanted to. More likely
they will just deprecate the old instance types though.
I don't think we're talking about the same thing. Amazon is committed to supporting what they call PVM-based AMIs, which as I understand it are Xen-based paravirt kernels that predate pv-ops and don't have the ability to boot as HVM, bare-metal, dom0 etc (all of which are supported by recent pv-ops) or else there would be no point to any distinction between PVM and HVM AMIs
Yes, that is a bit different. I still think they could shim it out and make it run under KVM if they really wanted to, but it's probably easier for them to just cap those instance types and let them age out. In the hosting business we generally don't upgrade customers who have already paid unless they are ready to pay us again.