DragonFly’s tap(4)/tun(4) devices have been historically precreated – tap0, tap1, tap2, tap3. They are now auto-cloned, which might surprise any software counting on the prior behavior. I don’t know of any specific packages that are affected by this, though. DragonFly version 5.6 is unaffected by this; it’s in -current only.
If you upgrade DragonFly and one of the shared libraries used by pkg gets updated, you can’t run pkg until you get files, but pkg is the program you use to bring in new files. This chicken-and-egg problem is solved with pkg-static, a version of pkg built without shared libraries.
You may have noticed some format flip-flopping between pkg and pkg-static if you had to run it after the most recent DragonFly upgrade; that is fixed. There’s a larger issue of certificate installation identified there; I don’t know a solution to it, but I do want to mention this for next time pkg breaks for someone – pkg-static will work as backup, including to bring in a new version of pkg.
When you encrypt your DragonFly boot drive, initrd(7) is run to get your system online and able to accept a password to decrypt the drive. So far, so good. The initrd program is a minimal userland designed to be small, and it generally works. However, it assumes a QWERTY keyboard. If you’re Pierre-Alain TORET and normally use an AZERTY (in this case French) keyboard, that makes it difficult to type the decryption phrase.
It’s possible to patch a different keyboard layout into initrd, and he has documented just how to do that.
Remember my post about a new upgrade script? tse, the author, has happily added in a bunch of suggestions. I’m intermittently traveling and can’t do anything to test it for days yet – but I’d love to see others try it out.
The bugs issue tracking versions is here: #3197. Can you, dear reader, try it out? Do an in-place upgrade on your version, or even a test install with a VM? I want to see what happens in the wild.
This slipped in just before the 5.6 release, and I thought I had already noted it: DragonFly now defaults to HAMMER2 for disks during install, instead of HAMMER1.
There’s now a read-only sysctl ‘jail.jailed’ that can be checked to see if the current environment is running within a jail; useful for scripts that should not run in that environment, etc. I link to it mostly because it’s an odd sort of meta-signifier of reality, like being awake or in a waking dream, and that entertains me.
DragonFly’s tcp keepalive was changed from milliseconds to seconds. This happened in both DragonFly-current and in the 5.6 release, and it changes the networking API, which means a dports rebuild is needed… or a pkg upgrade, for which happily all packages have been rebuilt. So, on your next update of the system, be sure to update packages too.
BSD Now 306 is up, with the normal mix of stories about multiple BSDs… Except two separate ones are about DragonFly, so this week is extra good.
You’re probably used to the ‘make buildworld; make buildkernel; make installkernel; etc etc’ dance on each upgrade at this point. ‘Tse’ has created a script that rolls that all up into a single action.