The latest debacle over the "forced" upgrade to Windows 10 and Apple's increasingly locked-in ecosystem has got me thinking. Do I really need to use a proprietary operating system to get work done? And while I'm at it, do I need to use commercial cloud services to store my data?
I've always used Linux since the first time I tried installing Slackware in the mid-90s. In 1998 we were the first national TV show to install Linux live (Red Hat). And I've often advocated Ubuntu to people with older computers. I usually have at least one computer running Linux around, in the past couple of years Dell XPS laptops have been great choices. And a couple of months ago I bought a 17" Oryx laptop from System76, an Ubuntu system integrator, for use in studio.
But as time went by, even Ubuntu began to seem too commercial to me, and I've migrated to community supported Debian testing and the Arch-based Antergos distros for everything. (i use Antergos on my Oryx on the shows.)
At VidiGuard, we care a lot about physical security. In fact, it’s our job. But equally important to physical security is the security of our customers’ data. We also need a robust, reliable platform that can run with minimal interaction. To make both of those happen, we employ OpenBSD in our on-premise equipment and our data infrastructure. Why OpenBSD?
For some time now, I’ve been running OpenWRT on an RT-N66U device. I initially set that because I had previously been using my Debian-based file/VM server as a firewall, and this had some downsides: every time I wanted to reboot that, Internet for the whole house was down; shorewall took a fair bit of care and feeding; etc.
I’ve been having indications that all is not well with OpenWRT or the N66U in the last few days, and some long-term annoyances prompted me to search out a different solution. I figured I could buy an embedded x86 device, slap Debian on it, and be set.
Right on schedule the LLVM 3.9 code was branched today in preparation for its formal release next month.
LLVM 3.9 is another six-month feature update to the LLVM compiler stack. We'll have more on its features and performance in the weeks ahead, in addition to the LLVM Clang benchmarks we already do daily with it at LinuxBenchmarking.com.
BSD fans looking to do some testing this weekend can try out the beta of the upcoming FreeBSD 11.0.
FreeBSD 11.0 is bringing updated KMS drivers, Linux binary compatibility layer improvements, UEFI improvements, Bhyve virtualization improvements, and a plethora of other work. Those not yet familiar with FreeBSD 11 can see the tentative release notes and what's new guide.
The Lumina Desktop Environment has made available their v1.0 beta release of the Qt-written desktop.
PC-BSD developers and others continue working on Lumina as an alternative, lightweight desktop environment. While originating in the BSD world, Lumina continues to be designed to work on any Unix-like OS and is licensed under a 3-clause BSD license. Should you not be familiar with Lumina from our past articles, visit Lumina-Desktop.org to learn more about the project.
The fifth alpha release of the huge FreeBSD 11.0 operating system update is now available for testing.
FreeBSD 11.0 is bringing updated KMS drivers, Linux binary compatibility layer improvements, UEFI improvements, Bhyve virtualization improvements, and a wide range of other enhancements outlined via the in-progress release notes.
The HAMMER2 file-system is going on four years in development by the DragonFlyBSD crew, namely by its founder Matthew Dillon. It's still maturing and taking longer than anticipated, but this is yet another open-source file-system.
For those unfamiliar with FreeBSD, it is considered one of the few operating systems left to be true UNIX. It is a direct descendant of the BELL/AT&T labs UNIX. Much of the software available for Linux is also available for FreeBSD as well, including Gnome and KDE desktop environments and much more user and server software. Despite the amount of software available, it is often thought of as an obscure system with a rather small software library. This is simply
The fourth alpha release of the upcoming FreeBSD 11.0 is now available for testing.
FreeBSD 11.0 Alpha 4 ships the very latest fixes for this major BSD update. FreeBSD 11.0 is scheduled to be officially released in early September with the code freeze happening last week, the beta builds beginning in July, and release candidates in August. The FreeBSD 11.0 schedule can be found via FreeBSD.org.
There's more work going on in the CUDA/OpenMP space for the LLVM Clang compiler.
Landing this week in Clang SVN/Git is generic offload toolchains for the concept of an offloading tool chain plus related work. The initial patch explains, "This patch is the first of a series of three that attempts to make the current support of CUDA more generic and easier to extend to other programming models, namely OpenMP."
ART has been the default routing table backend in OpenBSD for some months now. That means that OpenBSD 6.0 will no longer consult the 4.3 BSD reduced radix tree to perform route lookups.
The principal motivation for adopting a new tree implementation can be explained in three letters: SMP.
I'll describe in a different context why and how ART is a good fit in our revamp of OpenBSD network stack. For the moment, let's have a look at the single-thread performances of this algorithm in OpenBSD -current.
This new parallelism library is described as "[hosting] the development of libraries which are aimed at enabling parallelism in code and which are also closely tied to compiler technology. Examples of libraries suitable for hosting within the parallel-libs subproject are runtime libraries and parallel math libraries. The initial candidates for inclusion in this subproject are StreamExecutor and libomptarget which would live in the streamexecutor and libomptarget subdirectories of parallel-libs, respectively."