If you installed BSDStats but it didn’t work, here’s why – with a fix.
How many levels of plug-in can you find?
It’s probably going to be quiet for at least a few days because of the Christmas holiday, though I’ll of course have the normal weekend features up.
In the meantime, here’s something to ponder: this post about tmux and plugins for it led me to thinking about plugins in general. The pkg system is sort of a plugin scheme for BSDs, much like apt for Debian, yum, etc. Each language has its own libraries to load and plugins to manage past that, like Perl’s CPAN. Nowadays, applications have their own plugins. For instance, a system with WordPress installed with PHP installed with PHP plugins required with WordPress plugins that also require given PHP libraries. WordPress manages keeping itself and its plugins up to date, but not the underlying PHP installation. You can get something similar with Perl along with the Perl-specific package updates, through cpanm. Or, npm, which seems to be its own world of constant flux.
How many levels could this go? Like running multiple emulators within each other, how many levels of plugin could you achieve? There’s probably a series of levels proceeding from tedious to barely maintainable to ridiculous.
Where to find dports build results
Synth logs for dports are now located here on a new machine:
https://sting.dragonflybsd.org/dports/logs/Report/
If there’s only a short list, it’s because the most recent build was probably focused on retrying a broken-but-now-possibly-fixed package. I link both because of the utility and also because the interface is pretty.
A good time to update dports
There’s been a fresh binary build of dports – and then some more updates to cover a variety of security issues in some of those ports. Now is a good time for a ‘pkg upgrade’.
Signal safety in DragonFly
Some of the larger application sets on DragonFly have had trouble building, and inconsistent problems with that build. i.e. rust would fail, but in different parts of the build process, every time. It looks to be a problem with signal interaction, and there’s now much safer ways to do that on DragonFly.
That is going to require a full buildworld/buildkernel if you are on DragonFly-master, 5.7. Release/5.6 users are unaffected.
dsynth defaults to xz
Remember how I said dsynth defaults to txz (tarred, XZipped) ? I was apparently wrong and it was using tgz (tarred, gnuzipped). Now it really truly defaults to txz, for space.
PAM perturbed
Pluggable Authentication Modules on DragonFly have gone through some changes. pam_ssh has been removed, along with pam_tacplus, and pam_radius, in favor of the more frequently updated versions in dports. ppp(8) still supports radius, though.
Reminder: set hostname
You should set hostname in /etc/rc.conf. I am mentioning this now because not doing it kept me from running X apps from a DragonFly system on a Windows 10 system with vcxsrv, and I wasted half an hour of my life figuring that out. Apparently this is a lesson I need to keep relearning.
Watching dsynth go
dsynth(1) has a new ‘monitor’ command, which watches log output and tells you what it’s doing. I haven’t tried it yet, so I am only guessing. A screenshot would be nice.
dsynth: you’re building it
utmp out, utmpx in
The headline is a little misleading; umtpx has been in DragonFly forever, but now utmp is really retired and programs adjusted to match. The change is not that user-affecting and utmp data is still accessible; this is part of the ABI change alluded to over the past week.
If you are not familiar with utmp(5) and utmpx(5), they are databases in /var that track user logins and system restarts. utmpx is of course better cause it has an X.
New packages for DragonFly-current
If you are on DragonFly-current, the ABI changes of the past few days are complete and new dports packages are built, so now is a good time to do a complete build and install of world and kernel, and then a pkg update.
5.6 users can keep on keeping on; no breakage there.
ABI breakage in DragonFly master
There’s commits being made in DragonFly that will break binary compatibility. If you are running DragonFly-master, that means you will need to do a full buildworld/buildkernel when updating, and you will either have to rebuild packages or wait some days until a new set are built.
If you are running the 5.6 release, you are unaffected.
Scrolling in X
I’ve seen a similar config other places, but it never hurts to note: scrolling in X requires just a few xorg config lines.
dsynth details on DragonFly
First, history: DragonFly has had binaries of dports available for download for quite some time. These were originally built using poudriere, and then using the synth tool put together by John Marino. Synth worked both to build all software in dports, and as a way to test DragonFly’s SMP capability under extreme load.
Matthew Dillon is working on a new version, called dsynth. It is available now but not yet part of the build. He’s been working quickly on it and there’s plenty more commits than what I have linked here. It’s already led to finding more high-load fixes.
New servers, new tech
Following up on an earlier post, the new servers for DragonFly are in place. The old 40-core machine used for bulk build, monster, is being retired. The power efficiency of the new machines is startling. Incidentally, this is where donations go – infrastructure.
pkg and pkg-static
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.
DragonFly 5.6.2 released
Because of the recent tcp keepalive change and some other updates, DragonFly 5.6 has been updated to 5.6.2. See my release email, and update the normal way. You will need to update your installed dports.
tcp keepalive and dports on DragonFly
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.
Dports update for DragonFly-current
The binary package repository for DragonFly-current has been updated with the latest build of all packages, thanks to tuxillo and others on EFNet #dragonflybsd doing a lot of work.
Tuxillo noted: there’s new rust, thunderbird, firefox, nginx, several llvm versions, and a new chrome (version 72). freerdp is temporarily broken; use remmina with the rdp plugin instead. openvpn isn’t upgraded yet cause the build was with libressl, which is a broken combination – it’ll all be built with openssl in a future run.