I'll admit that (even just STARTING) the web browser was my #1 pain point in #OpenBSD, but everything was slow.
The one thing that it did better than the other major BSDs is its resume from suspend was pretty quick. #FreeBSD took 14 seconds to resume from S3 suspend on this box.
Sadly, Gimp 2.10 required Python2 of all things, so I was stuck running the beta GIMP 2.99 (which was honestly fine).
Now that I think of it, I wonder if #OpenBSD's disk encryption wasn't taking access of crypto instructions on the Core 2 Duo??? That would explain a LOT
I've been thinking I'd like to give #OpenBSD another try sometime, but I'd still like to find out why the performance on my Core 2 Duo was so abysmally poor. Not just browsers, but everything, including browsing threads in tut were painful.
I guess if all you did was edit code, then hit compile and walk away and get a coffee, then it wouldn't matter. But as a desktop, it was kinda bad.
There are now separate build files for #macos and #openbsd. This avoids users needing to make direct changes and instead just slightly tweak the Makefile.
I plan to make a basic tutorial for OpenBSD folks 🙂
My SO made me the lovely diamond painting attached to this Toot.
I was asked (some moons ago) to join the EuroBSDcon board - which I humbly accepted.
My talk for EuroBSDcon 2023 in Coimbra, Portugal was accepted.
I feel so incredibly honored to serve the BSD community that I fall short of words. Thank you all, really - from the bottom of my h3art (pun intended) :flan_heart:
(Disclaimer: I know that Wayland isn't all unicorn farts and Lucky Charms for many, especially for my friends in BSD-land. I'm hoping that the growing pains won't be too terrible, but I know they certainly haven't been fun up until this point. FYI #WayBros, "It works great on Gnome/KDE" is not a good apologetic for something that has just gotten past the half-baked stage, and was written in a Linux-exclusive way. But I'm happy so far.)
I'm not sure what the exact syscalls were, but I perused the NetBSD blog post on it, and it seemed to be pretty intense.
Actually, Wayland isn't the only alternative, but I don't remember the name of the other display server. Maybe someone more involved in the #OpenBSD world can fill us in on their plans and progress.
I liked the OS a lot; I just had to discontinue using it for performance issues which I didn't know how to troubleshoot.
Switching over from Bitwarden to pass has been fairly smooth. Nothing against Bitwarden, just difficult to run things nicely with that workflow via #OpenBSD
Now syncing all my machines (and via iOS) might prove more difficult...
The more I use and read about #VoidLinux the more I'm leaning towards waving goodbye to my bae #ArchLinux . I'm not 100% sure yet so I've decided to setup my old laptop exactly how I want for daily driving and see how it feels compared to my Arch daily driver. Oh yeah the meme below is just a little fun and you may well have other opinions but I'm starting to feel Void does seem better for me. 🤔
Me and my clumsy wording.
Honestly, I had a lot of hangups with both the Devuan and Debian installers, because I couldn't figure out how to get #libreboot working with true full-disk encryption. It works fine in #OpenBSD and #FreeBSD, but not #Linux, as far as I was able to tell.
I was surprised that Devuan didn't use the same installer as Debian though.
Nevertheless, thanks for contributing to #Devuan! :D
I'll try Devuan next.
I'll be giving #OpenBSD a fair go this weekend on my X201 (posting from that machine right now!). Running my patched suckless programs and I'm quite happy so far...
I love you, #FreeBSD, but 14 seconds to resume from S3 sleep on my stinkpad X200 (and no option for S1 or S2) is starting to get on my nerves.
Just upgraded to 13.2-RELEASE, too.
Still 14 seconds to resume when opening the lid, but with the added benefit of just rebooting when trying to resume with the power button now.
UPDATE: No more reboot when resuming from S3, that seems to have fixed itself, so that's good, but I have no leads on the slowness of resume.
I really don't know why this makes me angry but it does. The virt-manager program on Linux treats #openbsd as a legacy system. In no way is it legacy! 😾 The project continues to develop timely and interesting software innovations.