Don’t you mean buttbuttinate?

It’s replacing all instances of arse and ass with bottom…but doing so in about the most naïve way possible.

Not sure what proxmox has to do with this? All this is doing is allowing VMware workstation to run without out of tree modules, it means nothing for anyone else

Fact of the matter is RSA is perfectly secure still…and ECDSA/ED25519 should also be extinct given the rising need for post quantum cryptography

Did he actually use proton to run a native game… that’s just silly

I do whenever there is a vulnerability of note. I don’t do it on a regular basis though.

Just checked, I’m at 311 on my main server

According to the article they did allow it. They got rid of that clause in a license update, just didn’t allow you to modify your fork lol

This meme must be old as Java 9 added jmods

…that’s…a good question 🤔

If you can’t change your default shell that’s not really a lesson you should have to learn. You should be able to set your own default shell and this is coming from someone who’s shell preference is bash.

Huh, yeah I suppose that’s true. Qubes is an interesting project but I’m not sure it’s for me. I selectively isolate apps I worry about using containers, I actually should give flatpak a try as it basically does that for me but I haven’t seriously tried it yet.

The pedant in me dictates I must say you probably mean UEFI and not BIOS

Ollama is also a cool way of running multiple models locally

Maybe it’s just been good luck, or maybe I pay enough attention to what apt is going to do and know how to deal with it but I’ve been daily driving sid for years and am convinced it’s more stable than arch based on friends I have that run arch…maybe it’s just I’m more experienced but it really doesn’t break that much. Obviously ymmv.

How are fedora or SUSE valid alternatives “from the same repos”? They’re not even based on Debian or Debian repos?

Eh? Idk if I agree. My original comment was entirely a joke based on the fact that the literal argument of=/dev/sda has no affect on my system but to address your actual point. I personally don’t find nvme naming any more confusing than SCSI. /dev/nvme0n1 is only one char away from /dev/nvme1n1 just like sda vs sdb. Additionally if you understand how the kernel comes up with those names they make a lot of sense. The first number is the controller, the second is the namespace or drive attached to that controller, the 3rd if present is the partition on the given drive. It is entirely possible to have a controller with more than one namespace. That aside aside…I think there is a genuine benefit to be argued for having USB drives, which are SCSI and fall into sdX naming separate from system drives as I dd far more USB media than system media. Making it a lot harder to screw my system up when trying to poke a flash drive.

I am immune to /dev/sda for I only have nvme

I’m both IT and development…and I’ve caught both sides being utterly wrong because they’re only familiar with one and not the other

Me when this post has led me to find cute anime girl communities lol. I respect the decision to do it…but I’ll be subscribing to some of these