I’m an American who has been living abroad for 7ish years now. I often read comments from people who say they would do it “but the taxes are brutal.” Absolutely not the case. I dug deep into tax programs when I left and can comfortably say I am better off financially now than at any time I ever lived in the States… A major part of that is my tax strategy.
I love talking about this but most people don’t really care or realize how significantly it can change their lives… Eyes just tend to glaze over.
The NYT has had pro life op eds too… It’s important to understand where the other side’s dumb arguments come from so you can more easily defend against them.
For me, I try to follow a bunch of sources with differing views… PBS and NPR for mostly middle of the road American news. The Times for left leaning, WSJ and Bloomberg because it’s the closest thing to right leaning that isn’t batshit crazy. Al Jazeera, BBC, and the Japan Times for international news. A few Turkish and Georgian sources because it’s where I’ve been living for a couple years. Then just a lot of tech industry specific stuff because it’s my field.
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.
What worries me about the “systemd does everything as a tightly integrated package” is the too-big-to-fail aspect.
It’s been the default for ~10 years and it hasn’t been an issue yet… Even if it did “fail” the solution would never be to roll an entirely different init system. That would be absurd. If there is a bug, it gets patched.
I’d be worried that we’re seeing a lot of configurations that can’t be pulled apart piecemeal-- for example, if you need a feature not available in systemd
You can run services independently of systemd. There is no reason you couldn’t have whatever feature you want and systemd at the same time.
you need to deactivate a systemd component due to an unfixed vulnerability.
When vulnerabilities are discovered there is disclosure to maintainers, a patch is released, and then an announcement is made publicly with the instructions on how to fix the problem. I’ve never seen an instance where the industry collectively says “There’s a vulnerability here but we aren’t going to fix it. Good luck!” Especially for such an important layer of the stack… There’s no way that is going to happen.
Kube solves a ton of really complicated problems. I think a big part of the learning curve is just understanding what those problems are/were to know why we are all doing this in the first place.
Rolling out something like Talos is a good starting point for a sandbox to play around in. When I feel like you understand the basic ideas of things that can be run in kube (deployments, cronjobs, services, ingresses, etc) this is a really great resource to level up your understanding:
Standing up an enterprise level kube cluster is a 400-500k / year job
Ha! In what currency? Because it sure as hell isn’t dollars. Average senior level positions are in the high 100 to low 200k range.
Also, OP is talking about LFS… No one is going to ask them to do that shit either. All of this is a learning exercise. I didn’t say anything about an enterprise level anything. Standing up a cluster is a learning exercise.
Old school admin jobs are drying up extremely fast. The job market and a MASSIVE amount of development effort is going into the kube ecosystem. If you resist this change, you’re just going to fall behind.
Knowing this stuff is fine but make sure to keep your goals in mind. If the idea is to get a job, figuring out how Bluetooth works isn’t going to get you anywhere. You need to move in the direction the wider industry is moving. That direction is running containers in kubernetes.
If you can stand up a kube cluster, write a Prometheus exporter in go, scale pods based on those metrics, and auto resize workloads’ resource requests, then you should be able to find a job without much trouble… These are the things ops people are expected to do in 2023.
EDIT: The CNCF is a great resource for modern tooling.
The philosophical arguments are pretty garbage. I generally want to know if the “it violates the UNIX philosophy” people use browser extensions… That violates the UNIX philosophy too. Systemd “is backed by big corp” but who do you think is actually contributing time/effort/code to the Linux kernel? It’s the device manufacturers who are trying to get you to buy their products… So that fails too.
No offense to anyone reading this but if you’re really passionately anti-systemd, I would not hire you. This is a dumb hill to die on and a red flag.
I don’t own a car and rent whenever I need one. The car rental insurance with my card has been fine in my experience with the one exception being Salt Lake City. About a year ago I was there and they wouldn’t let me take a car unless I gave them a car insurance policy number to put into their computer. Despite being completely fine in the entire rest of the world, apparently Utah does not accept “I will use the insurance provided by my credit card” as a valid explanation… I was forced to buy the rental company’s crappy insurance that would have likely done more harm than good by buying it.
For read/write ops or disk usage over time, I would usually use a monitoring system like Prometheus and Grafana.
When you start talking about what specific files are accessed and when, that’s usually up to an intrusion detection system (or IDS). I don’t have good recommendations for that unfortunately.
Lots of the classics aren’t super space travel-y. Stranger in a Strange Land, Childhoods End, War of the Worlds, The Time Machine, Ender’s Game… Animorphs 😄
Yeah interesting idea. I can see it being useful for private enterprise implementations of gitlab to contribute to upstream projects… I don’t think it’s possible to fork a public github.com repo to a self hosted github enterprise instance but it’s been a while since I’ve run that and I don’t remember ever actually trying.
It might make tooling easier… I can see it being pretty easy to setup bi-directional comms with non-gitlab CI/CD pipelines doing this.
Really it might entirely eliminate the need for service accounts or whatever the gitlab equivalent of Github Apps is too which would be wonderful.