If you are using virtio drivers, there’s no longer a need for ‘device virtio_pci’ in your kernel config. It’s autoloaded as a dependency. If you run a custom kernel, remember to take it out. You’ll want to do that now if you’re on 5.1, or later at the next version upgrade if you are on 5.0.
The first link about TorBSD is important: many of the major security issues in computing trace back to having only one vendor or product or whatever, used by everyone.
- An Open Letter to BSD-powered Companies and Projects. (via)
- NetBSD GPU support (Intel HD 4400).
- Device Driver Development for BSD.
- Hypervisor on dfly?
- Unfortunately, StackOverflow is a difficult-to-avoid site nowadays… Man pages don’t have this issue. (via)
- “Virtual machine templates for BSD flavours“. Includes DragonFly. (via)
- Mac OS versus FreeBSD: A Comparative Evaluation. Might be paywalled. (via)
- 44CON 2018 CFP Is Open. A security conference in the UK, later this year – not a 4.4 BSD conference that has somehow lasted multiple decades, darnit. However, the source link notes a need for OpenBSD material.
- A long two months. “On Friday we saw the patches Matthew Dillon put together for DragonFlyBSD for the first time. These were the first patches for KPTI that were very straightforward to read and understand, and applied to a BSD-derived kernel that was similar to those I’m accustomed to working on.” Hey, nice credit. (via)
- Pledge: OpenBSD’s defensive approach to OS Security. (via)
- NetBSD proposal for stop-the-world syscall. (via)
The default options on the math/py-numpy port slowed it down. Francois Tigeot noticed, and committed a change that takes advantage of all processors. Read his note to users@ for details.
For your Monday entertainment: the boot log from DragonFly on a system with 11 sockets, 10 cores per socket, for 110 CPUs. Plus 8 TB of RAM.
(Skip past the control codes at the start)
Another across-the-BSDs week.
- What’s Next for Feature Development in FreeNAS/TrueNAS?
- Description of the 1969 proto-Unix system based on a 2812 line PDP-7 assembly kernel. (via)
- The Known Costs of Security Embargoes.
- Military Grade Data Wiping In FreeBSD With BCWipe.
- “Has Linux lost its way?” comments prompt Debian developer to revisit FreeBSD after 20 years. (via)
- Christos Zoulas’s recent NYCBUG talk on reproducible builds in NetBSD is now available as video.
- How do I make quiet build/compile server for home ?
- Libreoffice failing to start after upgrade to 184.108.40.206 40m0(Build:2) (on NetBSD).
- Question about a distro.
- Every Journey Starts with a FAIL. (via)
- Meltdown fix committed by guenther@. Note the DragonFly cross-pollination.
Oh, hey, that’s a nice thing to say. (via tuxillo on EFNet #dragonflybsd)
This isn’t really a dramatic event, but Rimvydas Jasinskas has added support for DWARF-4 line number tables in binutils 2.27. I am linking it to remind everyone that a little bit of Tolkien, in the form of elves (elfs?) and dwarfs (dwarves?) lives in your computer. We need a ORC standard. Oh. Hobbit? Hobbit.
Tomohiro Kusumi has brought in exFAT support to DragonFly from FreeBSD. Useful for cross-platform drives when FAT32 isn’t enough, and NTFS brings its own problems.
The default kernel config for DragonFly has changed: Sascha Wildner has added the acpi, gpio_acpi, gpio_intel, smbus and smbacp devices. If you are using a custom kernel, you’ll probably want to add these. If you aren’t using a custom kernel – you should have no negative effect.
The title really says it all – if you have a Coffee Lake series Intel chipset, your video is accelerated on DragonFly.
Rimvydas Jasinskas created a loader.conf(5) hint that keeps various nata(4) devices from attaching during boot. This is super useful if it’s a device that screws up your boot process. and I think it’s also great if you get irritated having something in your dmesg every time about the device you never use, like a CDROM.