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.
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.
This timer fix enables booting DragonFly on AWS. Well, that and the ena(4) driver. I haven’t tried it yet.
DragonFly now has ministat(1), imported from FreeBSD thanks to Aaron LI. Use it on the output from your next run of benchmarking tools.
It’s bizarre links week this week. Well, more than usual, I mean.
- The Infocom dump, via multiple places.
- Related: What is ZIL anyway?
- Techbros ruin eating, again.
- The Very Mathematical History of a Perfect Color Combination. I’ve mentioned Solarized before. (via)
- A fully reversible USB cable. (via)
- Brix System, life size LEGOs. (via)
- Useful/curious datasets. (also via)
- Cut / Fold Templates. Neat paper, neat interface, neat animations. (via)
- Quake is for everyone. (via)
- A look at IBM S/360 core memory: In the 1960s, 128 kilobytes weighed 610 pounds.
- One reason ed(1) was a good editor back in the days of V7 Unix.
- The Failure of the Great Tip-Free Restaurant Experiment. Linked because of the eternal truth of that last paragraph.
- Storage Performance Reference Guide: Interconnect Maximum Effective Data Rates. BSD site bit not BSD-related.
- Dwarf Fortress diary: The Basement Of Curiosity episode eight – All Hail the War Mayor.
- Dwarf Fortress diary: The Basement Of Curiosity episode nine – Titanfall.
- Efficiency Machines: The Operating System Recontextualized. It’s about a game.
- ArchiveBox. The open source self-hosted web archive. (via)
- Avoiding the gravity well of webbiness in gopher. (via)
- Retro web, simple web, and alternatives to the web. (via)
- I like the whole “computers-in-wood” asthetic [sic].
- Avalanche Noise Generator Notes.
It’s always helpful to see other people’s questions and answers; in this case it’s a conversation about HAMMER2 snapshots and how to manage them. (Follow the thread)
Unrelated to BSD: GPS rollover is happening a few days from now. This affects most people very little, and a few people a lot, but I mention it also to make you think about the systems that underpin our technology.
Thanks to Aaron LI, you can now (actually, since December) run ifconfig without involuntarily loading associated kernel modules, with the -n option. See his commit message for an example.