Did you know there’s a randread utility on DragonFly that will report on disk performance? Well, you do now. The very terse comment in the source code will tell you how to compile it and the arguments.
It really does work, that lead-in, and it’s on BSDNow episode 188.
Yes, I know we just released 4.8. This is a rollup release, capturing everything that was committed to the 4.6 branch after 4.6.1 and before 4.8 came out. If you are going to upgrade, it’s worth it to go to 4.8, but this way there’s a clean final version in the 4.6 branch.
(Hat tip to Sascha Wildner for reminding me to do this.)
It’s happening tomorrow night at the NYCBUG meeting: a yes.c code reading. (more details) Go, if you are close.
I am late in mentioning this, because it was added just before the DragonFly 4.8 branch: there’s a new ‘efisetup(8)‘ script added to DragonFly. Use to to perform a complete a UEFI-bootable installation to a given disk.
I’m very UNIXy this week.
Your useful tip of the week: Setting the
root login’s ‘full name’ to identify the machine that sent email. This makes so much sense. (via)
Odd batch of links this week.
Your BSD-related fiction book of the week (year? decade?) :’git commit murder‘ is out, set at a (fictional) BSD convention.
Now that we’re past the DragonFly 4.8 release, Francois Tigeot has added an update to the i915 driver, bringing it to match what’s in the Linux 4.7.10 kernel. He also committed Peeter Must’s port of the vga_switcheroo module.
This week’s BSDNow has no interview, but covers most every BSD to some extent, and talks about something I find super-interesting: a BSD phone.
KnoxBUG is meeting tonight – there’s no speaker scheduled, so it will be open discussion.
DragonFly 4.8 is officially released! Download from your nearest mirror, where it should appear in the next 24 hours. If you’re upgrading your existing install, you can use the generic instructions in the release notes or in my users@ email; whichever you click first. Don’t forget to ‘pkg upgrade’!
Old-school UNIX and games this week.
More thinking topics than version changes this week, which is interesting.
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.
Matthew Dillon picked up more NVMe M.2 hardware, tested it, and updated his report to match. Definitely a good read if you will be buying this hardware any time soon, and it’s not necessarily DragonFly-specific.
BSDNow 186 gets back into the convention grind after last week’s news about new roles: coverage of the recent AsiaBSDCon, and an interview of Philipp Buehler.
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.
Michael W. Lucas will be presenting at SemiBUG tomorrow, talking about the OpenBSD web stack.