Makes sense. I've always assumed that OpenBSD has a very narrow use case anyway. I love it for a network firewall because the configuration files are sane and easy to understand (stares at systemd networkd). I set it and forget it.
I Stopped Using OpenBSD
11–20 of 81 posts
Re: I Stopped Using OpenBSD
#12Sorry to see Solène Rapenne move on, I wish her success going forward. She has been a great asset to the OpenBSD team. But glad she will still try and help them out a bit. But in a way she has a point :( Just a few weeks ago I had a panic with 7.6 and half my files in /home disappeared. In the past I never lost data on an fsck, plus I never had a panic in many years. But glad I clone /home to another device daily :)…
That's insane. Note to self, never use openbsd where I can't reconstruct the system from scratch.
Re: I Stopped Using OpenBSD
#13“I can not do that on OpenBSD without a huge headache and very bad performance.”
This applies to practically everything, not just virtualization!
Re: I Stopped Using OpenBSD
#14TL;DR: OpenBSD is bad as a desktop (no bluetooth, limited gamepad support, etc).
Sounds like it's not great as a server either, if the virtualisation support still isn't up to scratch.
She states in that post she had issues running virtual machines on OpenBSD. This isn't the same running OpenBSD in a virtual environment.
Re: I Stopped Using OpenBSD
#15Something like 99% of the use cases I've seen for OpenBSD are servers that have no keyboard, mouse, video, audio or other plugged into them. It's completely unsurprising that bluetooth and gamepad support isn't a priority.
Yea, I noted that too.
As a gamer & dev running Linux, I pass-through bluetooth hardware into a gaming VM for controllers and don't even have bluetooth stack on host.
Re: I Stopped Using OpenBSD
#16I like Linux a lot but personally I am starting to get frustrated with rootless containers. It is frustrating one has to have higher privileges running the container to make it have its own IP address inside the container. It's frustrating you cannot have the container read and write on the filesystem as the UID running the container unless the process inside is root.
I might have a better experience with VMs but every system seems like a lot of effort to just get something running. And after that the object is not as disposable as I'd like. My favorite tool for VMs so far is Incus. I'm planning on looking into Firecracker this weekend for fun.
Unrelated, but regarding:
> I understand it can make some people angry as they have to learn how to use it.
I don't think that's a significant part of what is upsetting anyone.
Re: I Stopped Using OpenBSD
#17It seems her biggest issue by far is bad VM hosting, followed by the filesystem (the latter being possibly an hardware compat issue). Everything else seems tertiary or downstream from the big one.
Better VM hosting would enable a big usecase directly, enable the software separation she likes, ameliorate a good part of the battery issues (as that's what she often uses the OS for), and with passthrough maybe even help work around the other hw support issues.
Given how critical virtualization is to security anyway, it sounds like a topical thing for OpenBSD folks to put directly into the OS (a la bhyve).
Re: I Stopped Using OpenBSD
#18> flatpak: I really like software distribution done with flatpak, packages are all running in their own namespace, they can't access all the file system, you can roll back to a previous version, and do some interesting stuff
As of today flatpak still has holes you can drive a truck through.
Re: I Stopped Using OpenBSD
#19> flatpak: I really like software distribution done with flatpak, packages are all running in their own namespace, they can't access all the file system, you can roll back to a previous version, and do some interesting stuff As of today flatpak still has holes you can drive a truck through.
Use flatseal with flatpak.
Re: I Stopped Using OpenBSD
#20This points out something we forget at times: being a fan of a thing shouldn't mean we have to suffer for it. NetBSD doesn't have GPU compute capabilities, plus browser DRM is a PITA, so I run macOS, too. If I have to choose between not doing a thing at all and doing it in a less enjoyable environment, it's only my own foot that suffers were I to choose not doing it at all. What really matters here is that systems sh…
I suspect a lot just comes down to manpower... While extremely important the FS currently works "good" enough (although there were/are efforts to port HAMMER2).
But I share the frustrations, all these little papercuts really add up and I only use OpenBSD in server settings nowadays