OpenBSD admin and ports maintainer
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]
Snarky answer: PC
Slightly less snarky answer: Steam Deck
Can’t argue with that, I was ADHD skimming. I will now curl up in ball in the corner and die of embarassment and cringe :(
Did you check the hyperlink? Because it is !techtakes@awful.systems levels of stupid. I can’t read
Specifically “Sam Altman or Elon Musk about the “existential risk” artificial general intelligence poses to humanity” which contains a hyperlink leading to an independent article titled “Elon Musk says AI one of the ‘biggest threats’ to humanity”, and is just as much unholy brainrot as one might expect.
Yeah I’ve used jmp.chat before, but I couldn’t get any of the clients to work well with my pinephone’s microphone. Shame, since it’s the closest you’re going to get to VoIP on the thing.
Hello, I have downvoted your post!
Reasons include:
The doomsday argument is correct, and becomes more obviously correct with each passing day.
Never thought I’d find another IRC and XMPP fan on lemmy. Let’s replace SSM/MMS/RCS with XMPP while we’re at it.
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/Matrix 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).
skibidi toilet
Worth noting this only affects the portable release of OpenSSH, so OpenBSD (or anyone else using the native release) are unaffected.
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.