Make upgrade, then make rescue

If you haven’t done it before, you can use ‘make rescue’ to build a tiny base system on DragonFly, for use when /usr goes missing, for when your disk is encrypted, and other rather catastrophic problems.  It should be in sync with the rest of the system, which is why ‘make rescue’ can be part of a buildworld process.  I’m mentioning this because currently, ‘make upgrade’ should be done first.

CPU bug hardening added to DragonFly

Matthew Dillon’s added some patches to DragonFly related to securing floating point state, following similar work in OpenBSD.  There isn’t a reported catchy-name issue to match it, like Spectre/Meltdown – yet.

(If anyone has a good link to the similar OpenBSD commits, please share; I did not find them on a cursory search.)

Update: the fix is now in 5.2 and an update is recommended.

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)