Linux Archive

Linux Mint 17.3 is the final Mint 17 release and should put to rest any worries about Mint's plan to stick with Ubuntu LTS releases for its base. Mint has done what it set up to do, namely improve the Cinnamon desktop to the point that it not only matches, but in many places far exceeds the user experience found in other options like GNOME, and especially, Unity.

Indeed, it's hard to look at Mint 17.3 without comparing it to its upstream base. While Mint has been continually working hard on the desktop and cranking out release after release, Ubuntu has stagnated. If Ubuntu wants to leapfrog past some of its pain points, its developers would do well to look downstream. Mint's package management tools are simpler, more comprehensive, and easier to use than anything Ubuntu offers. Mint also manages to do all this without anything even remotely close to the resources Ubuntu enjoys.

One of the biggest freedoms associated with free software is the ability to replace a program with an updated or modified version. Even so, of the many millions of people using Linux-powered phones, few are able to run a mainline kernel on those phones, even if they have the technical skills to do the replacement. The sad fact is that no mainstream phone available runs mainline kernels. A session at the 2015 Kernel Summit, led by Rob Herring, explored this problem and what might be done to address it.

Late last week, hell had apparently frozen over with the news that Microsoft had developed a Linux distribution of its own. The work was done as part of the company's Azure cloud platform, which uses Linux-based network switches as part of its software-defined networking infrastructure.

While the software is real, Microsoft isn't characterizing it as a Linux distribution, telling us that it's an internal project. That's an important distinction, and we suspect that we're not going to see a Microsoft Linux any time soon.

For those who haven't kept up with bcache, the bcache codebase has been evolving/metastasizing into a full blown, general purpose posix filesystem - a modern COW filesystem with checksumming, compression, multiple devices, caching, and eventually snapshots and all kinds of other nifty features.

Feature-wise, 4.0 doesn't have all that much special. Much have been made of the new kernel patching infrastructure, but realistically, that not only wasn't the reason for the version number change, we've had much bigger changes in other versions. So this is very much a "solid code progress" release.

Sure - if you want a fast, well-built, well-equipped 4K laptop preloaded with Ubuntu, with most of the potential edge-case configuration issues already taken care of, with an active set of developers working to ensure that the necessary repos are kept current, and with an actual, for-real OEM warranty and support. The M3800 Developer Edition is what an OEM-loaded Linux laptop should be, and it's got the added bonus of being supported by Barton George and a small, dedicated group of Linux enthusiasts at Dell. Those folks are backed by Dell's significant resources and are in constant contact with Canonical.

The value proposition is pretty clear there, but the question is whether or not that value proposition is worth the extra money versus buying a less-expensive base laptop and loading the Linux distro of your choice. There's going to be a lot of overlap between the M3800 Developer Edition's target market and the segment of potential customers who have no problem with just rolling their own Linux installation on a Thinkpad or even on a MacBook. For those folks, how much is it worth to have Dell do the heavy lifting?

With Linux 4.0, you may never need to reboot your operating system again.

One reason to love Linux on your servers or in your data-center is that you so seldom needed to reboot it. True, critical patches require a reboot, but you could go months without rebooting. Now, with the latest changes to the Linux kernel you may be able to go years between reboots.

It's not a secret that I've been working on sandboxed desktop applications recently. In fact, I recently gave a talk at devconf.cz about it. However, up until now I've mainly been focusing on the bundling and deployment aspects of the problem. I've been running applications in their own environment, but having pretty open access to the system.

Now that the basics are working it's time to start looking at how to create a real sandbox. This is going to require a lot of changes to the Linux stack. For instance, we have to use Wayland instead of X11, because X11 is impossible to secure. We also need to use kdbus to allow desktop integration that is properly filtered at the kernel level.

This release adds support for btrfs scrubbing and fast device replacement with RAID 5&6, support for the Intel Memory Protection Extensions that help to stop buffer overflows, support for the AMD HSA architecture, support for the debugging ARM Coresight subsystem, support for the Altera Nios II CPU architecture, networking infrastructure for routing and switching offloading, Device Tree Overlays that help to support expansion busses found on consumer development boards like the BeagleBone or Raspberry Pi, support for hole punching and preallocation in NFSv4.2, and the Android binder has been moved from the staging area to stable; it also adds new drivers; and many other small improvements.

100Gb network adapters are coming, said Jesper Brouer in his talk at the LCA 2015 kernel miniconference. Driving such adapters at their full wire speed is going to be a significant challenge for the Linux kernel; meeting that challenge is the subject of his current and future work. The good news is that Linux networking has gotten quite a bit faster as a result - even if there are still problems to be solved.

I'm going to describe steps needed to have the following system:

• Dual-boot with Arch Linux / Mac OS X
• Boot manager UEFI Gummiboot (simple, can handle several kernels easily)
• Full disk encryption (Mac OS X and Arch Linux)
• LVM support
• Suspend to disk using a swapfile
• Settings for a great battery life (~09h30)

I keep the Mac OS X partition, to be able to update the firmware later.

If Linux is to achieve world domination, it must have One Frickin' User Interface (1FUI): a single user experience / interface behaviour and a single underlying UI toolkit API / widget set. World domination means putting Linux into corporations, schools, PDAs, and cell phones. This will only happen with 1FUI, and if this upsets the nerds, too bad. History clearly shows that if a platform/system offers a choice of user interfaces, the potential users will choose a different system.