I managed to find an ancient Wyse-185 terminal at my workplace today, left in the corner of the server room. For entertainment purposes only, I booted DragonFly in VirtualBox and attached the physical terminal to the physical serial port on my Windows laptop docking station, mapped through to that virtual machine.
I have already discovered that the character output will often pause until the keyboard is used, which may be a settings issue. Mash the keyboard enough and VirtualBox dies. I’d use different emulation but Hyper-V doesn’t support serial and Qemu I haven’t figured out.
It’s entertaining, though I am not sure what I will do, other than maybe run GRDC once I figure out the reason for output pausing.
I’m on mailing lists for KnoxBUG, SEMIBUG, and NYCBUG, so I know to post about upcoming events. I know there are more out there – can any members point me at the appropriate announcement mailing lists?
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.
Thanks to tuxillo and others, there’s a new build of dports on the way for DragonFly 5.4 that includes packages that weren’t building before – mongodb, kodi, mysql80, and I imagine more that I don’t know about. If the synth build is still running when you read this, you can look at its status page. If it isn’t running, the packages are of course in the normal place and you can use ‘pkg upgrade’ to get them.
Tobias Florek had a soft model made of Fred, the DragonFly mascot, years ago. He is moving and found a few unsold units. If you are in Europe (for shipping), and are interested in them, contact Tobias at email@example.com.
On your next DragonFly upgrade, watch the end of your ‘make upgrade’ output. You may have some deprecated files, especially if your system has been upgraded through several releases.
= You have 11 now deprecated files. = Once you are sure that none of your third party (ports or local) = software are still using them, rerun with REMOVE_DEPRECATED set.
The now-deprecated files will be listed just before this warning. They aren’t removed automatically in case there’s installed software still linking to them. If you are running only dports software, and are up to date with all of it, you are probably fine to remove these files:
make -DREMOVE_DEPRECATED upgrade
If you have software you compiled yourself some time ago, it may have linked to these old files. One way to search for that would be to use find to find all executable files that are in particular directories, and then use ldd to see what shared libraries are used by each executable:
… and then grep for the names of the deprecated files. You’ll get a bunch of “not a dynamic executable” errors when you do this because it’s a rough example I did for this post, but you can always pipe the stdout of the command to a file and review later. If you do turn up any executables linked to the deprecated files – recompile!
(If you have a better find string or strategy, please comment.)
This should, I hope, affect no-one except people running DragonFly mirrors: I moved all the DragonFly 3.x release ISOs into a different directory than the normal master download location. This should shrink mirror size.
DragonFly 5.4.1 is out, just in time for Christmas. My users@ post describes upgrading, as do the 5.4 release notes. The changes in this version are in the tag commit, which can be summed up as “keyboard fix, dhcpcd support, HAMMER2 improvement”.
Images are available for download at various mirrors, too. If you’ve recently upgraded to 5.4, it’s the normal build process.