This week on the show, we'll be chatting with Alex Reece and Matt Ahrens about what's new in the world of OpenZFS. After that, we're starting a new tutorial series on submitting your first patch. All the latest BSD news and answers to your emails, coming up on BSD Now - the place to B.. SD.
This episode was brought to you by
Headlines
Revisiting FreeBSD after 20 years
With comments like "has Linux lost its way?" floating around, a Debian developer was prompted to revisit FreeBSD after nearly two decadesThis blog post goes through his experiences trying out a modern BSD variant, and includes the good, the bad and the ugly - not just praise this timeHe loves ZFS and the beadm tool, and finds the FreeBSD implementation to be much more stable than ZoLOn the topic of jails, he summarizes: "Linux has tried so hard to get this right, and fallen on its face so many times, a person just wants to take pity sometimes. We’ve had linux-vserver, openvz, lxc, and still none of them match what FreeBSD jails have done for a long time."The post also goes through the "just plain different" aspects of a complete OS vs. a distribution of various things pieced togetherFinally, he includes some things he wasn't so happy about: subpar laptop support, virtualization being a bit behind, a myriad of complaints about pkgng and a few other thingsThere was some decent discussion on Hacker News about this article too, with counterpoints from both sides***
s2k15 hackathon report: network stack SMP
The first trip report from the recent OpenBSD hackathon in Australia has finally been submittedOne of the themes of this hackathon was SMP (symmetric multiprocessing) improvement, and Martin Pieuchot did some hacking on the network stackIf you're not familiar with him, he gave a presentation at EuroBSDCon last year, titled Taming OpenBSD Network Stack DragonsTeaming up with David Gwynne, they worked on getting some bits of the networking code out of the big lockHopefully more trip reports will be sent in during the coming weeksMost of the big code changes should probably appear after the 5.7-release testing period***
From BIND to NSD and Unbound
If you've been running a DNS server on any of the BSDs, you've probably noticed a semi-recent trend: BIND being replaced with UnboundBIND was ripped out in FreeBSD 10.0 and will be gone in OpenBSD 5.7, but both systems include Unbound now as an alternativeOpenBSD goes a step further, also including NSD in the base system, whereas you'll need to install that from ports on FreeBSDInstead of one daemon doing everything like BIND tried to do, this new setup splits the authoritative nameserver and the caching resolver into two separate daemons This post takes you through the transitional phase of going from a single BIND setup to a combination of NSD and UnboundAll in all, everyone wins here, as there will be a lot less security advisories in both BSDs because of it...***
m0n0wall calls it quits
The original, classic BSD firewall distribution m0n0wall has finally decided to close up shopFor those unfamiliar, m0n0wall was a FreeBSD-based firewall project that put a lot of focus on embedded devices: running from a CF card, CD, USB drive or even a floppy diskIt started over twelve years ago, which is pretty amazing when you consider that's around half of FreeBSD itself's lifespanThe project was probably a lot of people's first encounter with BSD in any formIf you were a m0n0wall user, fear not, you've got plenty of choices for a potential replacement: doing it yourself with something like FreeBSD or OpenBSD, or going the premade route with something like pfSense, OPNsense or the BSD Router ProjectThe founder's announcement includes these closing words: "m0n0wall has served as the seed for several other well known open source projects, like pfSense, FreeNAS and AskoziaPBX. The newest offspring, OPNsense, aims to continue the open source spirit of m0n0wall while updating the technology to be ready for the future. In my view, it is the perfect way to bring the m0n0wall idea into 2015, and I encourage all current m0n0wall users to check out OPNsense and contribute if they can."While m0n0wall didn't get a lot of on-air mention, surely a lot of our listeners will remember it fondly***
Interview - Alex Reece & Matt Ahrens -
[email protected] &
[email protected] / @openzfs
Tutorial
Making your first patch (OpenBSD)
News Roundup
Overlaying remote LANs with OpenBSD's VXLAN
Have you ever wanted to "merge" multiple remote LANs? OpenBSD's vxlan(4) is exactly what you needThis article talks about using it to connect two virtualized infrastructures on different ESXi serversIt gives a bit of networking background first, in case you're not quite up to speed on all this stuffThis tool opens up a lot of very cool possibilities, even possibly doing a "remote" LAN partyBe sure to check the AsiaBSDCon talk about VXLANs if you haven't already***
2020, year of the PCBSD desktop
Here we have a blog post about BSD on the desktop, straight from a KDE developerHe predicts that PCBSD is going to take off before the year 2020, possibly even overtaking Linux's desktop market share (small as it may be)With PCBSD making a preconfigured FreeBSD desktop a reality, and the new KMS work, the author is impressed with how far BSD has come as a viable desktop optionZFS and easy-to-use boot environments top the list of things he says differentiate the BSD desktop experience from the Linux oneThere was also some discussion on Slashdot that might be worth reading***
OpenSSH host key rotation, redux
We mentioned the new OpenSSH host key rotation and other goodies in a previous episode, but things have changed a little bit since thendjm says "almost immediately after smugly declaring 'mission accomplished', the bug reports started rolling in."There were some initial complaints from developers about the new options, and a serious bug shortly thereafterAfter going back to the drawing board, he refactored some of the new code (and API) and added some more regression testsMost importantly, the bigger big fix was described as: "a malicious server (say, "host-a") could advertise the public key of another server (say, "host-b"). Then, when the client subsequently connects back to host-a, instead of answering the connection as usual itself, host-a could proxy the connection to host-b. This would cause the user to connect to host-b when they think they are connecting to host-a, which is a violation of the authentication the host key is supposed to provide."None of this code has been in a formal OpenSSH release just yet, but hopefully it will soon***
PCBSD tries out LibreSSL
PCBSD users may soon be seeing a lot less security problems because of two recent changesAfter switching over to OpenNTPD last week, PCBSD decides to give the portable LibreSSL a try tooNote that this is only for the packages built from ports, not the base system unfortunatelyThey're not the first ones to do this - OPNsense has been experimenting with replacing OpenSSL in their ports tree for a little while now, and of course all of OpenBSD's ports are built against itA good number of patches are still not committed in vanilla FreeBSD ports, so they had to borrow some from BugzillaLook forward to Kris wearing a "keep calm and abandon OpenSSL" shirt in the near future***
Feedback/Questions
Benjamin writes inMike writes inBrad writes in***
Mailing List Gold
Debian DejavuPackage gone missing***
View all episodes
