
Sign up to save your podcasts
Or


This week on the show, we will be talking to Benedict Reushling about his role with the FreeBSD foundation and the journey that took him
“FreeBSD Mastery: Advanced ZFS” has officially been released
Support of OpenBSD pledge(2) in programming Languages
pkgsrcCon 2016 -Call for Presentations
Christos Zoulas talks about blacklistd
Penguicon 2016 Lucas Track Schedule
This week on BSD Now, I’m out of town for the week, but we have a special unboxing video to share with you, that you won’t want to miss. That, plus the latest BSD news, is coming your way right now!
Amazon lists FreeBSD as 'Other Linux'
sbin/hammer: Make hammer commands print root volume path
sbin/hammer: Print volume list after volume-add|del
Front cover reveal for the upcoming 'FreeBSD Mastery: Advanced ZFS" book
If you don’t already have one, get your FreeBSD Pillow
This week on the show, we will be interviewing GNN of the FreeBSD project to talk about the new TeachBSD initiative. That plus the latest BSD headlines, all coming your way right now!
Teaching BSD with Tracing
I’ve been a source committer since 2000. I got my start by taking over maintainership of the Adaptec ‘aac’ RAID driver. From 2002-2006 I was the Release Engineer and was responsible for the 5.x and 6.x releases. Though the early 5.x releases were not great, they were necessary stepping stones to the success of FreeBSD 6.x and beyond. I’m exceptionally proud of my role in helping FreeBSD move forward during that time.
I authored and maintained the ‘mfi’ and ‘mps’ storage drivers, the ‘udf’ filesystem driver, and several smaller sound and USB drivers. I’ve maintained, or at least touched, most of the storage device drivers in the system to some extent, and I implemented medium-grained locking on the CAM storage stack. Recently I’ve been working on overall system scalability and performance.
Credit where credit's due...
M:Tier's OpenBSD packages and binpatches updated for 5.9
NYC BUG Meeting (2016-04-06) - Debugging with LLVM, John Wolfe
Need to create extremely high traffic loads? kq_sendrecv is worth checking out
If you're in the Maryland region, CharmBug has a meetup next week
How to get a desktop on DragonFly
Linux vs BSD Development Models
This week on the show, we interview author Michael W Lucas to discuss his new book in the FreeBSD
“I just enabled ART in -current, it will be the default routing table backend in the next snapshots.
@mwlauthor
OpenBSD is an ecosystem of quality. This is the result of a culture of code auditing, reviewing, and a rigorous development process where each commit hitting the tree must be approved by other developers. It has a slower evolution pace and a more carefully planned development model which leads to better code quality overall. Its well deserved reputation of being an ultra secure operating system is the byproduct of a no compromise attitude valuing simplicity, correctness, and most importantly proactivity. OpenBSD also deletes code, a lot of code. Everyone should know that removing code and keeping the codebase modern is probably as important as adding new one. Quoting Saint-Exupery: "It seems that perfection is attained not when there is nothing more to add, but when there is nothing more to remove".
This week on the show, Allan and I have gotten a bit more sleep since AsiaBSDCon, which is excellent since there is a LOT of news to cover. That plus our interview with Ports SecTeam member Mark Felder. So keep it
AsiaBSDCon OpenBSD Papers
Antoine Jacoutot (ajacoutot@) - OpenBSD rc.d(8) (slides | paper)
First and foremost, the way code is developed needs change to stop the current negative trend in Bitcoin. The FreeBSD project has a rigid internal hierarchy of people with write access to their codebase, which the various Bitcoin implementations also have, but BSD does this in a way that is very open to fresh eyes on their code, allowing parallel problem solving without the petty infighting we see in Bitcoin. Anyone can propose a commit publicly to the code, make it publicly available, and democratically decide which change ends up in the codebase. FreeBSD has a tiny number of core developers compared to the size of their codebase, but at any point, they have a huge community advancing their project without hard forks popping up at every small disagreement. Brian Armstrong commented recently on this flaw with Bitcoin development, particularly with the Core Devs:
“Being high IQ is not enough for a team to succeed. You need to make reasonable tradeoffs, collaborate, be welcoming, communicate, and be easy to work with. Any team that doesn’t have this will be unable to attract top talent and will struggle long term. In my opinion, perhaps the biggest risk in Bitcoin right now is, ironically, one of the things which has helped it the most in the past: the Bitcoin Core developers.”
The other thing Bitcoin devs could learn from is the BSD community’s adoption of the Unix Design philosophy. Primarily “Worse is Better,” The rule of Diversity, and Do One Thing and Do It Well. “Worse is Better” emphasizes using extant functional solutions rather than making more complex ones, even if they would be more robust. The Rule of Diversity stresses flexibility of the program being developed, allowing for modification and different implementations without breaking. Do one Thing and Do it well is a mantra of the BSD and Unix Communities that stresses modularity and progress over “perfect” solutions. Each of these elements help to make BSD a wildly successful open source project with a healthy development community and lots of inter-cooperation between the different BSD systems. While this is the opposite of what we see with Bitcoin at present, the situation is salvageable provided changes like this are made, especially by Core Developers.
New TN Bug started
DragonFlyBSD Network/TCP Performance's gets a bump
FreeBSD Foundation introduces a new website and logo
Our producer made these based on the new logo:
IPv6 errata for 5.7/5.8, pledge errata for 5.9
Sponsoring “PAM Mastery”
A visualization of FreeBSD commits on GitHub for 2015
The VAX platform is no more
This week on BSDNow, Allan and I are back from AsiaBSDCon and we have an interview with Brad Davis about the new “Packaging Base” call-for-testing. We’ll be sharing our thoughts and stories on how the week
This week, Allan and I are away at AsiaBSDCon! (If you aren’t there, you are missing out). We will be back with a live episode next week. However, we’ve been asked for Allan to tell us about ScaleEngine’s
NetBSD on an RPi Zero
DragonFly tips for printing with CUPS
Fighting fraudulent networks using secure connections (SSL) blacklisting with OPNsense. Blocks known-bad certificates as listed at abuse.ch
Fix for running NetBSD/amd64 7.0 on kvm based virtual machines
Michael W. Lucas’s new book, FreeBSD Mastery: Specialty Filesystems is now escaping
The Penguicon Lucas Tech Track
FreeBSD based nginx/ffmpeg camera recording and live streaming
CFT: New Jenkins Builder for FreeNAS / PC-BSD
Status Update: PC-BSD’s SysAdm Server
Status Update: PC-BSD’s SysAdm Client UI
This week on the show, we have an interview with Jamie
“We are sympathetic to Canonical's frustration in this desire to easily support more features for their users. However, as set out below, we have concluded that their distribution of zfs.ko violates the GPL. We have written this statement to answer, from the point of view of many key Linux copyright holders, the community questions that we've seen on this matter. Specifically, we provide our detailed analysis of the incompatibility between CDDLv1 and GPLv2 — and its potential impact on the trajectory of free software development — below.
However, our conclusion is simple: Conservancy and the Linux copyright holders in the GPL Compliance Project for Linux Developers believe that distribution of ZFS binaries is a GPL violation and infringes Linux's copyright. We are also concerned that it may infringe Oracle's copyrights in ZFS. As such, we again ask Oracle to respect community norms against license proliferation and simply relicense its copyrights in ZFS under a GPLv2-compatible license.”
FreeBSD 10.3-BETA3 Now Available
LibreSSL isnt affected by the OpenSSL DROWN attack
NetBSD machines at the Open Source Conference 2016 in Toyko
OpenBSD removes Linux Emulation
Time is an illusion - George Neville-Neil
OpenSSH 7.2 Released
This week on BSDNow, Allan is back from the Storage Summit in Silicon Valley! We are going to get his thoughts on how the conference went, plus bring you the latest ZFS info discussed. That plus the usual BSD news is
It starts with his process of creating an AMI from scratch, which ended up not being that bad:
The blog post also has a link to a script which automates this process, so don’t be daunted if you didn’t quite follow all of that.
Thanks to the recently landed DomU support, the final pieces of the puzzle fell into place, allowing OpenBSD to function as a proper guest (with networking!)
Next it details the process of injecting a public SSH key into the instances for instant remote access.
An ec2-init.sh script was created (also on github) which does the following:
With that done, OpenBSD is pretty much AWS ready! He then gives a brief walkthrough of setting up nginx for new users, but if you’ve already done this before then the instance is ready for you to hacking on.
There were many rough edges in the Linux world and some of them exist even today. Choosing the right distribution (distro) for the task at hand is always the first and most difficult decision to make. While this is a strength of the Linux community it is also its weakness. This is exacerbated with the toxic infighting within the community in the last few years.
A herd of voices believes it is their right to bring down a distro community because it is not like their distro of choice. Forking upstream projects has somehow become taboo. Hurling abuse in mailing lists is acceptable. Helping new users is limited to lambasting their distro of choice. Creating conspiracy theories over software decisions is the way to go. Copyleft zealots roam social media declaring non-copyleft free software heretic abominations. It all boils down to an ecosystem soured by the presence of maniacs who have the loudest voices and they seem to be everywhere you turn.
Where is the engineering among all this noise? Btrfs - baking for a long time - is still nowhere near ZFS in stability or feature parity. systemd is an insatiable entity that feeds on every idea in sight and just devours indiscriminately. Wayland was promised years ago and its time has yet to arrive. Containers are represented by Docker that neither securely contains applications nor makes them easy to manage in production. Firewalling is dithering between firewalld, nftables, etc. SystemTap cannot match DTrace.
In the same time span what do various BSDs offer? pf, CARP, ZFS, Hammer, OpenSSH, jails, pkgsrc, (software) ports, DTrace, hardware portability; just to name a few. Few would deny that BSDs have delivered great engineering with free software licenses to the entire world. To me they appear to be better flag bearers of free software with engineering to back it.
Finally - and maybe repeating myself here - I have nothing but praise for the community. Be it BSD Now, mailing lists, Reddit, Twitter, LFNW, or SeaGL, people have encouraged me, answered my questions, and filed bugs for me. I have been welcomed and made a part of the community with open arms. These reasons are (good) enough for me to use FreeBSD and contribute to it.
OPNsense 16.1.3 released
Copies of "FreeBSD Mastery: Specialty Filesystems" seen in the wild
pfsense training available in Europe
LiteBSD now has 50 ports in its ports tree
Ports tree locked for OpenBSD 5.9
“FreeBSD Filesystem Fun” at March semibug
Event #46 — Embedded Platforms (BSD, OpenWRT, Plan 9 & Inferno)
From the publisher's feed

286 Listeners

2,011 Listeners

2,018 Listeners

2,144 Listeners

272 Listeners

374 Listeners

169 Listeners

8,063 Listeners

15,564 Listeners

22 Listeners

98 Listeners

29 Listeners

221 Listeners

22 Listeners

608 Listeners