In Other BSDs for 2018/06/23

Lots of announcements, lots of reading.  Note the first item listed is happening today.

In Other BSDs for 2018/06/16

Lots of different items, probably because of BSDCan.

mkinitrd out, initrd in

There was an optional ‘make initrd’ step in the DragonFly build process, where you can create a small binary to use for mounting encrypted root drives.

Aaron LI has removed mkinitrd in favor of ‘make initrd’, which builds a separate binary to use in exactly those situations.  See the commit message for more detail.  It incidentally creates a ‘/rescue’ directory and works as a rescue ramdisk, similar to other BSDs, if you should ever need it.  (See updated MOTD for details)

In Other BSDs for 2018/06/09

BSDCan is running this weekend.  There is, depending on what time you are reading this, a livestream.

BSDNow 249: Router On A Stick

BSDNow 249 is covering a really wide range of topics including an uncommon amount of NetBSD, so I’m going to do the easy thing and repeat the summary: “OpenZFS and DTrace updates in NetBSD, NetBSD network security stack audit, Performance of MySQL on ZFS, OpenSMTP results from p2k18, legacy Windows backup to FreeNAS, ZFS block size importance, and NetBSD as router on a stick.”

In Other BSDs for 2017/06/02

One of these links will be very useful to someone.

In Other BSDs for 2018/05/26

I have the normal list of links, but here’s a feature.  At first glance, this looks like Netgate, the commercial entity behind pfsense, is not using FreeBSD for their new product.  However, Jim Thompson of Netgate steps up and give a full-on explanation, and points out there’s already code out there to do this – it needs contributors.

In Other BSDs for 2018/05/19

Note the eleventy-jillion hackathon reports.

Your thinkpiece for the week: The cultural shift from not selling out to blowing up.  There’s a BSD analogy possible there.

In Other BSDs for 2018/05/12

This came together very nicely.

CVE-2018-8897 fix in, more Spectre fixes for DragonFly

A recent and new CPU bug, CVE-2018-8897, is fixed in DragonFly.  THis applies to both Intel and AMD processors.  I’m happy to see that the CERT page lists equal notification timing for a whole lot of operating systems, rather than the few that heard about Spectre/Meltdown early.

Following that topic, Matthew Dillon has “fleshed out” Spectre mitigations, and his commit message details the current state.  The sysctl ‘machdep.spectre_mitigation’ will tell you what’s set at any given point.

Update: update.