Have you heard about Tor?

Maybe I’m just old, but I thought a distribution is literally just a package delivery basically, just like you speculated. Making software work together nicely is actually already hard enough IMO. I don’t think anything is wrong. Valid question though

How do you sell what you did as “it just worked”? Rightaway? You lied to them. You have your coworkers on an unmanaged machine with a foreign OS on the guest WiFi with custom networking. Don’t oversell a workaround as a solution.

Simplifying the problem to “Windows” seems unfair, given how many problems you found. All of them still require a long-term solution for regular operation.

I wasn’t actively aware of this for most of my life until I recently visited a clients office. Buying someone a cup of coffee is an entire thing. There’s no free coffee. You have to purchase every single cup. And you first have to walk several minutes to the place where they sell the coffee. It blew my mind. I’m used to drinking one cup after the other without even giving it any thought. Coffee machine right next to me or around the corner. There, coffee incurs friction and cost.

So when you invite someone for a cup of free coffee, this can open doors for you. I’m not kidding. People get all excited when you offer them a coffee break on your dime. And there’s levels to it too. There’s the regular coffee, and there’s the premium one. For the premium you have to walk longer and wait in line until the barista serves you.

It’s a key component in office politics when coffee access is regulated.

Why anyone would restrict access to legal stimulants in the office is unclear to me though. Put espresso machines on every desk!

So you fucked everyone because of a beef you had with AWS. Go fuck yourselves. Moving people off Elastic products is the right move either way. Don’t look back.

I feel like the time to hide information behind YouTube links is over. Feels like a link to a paywall article at this point.

5 nines imply a downtime of 6 minutes a year, or every 100,000th operation failing. That’s not great for a file system. I assume you picked the number arbitrarily, but still think about it.

And has been for so long, they already went through it once

Numbers give the wrong impression that one version follows another. Debian release channels exit alongside each other individually. Giving the release channels names helps to make that distinction. It also makes for an easy layout of packages in APT repositories.

Sid is and always has been Sid. If you were to assign numbers, what number should replace that name? There are perfectly working labels for release channels and there is no reasonable replacement.

To add to that for clarity: With the original Mono, you could run a regular Windows .net application on non-Windows without any additional work (with limitations, as native Windows API calls were unsupported). With the modern dotnet, you can compile new applications from source that will run anywhere

Messing with the computer is pretty important though

I remember this mindset in myself. Today I consider it a waste of time.

If you rely on any tool for this, the tool will make mistakes you cannot accept. If you do it manually, you will make mistakes as well and that also does not work. Also, the information your consider worthy for removal might be key to understanding the problem.

Like, you remove your name, but a certain character in your name is what is actually tripping up the program.

Ultimately, don’t post your logs publicly. In the past years, I was always able to email logs to devs. I have no reason not to trust them with my log. If they want data from me, they could easily exfiltrate it through their actual application.

If you are already familiar with one package manager, pick a distro that also uses that package manager.

When deciding on the release track, the harder it is to recover the system, the more stable the track should be. Stable does not imply secure.

As you move up through virtualization layers, the less stable the track needs to be, allowing access to more recent features.

Steer clear of distros that pride themselves on using musl. It’s historically slow and incomplete. Don’t buy into the marketing.

Think about IaC. Remote management is a lot more comfortable if you can consider your server ephemeral. You’ll appreciate the work on the day you need to upgrade to a new major release of the distro.

https://verwaltung.bund.de/leistungsverzeichnis/en/leistung/99400208017000

Before Google Drive and Syncthing I relied on such a USB device. Today, no matter what I put on the stick, it’s outdated or entirely not what I need when I need something.

Having any stick on hand, and being able to flash an image from your phone, that’s nice

Are you aware of Nvidia recently releasing different versions of their kernel modules? There’s an open-source and a proprietary flavor. Make sure you have the right one selected for your hardware and fallback to nuvoueau if need be.

Double-check that your APT sources are exactly what you expect them to be.

Clean your APT cache. Then update it.

Try to fix broken packages again with apt install.

If the problem persists, look at every single package mentioned in the error. Go to the Debian packages website and look up what the current version for your release is. If there are any mismatches, try to resolve them by uninstalling these packages until apt install completes without error again. Make sure to reinstall the right version of your packages again.

Given your other comments about manipulating post installation scripts for some time, if the above doesn’t work for you, consider backing up your data and reinstalling a fresh setup.

Only freaks have AM/PM in their time system.

You can read this blog post, authored as a series of tweets instead https://mastodon.social/@pid_eins/112353324518585654