Some of this is overflow from last week.
The summary for BSDNow episode 252: “FreeBSD 11.2 has been released, setting up an MTA behind Tor, running pfsense on DigitalOcean, one year of C, using OpenBGPD to announce VM networks, the power to serve, and a BSDCan trip report.”
DragonFly-current, that is. Some newer multi-processor systems use X2APIC to boot, and DragonFly can now use it.
I’m going wide-topic this week.
Lots of announcements, lots of reading. Note the first item listed is happening today.
- Book Fair, 23 June 2018. Michael W. Lucas is at the Scriptorium Book Fest today, in Michigan. Go if you are near and get a signed BSD book.
- Escape from System D, Episode V. Interesting cause it mentions BSD and interesting for spot-on characterization of Twitter/Hacker News feedback. (via)
- 25 years of FreeBSD. (via)
- NetBSD Summer of Code reports: libfuzzer, kernel address sanitizer, and kernel undefined behavior sanitizer.
- Valuable News 2018/06/17.
- FreeBSD Desktop, parts 1, 2, 3, 4, 5, 6, 7, 8, 9, 10. I linked to a few of the early ones before, but I want to present a complete (so far) list.
- FreeBSD 11.2-RC3 Available.
- OPNsense 18.1.10 released.
- httpd(8) Gains Simple Request Rewrites.
- SMT Disabled by Default in -current.
- More Mitigations for (potential) CPU Vulnerabilities.
- LDAP client added to -current. This, or a similar LDAP client, should be present in all BSDs.
- KDE on FreeBSD – June 2018. 5 is almost working in DragonFly, too, by the way. (via)
- itch.io Summer Sale + General itch.io Feature.
- “what’s good in openbsd superior than freebsd?“
- HardenedBSD 11-STABLE v1100055.4 Released. (via)
- “Today I stumbled upon a BSD Wikipedia page. Why should I choose BSD over a Linux based distro?“
These would be ‘In Other BSD’ links, but this isn’t Other BSD – It’s DragonFly:
Mixed in with the other documentation on the DragonFly website is a “how to build a release” explanation. I use it every time there’s a new DragonFly version. If you were wanting to build a DragonFly ISO/IMG with changes or different preinstalled dports, I’ve added some notes about what’s relevant for non-release building.
We used to have “GUI” releases of DragonFly which were based on the nrelease process installing pkgsrc packages and adding some configuration files. It doesn’t happen now mostly because nobody has had the time to reconfigure for dports; if you were looking for a project this weekend, may I suggest…?
BSDNow 251 has one of the more fun titles ever, and goes into HAMMER encryption, BSDCan details, and a number of other things that make for good BSD news.
I’m pulling a quote off of IRC to show some of the testing on HAMMER2, specifically as the background for this commit:
14:22 <@dillon_> ^^^ hammer2 bug, could reproduce it around once a day doing a continuous rm -rf on hardlinked snapshots. reproduced about once every 500 million directory entries or so
I am somewhat tickled by the notion that you might have a problem after deleting half a billion directory entries.
SemiBUG meets tonight at 7 PM, and James Turner is presenting about BHCS. I rarely say this, but: I wish I was closer to Michigan. Go, if you are near.
Update: the files referenced during the talk.
I’ve tagged and built DragonFly 5.2.2. This is mostly so that our current release image includes the fixes for the LazyFP bug, CVE-2018-3665. My email to users@ has upgrade details.
I’m going heavy on history this week.
- “an imaginary mail order computer games shop in 1985“.
- NeoVim, a refactoring of Vim.
- “The Obscuritory, a blog about lesser-known, odder games and software.” (via)
- Pulling the rug out from under an internet protocol.
- Building the Commodore that should have existed. (via)
- Via the previous link, the C256 Foenix Project. A Commodore 128 sequel.
- The Arcade Flyer Archive, advertising material around arcade games. (via)
- AtlTVHead, a project. (Video)
- OpenStreetMap Should Be a Priority for the Open Source Community. (via)
- Webrings. Was there ever a BSD one? I don’t know…
- Student events at SC18 this fall – sign up now to participate. That’s “SC” as in “SuperComputing” – they will have a Cray on display, for instance. (via)
- “There’s real reasons for Linux to replace ifconfig, netstat, et al“. The argument isn’t valid, I think – you’ll get the same problem with new tools; it’s really reinvention, not improvement. (via)
- Yore Computer, old UK computer magazine pages. (via)
Lots of different items, probably because of BSDCan.
I am typing BSDXXX phrases a lot, it seems. BSDNow 250 goes over the just-finished BSDCan. There’s a ton of events, so get reading/listening.
DragonFly has had NX (Non-eXecutable) support for some time. It’s now on by default for read operations in DragonFly master – not the current release. You can step it up to level 2, for write operations, with a loader tunable, but it may cause issues with dports.
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.
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)
It’s been a busy week and I didn’t have overflow from last week to help, so these are very fresh links.
BSDCan is running this weekend. There is, depending on what time you are reading this, a livestream.
If you have a serial card add-in, DragonFly can now output the console to it – a way to run completely headless. It’s not quite like a normal on-motherboard serial port boot, so look at the commit notes for implementation details.