Jordan Hubbard from the FreeNAS project, an open-source initiative to create a powerful, free, secure, and reliable NAS (Network-attached storage) operating system based on BSD technologies, announced the release of FreeNAS 9.10.
FreeNAS 9.10 is the tenth maintenance release in the current stable 9.x series of the project, thus bringing the latest security patches from upstream, support for new devices, as well as several under-the-hood updates. As expected, FreeNAS 9.10 has been rebased on the latest FreeBSD 10.3 RC3 (Release Candidate) release.
Some interesting things — for KDE users and developers — have landed in the official FreeBSD ports tree recently.
CMake has updated to 3.5.0. One side effect of CMake updates is that newer policies tend to produce voluminous warning messages when building older software (like kdelibs4-based things, which is all the KDE software in official ports right now). This can make it hard to track down cmake / configure errors amongst the warnings. There’s not much to do there except (slowly) update other ports to set the new (or old) policies explicitly.
The inaugural release of UbuntuBSD is now available, which the developers have codenamed "Escape From SystemD", and pairs the Ubuntu userspace with the FreeBSD kernel.
Similar to the now-rather-defunct Debian GNU/kFreeBSD that paired the Debian GNU user-space with the FreeBSD kernel rather than the Linux kernel, developers have done the same with Ubuntu and called it UbuntuBSD. This first UbuntuBSD beta release is based off Ubuntu 15.10 Wily Werewolf and the FreeBSD 10.1 kernel.
In preparation for the anticipated FreeBSD 10.3 release later this month, 10.3-RC2 is now available.
Marius Strobl announced the FreeBSD 10.3-RC2 release on Saturday afternoon for all major architectures plus an assortment of ARM boards. FreeBSD 10.3-RC2 fixes a potential data corruption issue with incremental ZFS send, file syncing improvements for hash-based database files, some security issue fixes, and more.
There’s an exp-run going on for KDE4 on FreeBSD right now. That means that the official package-building machines are grinding through the entire ports tree to see what happens. This is part of the regular procedure for big updates — and this is a big one.
While KDE4 as a desktop — with Plasma shell 4 and the old collection of KDE modules like PIM, etc. — is not getting a lot of upstream releases, it does get some updates, and some applications release new versions. This is one reason to continue to update the packages.
For those of you keeping score at home, OpenBSD is like other BSD derivatives, however this derivative is regarded as one of the safest systems due to the OpenBSD team’s attention to security (and could very well be the folks on the receiving end of Linus’ infamous “monkey” quote regarding, um, attention to detail on security issues, but I digress).
There’s never been a whirlwind of politics surrounding an open source project on the scale that we see with Bitcoin. Alternative implementations are considered controversial on principle, and Core devs can’t propose a bug fix without being accused of manipulation on behalf of outside interests. However, BSD, another popular open source project, doesn’t seem to have these problems. Why not?
OpenBSD — a security-focused & research-based Operating System — started auditing their source code tree in 1996. They combed their source code repository looking for bugs that could lead to security vulnerabilities. The results were hundreds of security bugs found & patched. Thankfully, some of those fixes made it to Linux, FreeBSD and NetBSD. Today, OpenBSD proudly boasts about 2 vulnerabilities in more than 10 years. Code auditing is still on-going !