A+. Would live again.

Someone call the ICC. This is a crime against humanity.

It is possible to build trains/stations in lightly populated areas and have modern building codes in place to encourage modern, efficient towns be developed around them.

China took it to an extreme in one situation but it's entirely possible on smaller scales.

Kina Granis - In Your Arms

It's all stop motion with jelly beans.

Here is the making of it.

A project that allows a full installed-in-place Linux installation with grub and all, no USB drive required.

This could be possible today. A combination of PXE booting and FAI would be enough. I think you'd just need to work out a way for PXE to work over the public Internet. Otherwise you'd need to have the image downloaded already and have it available via web server to be accessible from the booting machine. Years ago I used iPXE and it was really nice. Haven't used it in a loooong time.

Also, Talos is doing some really interesting install processes as well. Basically you boot a small (~80mb) image, it exposes a network port, and you send it a machine configuration manifest. It all runs in memory until the configuration instructions are sent, then it installs. There isn't even an option to install it locally because local auth is not allowed and ssh is not included. You must do it over the network. Talos is all kubernetes so might not be what you're looking for but it's an interesting approach.

I'd imagine it's a reclassification of symptoms so that treatments can be better targeted.. Not because it hurts someone's feelings.. That's dumb.

Trello, Google Calendar, Notion, Evernote, Proton Calendar, etc, etc..

If you want to really DIY it, and depending on the things you want to be notified of, the Pushbullet API is pretty decent. I have been using that for years. You could probably do something with IFTTT or Zapier or something similar too.. I haven't dug into those.

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:

https://github.com/kelseyhightower/kubernetes-the-hard-way

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.

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.

Yeah for this situation, versioned APIs are the answer. If, for example, you look at the kubernetes ecosystem, the entire thing is based on APIs and every resource starts by specifying an api version on the very first line.

apiVersion: v1
kind: Namespace 
metadata: 
    name: example-namespace

This is how they can make upstream changes and not break existing environments in the process.

They would need to build an office within a ten minute walk from my home.