An article about a semctl(2) bug on DragonFly, “Make DragonFlyBSD great again!“, has popped up a few times, in comments here, some online forums, and in IRC. I’m linking to it so that I can also say: read all the way to the end and notice the date. The bug was fixed more than 6 months ago. This is not a current security problem, but a (enjoyable) description of how someone in Poland documented it.
Nobody reads anything but headlines, geez.
The last time SSH was updated in DragonFly, a DragonFly-specific customization, “PasswordAuthentication No”, was reverted to the default. This meant password logins through SSH worked on DragonFly – which is normal for perhaps every other UNIX-ish operating system, but DragonFly has traditionally defaulted to requiring a key out-of-the-box.
It has been fixed, and you can change the setting back. This only affected DragonFly-master from August through March. 4.6 users are unaffected.
I tagged the release candidate for DragonFly 4.8 – slightly delayed because of my involuntary time offline – and here’s the resulting automatic changelist. There’s ISO/IMG files uploaded now to the main DragonFly archive, which means they should be available at a mirror near you soon.
Slightly short this week, maybe because people are prepping for AsiaBSDCon? I have plenty of links for tomorrow’s Lazy Reading.
The question of using vkernels(7) in a manner similar to jails pops up time and again, and the answer is, unsurprisingly, “it depends“. It looks like when you want to isolate greedy programs, vkernels are the way to go.
I went to a more simple format for the page. New year, new layout, and so on. How is the load time for people?
BSDNow 174 this week presents a recap of the 2016 year, including chunks of interviews you may have missed.
Matthew Dillion mentioned his changed tutorial on secure web browsing on DragonFly, though I imagine it applies to other systems too. The trick is to use an isolated user account for running a web browser, and he includes the various steps to do so smoothly in the tutorial web page.
Here’s your reminder: SemiBUG meets tomorrow, for any BSD users in the Detroit / Michigan area.
If you are moving to the newest 1.8 version of Go, the language, you need to be on at least the last release of DragonFly 4.4, or 4.6. You’ve probably upgraded by now anyway, or at least I hope you have.
Tennessee area BSD user group KnoxBUG is meeting tomorrow, and Warren Block will be the guest speaker. He’ll be talking about documentation. Going by the linked announcement, there will be both prizes and blame, so something for everyone!
SemiBUG is meeting tomorrow; Joe Gidi will present on managing Android devices with BSD. My assumption is that it will be at Altair Engineering, in Troy, MI, again.
The January meeting will be Michael W. Lucas talking about Ansible. (Dunno if there’s a December meeting planned.)
I’ve been on the road all week, so it seems like I just posted about the last episode. BSDNow 167 is online, and it returns to the interview format. Scott Long of Netflix is interviewed. He’s part of the reason most of the Internet runs through BSD.
Reminder: Isaac (.ike) Levy’s “Infrastructure in a Post-Cloud Era” presentation is tonight, at NYCBUG’s November meeting. Go, see.
COMPAT_43 is gone, but it hasn’t worked in a long time anyway. Note that this is 4.3BSD, pre-everything.
I’ve uploaded ISO and IMG files for DragonFly 4.6.1, so they should be available for download at your local mirror. Note that there’s an uncompressed 4.6.1 ISO for those installing to a virtual server.
Tomohiro Kusumi is thinking about porting it. Follow the whole thread for details.
I may have mentioned this in part before, but Matthew Dillon has a brief script to reload pf when an interface IP changes. I’m linking it here in case it’s useful in the future.
How long does it take to build all 24,000 packages in the DragonFly ports collection? Apparently about 22 hours on a dual Xeon machine (with I think 36 cores) or 48-core Opteron. This is with synth. I used to measure pkgsrc builds in weeks.
This makes sense once you think about it: copy-on-write filesystems (like Hammer2 and ZFS and probably others) actually do nothing when “zeroing” out filespace.