![](https://lemmy.sdf.org/pictrs/image/ee22644c-7bce-415f-a9bd-eab6a79ac074.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Yes, and not even the modern fvwm3, due to licensing issues.
OpenBSD admin and ports maintainer
Yes, and not even the modern fvwm3, due to licensing issues.
Definitely OpenBSD’s default fvwm
Because the only redeeming quality of Windows is the fact a lot of software works on Windows and only on Windows, which is also exactly the problem with Windows. It’s great WINE can exist, but not all platforms support WINE, and as an OpenBSD user first and foremost it means I can’t play many of my favorite games on my preferred platform.
Ultimately, Windows sucks and is a standard because our society puts corporate greed and thieves like Microsoft above superior projects; and even if Microsoft were firebombed off the planet tomorrow, they’re just a symptom of the problem, and it’s only be so long until another thief steps into Microsoft’s position and ruins everything again.
Removed by mod
Removed by mod
well diskletters/numbers can change between boots and hardware configurations, and unless you have a good label for the partition, this is the only way I can think of to name your permanent mount points that isn’t problematic/incorrect in some other way. This will always work correctly with any amount of partitions with any amount of disks; and it’s not exactly hard to get the DUID of a disk, at least on OpenBSD. It’s also highly scriptable as such.
I’m an OpenBSD user, but it shouldn’t be hard to translate this to Linux:
If the partition I want to mount is /dev/sd0i
, and sd0’s UID/DUID is 3c6905d2260afe09
, I mount /dev/sd0i
at /3c6905d2260afe09.i
. fstab entry looks like
3c6905d2260afe09.i /3c6905d2260afe09.i ffs rw,whatever_flags 0 0
/[UUID or PART-UUID].[partition number/letter]
Agreed, and in addition, I hate the web interface dependency for github and gitlab, and how many system resources they use (can’t even load gitlab on my pinephone without it crashing due to running out of memory!). At least gitlab can hypothetically have a minimal open source client. I’d much rather just communicate with developers through mailing lists. If hosting is hard, there are providers for lists.
I think there’s nuance to this. Of course there are asshats like MongoDB that pull the rug and enshittify; but on the other hand licenses are a tool, not an ideology. If fucking over corporations involve a more restrictive non-commercial license that isn’t open source, that’s a good thing in my eyes. It depends on the software being written and how it’s being used.
Fuck Discord, all my homies hate Discord; use IRC/XMPP/SMTP instead.
I’m not gatekeeping anything, I only care if your patches for my ports are good.
FSF feels like a cult, they care more about the purity of foss than its practical effects on the world; and their specific implementation of foss (copyleft). This goes back to licensing and how there’s more nuance in licensing than if it’s open source or not.
If IBM makes redhat do something that greedy and stupid (it’d be more likely to happen with a distribution like fedora or centos than userland components), we have plenty of existing infrastructure to fall back on.
And neither Arch, nor Ubuntu, nor Debian, nor OpenSUSE, nor any other distro using systemd belongs to IBM.
Where did I say they belong to IBM?
Sure, the centralization is pretty damn bad. But for example replacing sudo is needed.
We already have doas, which is such a simple codebase I’d have a hard time imagining it contains a bug that leads to setuid being a problem. run0’s codebase size on the other hand…
Arch ships redhat userland (systemd) and doesn’t support alternative userlands; you have to go to artix for that.
Nah, I’m just referring to IBM’s acquisition of redhat. I’ve been referring to redhat as IBM in kind.
No, it’ll just be yet another pile of bloat that’ll separate IBM distros and their followers (rhel, fedora, centos, debian, arch) from the rest (alpine, void, gentoo, devuan, *BSD).
Worth noting this only affects the portable release of OpenSSH, so OpenBSD (or anyone else using the native release) are unaffected.
Your ability to ride the fence is admirable OP, don’t let anyone take it from you 🙏
It’s as easy as following any set of instructions. Whether or not you actually understand what the instructions are doing is an entirely different story. If you actually want to learn how to operate a posix system, doing a bunch of command line installs of Linux isn’t going to help you with that. What will help is living in something with excellent documentation like OpenBSD, with minimal reliance on external tooling. Once you have the skills, they’ll transfer anywhere.
If you’re going to give GNOME shit, at least let it before how much they destroy portability of GTK, enabling cancer like Client Side Decorations, and ignoring their community when it comes to things like desktop icons.
For destructive commands I much prefer find / -type f -exec mv {} /blackhole \;
For something with that little memory, I would use a minimal window manager; you’ll want every megabyte of memory if you want to have any chance at running something like a javascript-capable browser without constantly hammering swap. fvwm, cwm, jwm, and ratpoison are all small window managers I enjoy; but do your own research into what window manager is the best for you.