It's easier to think about Linux on the context of what an individual application needs to run. Pretty much everything you do will have these components.

• configuration
• an executable
• a communication mechanism (dbus, networking, web server, etc)
• something that decides if the application runs or not (systemd, monit, docker/docker compose, kubernetes scheduler, or you as the user)
• a way of accepting input (keyboard and mouse, web requests, database queries, etc)
• a way of delivering an output (logging to unique log files, through syslog, or to stdout/stderr, showing something on a screen, playing a sound, returning a message to the client, etc)
• storage (optional)
• some cpu and memory capacity

That's really it. If something isn't working, it's pretty much exclusively going to fall into one of those categories. What that means is going to vary significantly from app to app but understanding this is how literally everything works makes the troubleshooting process a lot easier.

I got a galaxy watch thinking I'd do all these cool things with it. Ultimately I only used it to set alarms to let me know my tea is ready..

I only really use the mechanical watch now.

It's fucking stupid to do it all at once but I think this should have happened ~5 years ago. Raising interest rates are how you fight inflation.. We wouldn't be in a situation where it costs 500 TL for one sucuk if they started doing this well before covid.

Can't speak for most of these places but I'm pretty doubtful in general.

I have no idea what it means for VPNs to be restricted in Turkey for example.. I use them almost every day. Personal, self hosted, commercial, corporate... Both using them while I'm in Turkey to get information from the outside and when I'm outside trying to get information from the inside.

I've never had any issue using them. Like literally ever.

Yeah I am deep in the kube world as well. Since this industry-wide shift started happening, I feel like I write essentially no code anymore outside of bash scripts to glue things together. It's essential but it's not a replacement.

This cartoon seemed to me to be suggesting that you could implement the behavior of kube with bash. That's obviously absurd.

We had a service that compiles a dataset once per quarter. The total size is ~30gb. We were starting a container, storing it on an EFS volume, and mounting like any other disk.

Every time a pod started it would need to read this data into memory so we would get quick initial start-up time but the time to be ready for traffic still took a while.

Since we didn't need to update it very often, we decided to just package the compiled dataset into the container and skip the EFS volume. We updated the image pull policy to ifNotPresent so it cut egress traffic pricing from EFS to zero. Now there is a cost to pull the image from ECR but that's only if the pod is being scheduled onto a node it hasn't been run on before. There was no noticable change in behavior or performance and we saved a bunch on cost.

Sometimes the big, dumb option is the right choice.

NPRs top 100 scifi and fantasy books.

https://imgur.com/a/zHxdYSF

If you're in America..

https://www.market.unicefusa.org/

But I guess a good question is, why do you want multiple OSs?

Agreed. Is it cool you can do this? Sure.. why not. Is it valuable/useful in any way? No.

I'm an old grey beard at this point though.. The days of being interested in the latest OS or distro hopping are long loooong behind me.

I still can’t believe voters didn’t give him the boot.

That was the Trump-era midterms IIRC.. He's there now because he has a D next to his name. That's about it.

https://lemm.ee/comment/3057321

Yep. IO.

OP, this might be overkill for you but it might be worth standing up a grafana/prometheus stack.. You'd be able to see this stuff a lot faster and potentially narrow in on a root cause.