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.
I'm thinking of trying out running #OpenBSD on a server instead of #Ubuntu, because Derek Sivers recommended it for its security (particularly around the more controlled packaging).
I have basically zero experience with BSD, but a ton with #linux (redhat, ubuntu, arch, centos, amazon linux, etc.).
Any advice on making the transition? Is this a good move or unnecessary or bad?
I don't have sympathy for #OpenBSD or #LibreSSL. However, I can understand that they had good reasons to fork OpenSSL, and that switching back today would be hard. I can understand projects refusing to officially declare support and rejecting workarounds.
OTOH, pushing LibreSSL hate to the point of blocking Python implementations that don't link to OpenSSL is just horrible. Users get in the crossfire, again.
Have you ever noticed that there are certain directories everyone has? ~/Documents, ~/Downloads, ~/Desktop, and so forth? Some of them you don't need, some of them you might wish were named differently, but any time you rename or delete them, the originals reappear?
You see, these directories follow a standard so that all programs know where they are—with the right tools under your belt, you can customize them.
That's pretty wild!
Reminds me a bit of #OpenBSD's focus and elegance, but on another level ;)
Are there any tiling WMs, or is it the interface more like cwm. Is there any progress on that front, or is that just not a priority? (which is totally fine)
It's another priority thing:
Bluetooth isn't a priority for #OpenBSD
Having a cohesive OS with good docs isn't a priority for 90% of #Linux distros
Being remotely SANE isn't a priority for #Canonical
My new open source operating stack consists of #almalinux , #debian, #linuxmint, #freebsd, and #openbsd. Each of these 4 operating systems have their distinct advantages and place. I love the #foss life.
@RL_Dane@XOrgFoundation I believe #OpenBSD uses their own xenodm fork now that @mherrb maintains - but while there is no one actively maintaining X.Org’s xdm now, the community is still merging patches and making releases, so it’s not abandoned like many of the other projects.
Yes, you're right -- OpenBSD's Xorg is a fork, or at least a patched version that implements some clever privilege separation takes advantage of some of their own cool security-related syscalls.
As you can see from the README and the diff that I gave to you, xe took the portable version, stripped out all of the bits that were conditionally compiled for anything other than Linux, substituted in Linux shadow password and PAM libraries, and added in the file-based timestamp mechanism from sudo.
Worse: This is the official #ArchLinux flavour of #doas. The portable one that didn't go back to sudo under the covers is relegated to the AUR.