There’s a new page on the DragonFly site covering how to install DragonFly as a guest system under KVM.
I know I’ll need this again, so I am making a post out of it. If you are running a DragonFly system through NVMM using the excellent site instructions, and you want X apps to display on a local Windows workstation, you need to:
- Install VcXsrv (or your X server of choice) on Windows and start it up.
- Install xauth and xterm on the DragonFly host.
- On the DragonFly host, set these three options in /etc/ssh/sshd_config. They are already there but commented out with different arguments.
X11Forwarding yes X11DisplayOffset 0 X11UseLocalhost yes
- Reload sshd: ‘service sshd reload’.
- ‘Enable X11 Forwarding’ under Connection -> SSH -> X11 in the puTTY setup dialog.
Connect to the DragonFly host with puTTY, type ‘xterm’, and a terminal window should appear on your Windows desktop within a few seconds. This could be turned into a shortcut with puTTY to avoid having redundant terminals, but I’m not writing that out yet.
Linked here cause maybe it’ll help someone else with synproxy and pf in DragonFly: synproxy state doesn’t work in Packet Filter.
Here’s something I just learned: If you are running dma(8), /etc/dma.conf will contain MAILNAME. If your email server is somewhere else, but you set MAILNAME as your domain – dma will deliver locally.
I had /etc/dma.conf set with MAILNAME shiningsilence.com – so dma kept delivering overnight periodic results to root, which was aliased to firstname.lastname@example.org in /etc/mail/aliases and so it was delivered to ‘justin’ locally on the machine.
Changing MAILNAME to www.shiningsilence.com – the host you are reading right now – fixed the problem. Now, whether this was an automatically set config or something I misconfigured some years ago… I can’t tell.
I didn’t know about this, but there’s a daily/weekly/monthly/security_show_badconfig option in periodic.conf that is now defaulting to “yes” in DragonFly. This I assume means you’ll get the output of erroring periodic scripts sent to you. Useful, especially if you find out about an error you hadn’t seen before.
If you’ve got unshielded disk cables in a tiny PC, you can run the AHCI link a bit slower to better handle interference.
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.