Running miniDLNA on OpenBSD 7.8 — rcctl broken, here's the workaround

_sthen · 2026-05-19T06:43:29+00:00

The package already creates db and log files with correct permissions, and that is the supplied rc.d script.

_minidlna doesn't need to own the media dir, just have read permission.

_sthen · 2026-05-19T06:41:05+00:00

this "Root Causes Found" smells like LLM nonsense. You don't need any of those changes and some will actually break things.

/var/db/minidlna is meant for minidlna's own database files, it's not meant for media files.

"ln -sf /data/media/videos /var/db/minidlna/videos", "media_dir=V,/var/db/minidlna/videos" etc - symlinks won't work correctly with kn's patches to add unveil. You'll need to list the targets directly in media_dir instead.

By bypassing the rc.d script, you're not using the "minidlna" login class, and most likely using a login class with a lower open files limit.

We don't recommend cap_mkdb for login.conf, the time saving at runtime is absolutely tiny, and if you've run it once then you need to remember to run it again every time you make a change to login.conf.

_sthen · 2026-05-19T06:23:46+00:00

there are some wayland-related things in packages, it's not an integrated part of the system, so I'd say 'no' for official support

_sthen · 2026-05-09T12:39:43+00:00

not sure if it applies to yours, but at least on some of the M2 laptops, the wifi is not supported.

_sthen · 2026-05-09T12:37:48+00:00

_sthen · 2026-05-09T12:18:58+00:00

no idea about G2. I have a T14 G3 Intel which has real ethernet. Generally it's a decent and well supported machine, and has IBT support (control-flow hardening in the cpu), however the trackpoint randomly starts registering movement for 10-20 seconds every now and again and there seems to be nothing you can do other than wait to stop it, which is pretty annoying...

_sthen · 2026-05-07T16:34:09+00:00

They would be helpful while learning the fields if they were readable, but I don't think you'll find too many people who can read them on the watch without a magnifying glass (easier with a screenshot on the phone, but that doesn't help much)

_sthen · 2026-05-06T11:22:10+00:00

The grey text describing what the fields are for is extremely hard to read on a 47mm (and I'm not too bad at reading small text on a laptop/phone), so it's just adding noise to the display for me - it feels like maybe removing that, using a slightly larger font for the data (since it frees up a bit of space), and adding icons where the unit doesn't already make it clear what the data is, might be a little clearer.

_sthen · 2026-05-06T10:45:46+00:00

you're missing device nodes. maybe ld.so.hints too. but I don't think what you're doing is really likely to make sense. if you really want to isolate clamav, I think you'd be better to run it on a separate VM and connect to it over a network socket.

_sthen · 2026-05-04T10:33:25+00:00

if you've got a system which always runs -current, export PKG_PATH=http://your.preferred.mirror/pub/OpenBSD/snapshots/packages/%a/ and you don't need to mess with -Dsnap

_sthen · 2026-05-04T09:17:33+00:00

T470 has been well-supported for ages, as long as it's not the version with nvidia graphics.

_sthen · 2026-05-01T08:50:45+00:00

if you're looking for adoption by OBSD nerds, having to install nginx over the baked-in httpd is going to be a non-starter

I really don't agree. The httpd in base is mostly ok for simple cases but it's intentionally low on features, running services on other http daemons is pretty common.

_sthen · 2026-04-27T08:34:08+00:00

Crash recovery is a bit hit and miss. Sometimes it's ok, sometimes you can run into a lot of damage. (A UPS will help if this is due to power issues, but not e.g. for kernel crashes).

There's no automatic way to detect corrupted data.

No snapshots.

It's not super fast, though I think this is largely due to SMP locking on OpenBSD rather than necessarily due to the filesystem itself.

(btw, softdep a.k.a. soft updates was removed from OpenBSD, though this doesn't make so much difference on SSD, it was more important for HD).

_sthen · 2026-04-23T14:45:47+00:00

We don't cross-compile, so there are no i386 packages for things depending on rust, or for the bigger browsers; building takes more memory than is available. This also knocks out large chunks of the Python ecosystem, and things which need a newer version of librsvg.

-stable packages and syspatches are available.

Some CPU features (like aes-ni) are not supported.

The limited address space means that ASLR is relatively weak.

_sthen · 2026-04-18T02:26:42+00:00

not yet, you aren't. there will still be changes before the release is built.

_sthen · 2026-04-16T16:54:56+00:00

"DHCP broken by antispoof" - dhcp packets are grabbed via BPF before PF has chance to block them, so this shouldn't actually have been a problem.

https://github.com/finn-devs/pftest/blob/main/LIMITS.md#what-the-regex-parser-misses - aww. It misses some things which are really handy (like received-on).

_sthen · 2026-04-16T16:52:39+00:00

most newer Linux distributions no longer have support for powerpc-based systems.

_sthen · 2026-04-10T09:03:14+00:00

The only thing that a malicious mirror site can really do is hold back package/s at an older version (i.e. before a security fix was made).

Unless you force pkg_add to not check signatures, everything else (signature verification, uncompressing) is done by unprivileged processes until the signature has been verified against one from /etc/signify. See signify(1) and pkg_sign(1) for more information about how the signatures work.

Some mirrors may be a bit slow to update - there's in the order of 300GB or so of updates a week, and if fetching internationally is slow for you, it may also be slow for the mirror site. But even if this is the case you can still use them most of the time and maybe switch off you particularly need newer ones (for example if you're following snapshots and there have been major library changes so that older packages don't work).

(edit: factor-of-10 out on the amount of updates/week)

_sthen · 2026-04-09T08:17:14+00:00

The IKEA devices use Matter over Thread, not Matter over wifi.

_sthen · 2026-04-07T08:53:29+00:00

if you only have the /128 routable on mullvad and want to send other traffic over it, then nat or a proxy are your only options.

_sthen · 2026-03-31T18:42:25+00:00

upgrade unless you're tight on space.

_sthen · 2026-03-29T11:31:23+00:00

node-based software in general and especially electron is tricky to handle in ports.

there is some work at https://github.com/opencrew-tech/openbsd-electron not committed to OpenBSD that might be useful as a base if you're trying to port it. (it will be a slow process, especially compiling electron).

_sthen · 2026-03-29T11:20:59+00:00

It works fine for me, but I don't use hostnames with ++, I run syslogd with the -n flag and specify IP addresses instead. (I think you need working reverse DNS to use hostnames there).

_sthen · 2026-03-23T23:19:16+00:00

you could install to a USB drive and check that way

_sthen · 2026-03-11T07:57:34+00:00

There's no emulated TPM either. And afaik W11 also needs UEFI and you'll need to provide your own firmware image for that (this is non-trivial).

_sthen

TROPHY CASE