Janz Tec has released an industrial controller built around the Raspberry Pi 3, with WiFi, Bluetooth, CANbus, and CODESYS compatibility.
Saelig launched North American distribution for the latest in Janz Tec’s emPC-A/RPI line of Raspberry Pi based industrial controllers. The Raspberry Pi 3 derived emPC-A/RPI3 follows the almost identical, RPi 2 based emPC-A/RPI2, which was called the emPC-A/RPI when we covered it back in Aug. 2015.
We've been talking about WireGuard for months and it's hoping to go mainline in the Linux kernel this calendar year. Earlier this month at FOSDEM was a status update on the project.
WireGuard lead developer Jason Donenfeld presented on this project that he's been developing over the past year. For those that haven't been following WireGuard up to now, this VPN tunnel is implemented in less than four thousand lines of kernel code, is designed to be very secure, keeps track of minimal state, has a minimal attack surface, provides a solid crypto base, is designed to be very performant, and has other benefits.
Mesa 17.0 ships with many big changes and improvements -- see that article for an overview. In the past week I've also published Intel benchmark results with ANV Vulkan having noticeably better performance, RADV/RadeonSI being much faster, and Nouveau Maxwell improvements.
Soon it will be a decade since we started the RadeonHD driver, where we pushed ATI to a point of no return, got a proper C coded graphics driver and freely accessible documentation out. We all know just what happened to this in the end, and i will make a rather complete write-up spanning multiple blog entries over the following months. But while i was digging out backed up home directories for information, i came across this...
Munich may dump Linux for Windows [Ed: Microsoft tried this FUD with Gartner, then HP, now Accenture, and media always falls for it.]
Taming the Mesos Bleeding Edge with DC/OS [Ed: Microsoft-connected]
Oracle looks to the cloud for easier enterprise data integration [Ed: openwashing in there]
After being in development since the end of 2015, the CRUX 3.3 open-source Linux-based operating system has been released this past weekend, and it's now available for download.
Shipping with a multilib toolchain consisting of the Glibc (GNU C Library) 2.24, GNU Binutils 2.27, and GCC (GNU Compiler Collection) 6.3.0, CRUX 3.3 is powered by a kernel from the long-term supported and most advanced Linux 4.9 kernel branch, namely Linux kernel 4.9.6, and an updated graphics stack based on X.Org 7.7 and X.Org Server 1.19.1. Some important libraries have also been updated in CRUX 3.3.
Those waiting for the milestone that would have been version 4.10 of the Linux kernel have another week to wait, after Linus Torvalds decided not to release the final version this week.
“Hey, it's another week, and I could have released the final 4.10,” Torvalds posted to the Linux Kernel Mailing List, adding that “... I wouldn't have felt bad about just doing the final release today.”
The Linux 4.10 kernel didn't end up being released today, but was pushed back by an extra week. However, in looking forward to next weekend, here are ten of the features that excite us about Linux 4.10.
In the last few months, we tried multiple GNU/Linux distributions for gaming purposes, and we have arrived at the conclusion that there's no perfect operating system out there designed for Linux gaming.
We all know that the world of gaming is split between Nvidia and AMD users. Now, if you're using a Nvidia graphics card, even one from five years ago, chances are it's supported on most Linux-based operating systems because Nvidia provides up-to-date video drivers for most, if not all of its GPUs.
Slackware!? Yes, one of the oldest of Linux distributions won with just over 16 percent of the vote.
If that sounds a little odd, it is. On DistroWatch, a site that covers Linux distributions like paint, the top Linux desktop distros are Mint, Debian, Ubuntu, openSUSE, and Manjaro. Slackware comes in 28th place.
So why the discrepancy? With more than double the votes for any category, it appears there was vote-stuffing by Slackware fans.
Hey, it's another week, and I could have released the final 4.10.
It's not been all that busy, although we did have a number of small
last-minute regression fixes (some just reverting stuff that caused
problems and needed more thought, others fixing things). But nothing
out of the ordinary, and I wouldn't have felt bad about just doing the
final release today.
But I decided that there's also no huge overriding reason to do so
(other than getting back to the usual "rc7 is the last rc" schedule,
which would have been nice), and with travel coming up, I decided that
I didn't really need to open the merge window. I've done merge windows
during travel before, but I just prefer not to. If it was the second
week of the merge window when the big bulk of stuff had been merged,
that would be one thing, but that's not how the schedule turned out.
The patch landed in Intel's drm-intel-next-queued branch this week for enabling atomic support by default on the hardware platforms where it's fully supported.
Following this mailing list discussion, atomic support is now being turned on by default for the Intel Linux DRM driver while it's disabled-by-default support has been in good shape since Linux ~4.9. Though due to the timing of this change-over, this looks like it will be a change for Linux 4.12 as Intel's 4.11 DRM feature work is already over with the 4.11 merge window being imminent.
Just a quick note for anyone who routinely builds the latest X.Org Server from Git, the video driver ABI has been broken again, thus you'll need to rebuild your dependent DDX drivers assuming they have been modified for this new ABI.