A running description of activity related to DragonFly BSD.
Jails on DragonFly can now route to loopback addresses (i.e. 127.0.0.1). Because of this, they can work like shared IPs and the jail can connect to the host.
I think this means that you no longer have to bind jail services to specific IPs as you did previously. Don’t quote me on that; I’ve run few jails in my life.
Update: I should have linked this too: the sysctl jail.defaults.allow_listen_override that makes it easier in the host system too.
Again, dumping out all the links I can in case you are stuck at home.
Your unrelated music link of the week: Hannibal Rex – The One Hundred & Forty Faces Of?.?.?. Has the same drive as early Mix Master Mike, to my ear. (via)
Linked cause I always forget the right shell command for UTF-8, to reduce the amount of ???? ??? ??? ??????? ??.
I imagine this may work for any BSD, really. Aaron Li has the instructions, which may be especially useful for non-English readers.
There’s several accidental themes fighting it out this week.
Your unrelated music link of the week: Cosey Fanni Tutti ?– Tutti. Found via Ted Gioia’s Best 100 Albums of 2019, which was discovered via Conversations with Tyler. There, now you definitely have enough to listen to until 2020.
I thought this would happen: the nrelease(7) process can use binary packages to build DragonFly. (For the dports packages, not the base system.) This is very interesting to me, but also useful for anyone who wants to build a custom DragonFly; something I think more people could do.
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.
This week is a nice mix between useful and entertaining.
I’ve seen a similar config other places, but it never hurts to note: scrolling in X requires just a few xorg config lines.
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.
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.
Aaron LI’s fixed a bug in rconfig tag names. This is minor, but I think rconfig(8) is a very powerful and underappreciated utility, so I point it out whenever possible.
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.
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.
‘daftaupe‘ has updated the installation page for DragonFly to note what different steps you use when doing a manual install over encrypted HAMMER2.
A question on starting up a virtual kernel on DragonFly and sticking it in the background led to some suggestions – follow the thread.
I am posting this so it can help someone else, someday.
I have a DragonFly-5.4 system. I installed mysql56-server, and started it up. By default, it listens on “*”, which meant it listens on a local socket and IPv6 ::1 – not 127.0.0.1.
2019-06-04 13:35:03 15833 [Note] IPv6 is available.
2019-06-04 13:35:03 15833 [Warning] Failed to reset IPV6_V6ONLY flag (error: 45). The server will listen to IPv6 addresses only.
I put bind_address=127.0.0.1 into my.cnf to get IPv4 loopback to work. Local socket connections still worked either way. I’m not using IPv6 on this machine, so this solution works in this situation. I’m not sure my mysql decides to go only IPv6 based on a strange flag, but mysql is reliably unreliable.
Remember the commit that autocreates human-readable disk device names under /dev? (Here’s a reminder.) It’s now in 5.4 – technically, since 5.4.2. Anyway, it will automatically identify the root USB disk when you boot from a USB .img file, so you no longer have to guess which /dev/daX file it was – usually da8 but sometimes you got a surprise instead.