Questions Answered, Questions Posed - What Happened to Tux500?

One hundred and seven emails were actionable questions or comments concerning the Tux500 project. Those questions or comments were broken down into catagory and because they address important matters in the community, I have decided that some of them need answered sooner than I can physically get to them individually. Herein, I will address them by catagory.

How are we doing?

Not nearly as well as we projected prior to kicking off the project. By now, we had projected our community donation level to be approximately thirty five thousand dollars. This effort was not hastily arranged and executed, although there are reports to the contrary. Reading the names of those making such comments, it may be old age creeping up, but I do not specifically remember any of those people sitting in on the meetings or conference/video calls held prior to the first announcement. It seems uninformed opinion carries the same validity as documented fact here in the Linux Community. That's tough to overcome.

Upon the completion of legal requirements, the first announcement was made. Once it went live, press releases were dispatched to one hundred and eighty two publications. This of course included all the Linux News websites as well as the dead tree editions of major Linux magazines. Two of those magazines responded just inside the second week of the project. One magazine made it a point to interview at least one project leader and double-checked the links, publications and individuals with pertinent information about the project. It was with more than wishful thinking we concluded that these publications were going to report on Tux500. As time passed and we noted that no story had been mentioned in either publication, we inquired as to if there were to be a story. One publication responded by informing us the Editor was simply deciding "which direction" they would go with the story.

A few moments ago, renowned Linux kernel maintainer Greg Kroah-Hartman had the pleasure of announcing the general availability of the Linux kernel 4.8.13 and Linux kernel 4.4.37 LTS maintenance updates.
While many rolling GNU/Linux distributions have just received the Linux 4.8.12 kernel, it looks like Linux kernel 4.8.13 is now available with more improvements and bug fixes, but it's not a major milestone. According to the appended shortlog and the diff since last week's Linux 4.8.12 kernel release, a total of 46 files were changed, with 214 insertions and 95 deletions.

openSUSE's Douglas DeMaio reports on the latest Open Source and GNU/Linux technologies that landed in the repositories of the openSUSE Tumbleweed rolling operating system.

What Is A VPN Connection? Why To Use VPN?

We all have heard about VPN sometime. Most of us normal users of internet use it. To bypass the region based restrictions of services like Netflix or Youtube ( Yes, youtube has geo- restrictions too). In fact, VPN is actually mostly used for this purpose only. ​

The Libreboot C201 from Minifree is really really really ridiculously open source

Open source laptops – ones not running any commercial software whatsoever – have been the holy grail for free software fans for years. Now, with the introduction of libreboot, a truly open source boot firmware, the dream is close to fruition.
The $730 laptop is a bog standard piece of hardware but it contains only open source software. The OS, Debian, is completely open source and to avoid closed software the company has added an Atheros Wi-Fi dongle with open source drivers rather than use the built-in Wi-Fi chip.

Latest News

Games for GNU/Linux

Feral Interactive was proud to inform the media about the upcoming Christmas release of the immense DLC pack for the Total War: WARHAMMER turn-based strategy and real-time tactics video game to SteamOS and Linux.
Last month, on November 22, the UK-based video game publisher Feral Interactive brought us the Linux/SteamOS port of the astonishing and addictive Total War: WARHAMMER game developed by Creative Assembly and published by Sega. And now, they promise to port the Total War: WARHAMMER Realm of The Wood Elves DLC too.

Containers News

Victor Vieux from the open source Docker app container engine released new development versions of the upcoming Docker 1.13.0 major milestone and Docker 1.12.4 maintenance update for the current stable series.
The third Release Candidate (RC) version of Docker 1.13.0 arrived a couple of days ago with numerous minor tweaks and fixes to polish the software before it's tagged as ready for production and hits the streets, which should happen in the coming weeks. Docker 1.13.0 RC3 comes two after the release of the second RC build.

The conventional wisdom of Linux containers is that each service should run in its own container. Containers should be stateless and have short lifecycles. You should build a container once, and replace it when you need to update its contents rather than updating it interactively. Most importantly, your containers should be disposable and pets are decidedly not disposable. Thus the conventional wisdom is if your containers are pets, you’re doing it wrong. I’m here to gently disagree with that, and say that you should feel free to put your pets in containers if it works for you.

AMDGPU News

This morning's AMDGPU-PRO 16.50 preview included some 16.40 vs. 16.50 hybrid driver benchmarks, but for those wondering how 16.50 compares to Mesa 13.1-dev for RadeonSI OpenGL and RADV Vulkan, here are some preliminary tests for the two current Vulkan AAA Linux games.

AMD ran into a snag getting out the updated proprietary hybrid Linux driver stack this morning, but it's now available for download from AMD.
This page has the 16.50 Linux x86/x86_64 driver available for download.

While AMD developers have been working to improve their "DAL" (now known as "DC") display code for the better part of the past year and this code is needed for new hardware support as well as supporting HDMI/DP audio on existing AMDGPU-enabled hardware plus other features, it's still not going to be accepted to the mainline kernel in its current form.