I always thought IRC was pretty decentralized, but I didn’t realize talk(1) was designed to work machine-to-machine. That means in theory that if you have a talk(1) binary on your machine, you could chat directly to anyone else with the same binary, even on a different platform. Since 4.3BSD! Anyway, I only realized this because of this recent bugfix thanks to Dan Cross.
If you upgrade pkg on your system, it may start erroring out. This is because the default config will confuse the newer version. To fix this, you can copy over a working config and the problem will go away. I expect this may only be a problem until the next release.
You can’t tell directly from the commit message, but committing to DragonFly may trigger a reminder to MFC, based on commit message content. This is thanks to Aaron LI. It’s little, but this sort of automation is a good idea.
So, if you find yourself in possession of an ADM-3A terminal, and want to attach it to a DragonFly machine, here is the /etc/ttys config (viewed on the ADM-3A itself of course) and the front switch settings that worked for me.
This won’t affect your day-to-day operation of DragonFly, but it’s interesting: apparently, uptime was always (now minus boot time). If you reset the clock on the machine, however, it would no longer be accurate. Now it is accurate, for a number of utilties.
The next release of DragonFly will be 6.0, mostly because 5.10 is an annoying version number rather than any significant version changes. We’re due to release by the biannual calendar schedule – but there’s a DRI bug that needs to be fixed; I plan to tag as soon as that’s done.