On Saturday we will post the usual batch of positive news and some items will demonstrate the nearness of Novell and XenSource. Thus, the impact of this acquisition on Novell will be interesting.
With Xen in the hands (and agenda) of Citrix, KVM might have more room to breathe in the Linux universe. Bernard Golden (shown in the videos at the bottom) has more to say in a quick roundup from LinuxWorld.
Crosby was also concerned about the proliferation of Linux virtualization technologies; meaning KVM, although there are still further Linux virtualization initiatives. His plaintive cry is that this fragmentation of effort might allow Microsoft to win the virtualization race; the race, that is, to be the replacement technology for VMware. While his concern is understandable, I'm not sure there's any real way to solve it, particularly as a couple of the alternative technologies -- including KVM-- emanate from commercial companies that, presumably, have deep enough pockets to keep the technologies going for the foreseeable future.
Yesterday, one knowledgeable blogger criticised XenSource for taking a wrong approach in implementation. He argued that KVM got it right. And amid VMWare's IPO, accusations are circulating as well. VMWare is said to have used Linux and renamed it.
Update: this acquisition appears to be a reason to worry. There is some early analysis available now ending with "Linux, incidentally, got barely a mention."
Looking at many sites that are full of slop images is becoming an eye sore and hallmark of text too likely generated by LLMs or 'assisted' (tainted) by them
On 12 March and 16 June 2025, staff representation met with the administration in the Local Occupational Health, Safety and Ergonomics Committee (LOHSEC) in Munich
To be very clear, this does not describe "Linux" anything; it's true in just about every facet of news, except the paid-for fake "journalism" about "hey hi" (sites getting paid explicitly to maintain or rekindle hype)
Restricted Boot (so-called 'SecureBoot') does not improve security. It is nothing but trouble. It's meant to trouble non-Windows users. In dual-boot setups, SecureBoot is a recipe for disaster because Microsoft keeps erasing or tampering with the boot sector, to paraphrase an associate