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.
Nan Xiao needed a taskset tool on DragonFly, so he made one. It’s apparently similar to usched(8).
If you want to see all running threads on your system, grouped by process, with who ran it and how much memory it’s taking, it’s easy: ps -alxRH.
I mention this because it’s easier to remember ‘alxRH’ than it is to find all the right options in the ps man page.
I’ve mentioned dbus and DragonFly a few times; here’s one of those “you will eventually do this” tidbits: if for some reason you are installing it for the first time, remember to start it with the rc script.
Who can recommend a dynamic DNS service? (I’d like to know from direct experience, not Googling.) I’ve been using Dyn for years, but they’ve been unintelligibly merged into the Oracle behemoth, and I need to change.
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.
In a larger users@ thread about multiple BSD development systems and how to set them up, I spied this tip on making multiple local virtual machines all reachable via SSH.
Shamelessly copied from my own users@ post: I tagged 5.6.1 and built it earlier today. This version has a corrected sshd_config and fixes a lockup bug in ttm. The ISO should be showing up on mirror-master.dragonflybsd.org in the next 20 minutes or so, or you can rebuild using the normal process on an existing 5.6 system:
If you are still on 5.4 or earlier, you need to bring in 5.6 sources, which is noted in the 5.6.0 announcement.
OPIE was disabled recently in DragonFly. Now that the 5.6 release is out, it has been removed. This may require manual intervention if you are on DragonFly-master (i.e. 5.5. or 5.7) and update in the next day or two. This need to fiddle with it will go away soon with changes to ‘make upgrade’; I will mention it when I see it.
This won’t affect anyone running 5.4 or 5.6. It’s only in development.
DragonFly 5.6.0 has been released. This version brings an improved virtual memory system, updates to radeon and ttm, and performance improvements for HAMMER2. Matthew Dillon did some informal testing of the VM improvements, and posted results to the users@ list.
My users@ post has the usual details on upgrading (pay no attention to my 5.4 typo), as do the release notes.
ISO and IMG files of DragonFly 5.6rc1 should start showing up at mirrors over the next few hours. This is the release candidate, not the release, so don’t install unless you want to test.
Thanks to a suggestion from Lassi Kortela, man.dragonflybsd.org now exists and takes you directly to the online man page interface, similar to man.(free/net/open)bsd.org.
A question on starting up a virtual kernel on DragonFly and sticking it in the background led to some suggestions – follow the thread.
NYCBUG is meeting at Suspenders, tomorrow. The announcement has details. Go, if you are near.
That sounds like a good thing, right? No automatic bugs, just manually placed ones. What it really means is that bugs.dragonflybsd.org no longer autocreates users, cause there was a certain amount of spam coming through freely created accounts there. It may be hard to tell the next step.
Here’s something that might be useful: an example cleaning file for creating an AWS DragonFly image. Here’s the blob if you want to see what’s in it. I assume you will want to install awscli to use.
There’s a vmm demo from Josh Greene tomorrow, at SEMIBUG’s monthly meeting. Go, if you are near.
It’s on the RSS feed but not in the normal place, and it’s early, so I bet this week’s BSD Now is put together early because of travel. I’m linking to it early for similar reasons.
If, like me, you’ve been running DragonFly for a long time, and you haven’t switched away from tcsh for your account or for root, you may not have ‘set autorehash’ in your .cshrc. Newer installs have it.
Put that into .cshrc if you don’t have it, and it’ll save 15 seconds of the rest of your life not typing ‘rehash’… assuming you can overcome the muscle reflex.
Remember my Wyse terminal experiment with a DragonFly VM? I mentioned an odd output pause where the screen would stop updating until there was keyboard activity – or occasionally just die. That was an artifact of Virtualbox; running this now in Qemu has no such problem.
I now have a very overcomplicated clock! I’m running GRDC on this Wyse-185 connected as a vt100 to the virtual machine running DragonFly 5.4 in Qemu on my Windows 10 work laptop. It’s at 9600 baud so I can see the numbers morph. I find this aesthetically satisfying.