If you are upgrading an older 5.8.x system to DragonFly 6, and get a lua error when updating pkg: manually copy over a config file, and you’ll be set.
If you edit /etc/fstab, and then later change something like the proc filesystem from OpenJDK, you might not boot normally. Antonio Olivares has a solution for you.
Working on less traditional BSD links here.
- Toward an automated tracking of OpenBSD ports contributions.
- Commentary on the MacOS -> FreeBSD article from last week.
- BSD Unix Hardware Support Database. (via)
- BSD Discord server. More linked in comments.
- Become shell literate. Wonderfully not Linux/bash-specific.
- There’s always more history. Early BSD work, indirectly.
- CentOS killed by IBM – a chance to go new ways?
- Set your favorite pager.
- OpenBSD on TECLAST F7 Plus.
- OPNsense 20.7.7 released.
- Valuable News – 2020/12/14.
Well, it doesn’t fix anything, but it seems like an answer that almost always helps: running sysmouse usually fixes most X11 mouse problems.
The ChiBUG monthly meeting has gone virtual, so go now if you are interested. The thread about it also includes some notes on how to connect under BSD that may be useful beyond this immediate event.
If you delete all your installed packages, you will also lose the certificate used by pkg to verify the connection to download new ones. There’s several workarounds for this problem.
Screen switching, where an xterm’s contents return to what it was before starting a full screen program, was turned on and then back off for DragonFly. It would have only affected DragonFly-current users, and even then only for a short window of time. If you encounter it anywhere else, though, here’s how to turn it off using Xresources.
Instead of posting about updates, here’s a feature that you will hopefully never notice: ‘make upgrade’, part of the upgrade process in DragonFly, will now go look for 3rd party software built to depend on deprecated DragonFly system libraries, before removing those libraries. (details) If you’ve had a program stop running because something else was upgraded – and I’m sure you have, cause “dll hell” is an actual phrase – you’ll be thankful for this.
A note for the future: if pkg itself isn’t working, you can use pkg-static.
Did you know there’s a default size limit to pf’s routing table? I did not, but it makes sense that there is one. If for some reason you bump into this limit (difficult for home use, I’d think), here’s how you change it.
karu.pruun posted an answer on how to get DragonFly onto your GPT/EFI drive.
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.