I Stopped Using OpenBSD
dataswamp.org
I Stopped Using OpenBSD
1–10 of 81 posts
Re: I Stopped Using OpenBSD
#2[deleted]
Re: I Stopped Using OpenBSD
#3TL;DR: OpenBSD is bad as a desktop (no bluetooth, limited gamepad support, etc).
Re: I Stopped Using OpenBSD
#4TL;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.
Re: I Stopped Using OpenBSD
#5Sorry 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 :)
But I still will use OpenBSD for testing items I develop on Linux. It is a great help finding issues where Linux will ignore some bugs I insert.
Re: I Stopped Using OpenBSD
#6TL;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.
And losing files after a crash is something that hasn't happened to me for at least a decade (not with NTFS,ZFS(FreeBSD),UFS2(FreeBSD), ext4 or XFS), maybe rip out soft updates was a bad idea?
Re: I Stopped Using OpenBSD
#7This 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 shouldn't crash or panic at all, ever, or if they do, the filesystems used shouldn't lose data or otherwise become corrupt. We left the lack of memory protection in the '80s (some of us the '90s), so there's no excuse if the hardware isn't faulty.
So I have to wonder why the OpenBSD folks, who prioritize security over speed, for example, wouldn't prioritize stability over everything except possibly security (I'd rather a panic than a compromise) and spend some energy looking in to these issues and fix them?
Why wouldn't any filesystem corruption (which could have security implications if the corruption can be controlled) and/or data loss be considered a sign of other deep issues and be made a high priority at OpenBSD?
Perhaps Solène's writeup will be a good wake-up call for the OpenBSD people.
Re: I Stopped Using OpenBSD
#8Something 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.
Re: I Stopped Using OpenBSD
#9Journaling filesystems have been around for decades now; I don't think I've had a data loss incident since I stopped using Windows 98? I know it's volunteer driven but it seems like working on data integrity might be more of a benefit for security than some of the gimmicks like TRAPSLED.