simonmicro

Cough. Findroid. Cough.

Sure! Kube-vip is your go. Just use shared virtual ipv4 adresses.

Google for Sony Open Devices. AOSP, but running on Sony devices. While I prefer LOS, SODP is always the beginning to port it from.

Oh, it wasn’t just me!

Sorry, but I fear not. Ansible has a good getting started out there, but I think you’ll learn the most just using it.

Maybe a broad roadmap… Try to add systems. Test them via Ansible-Ping. Change some configs (add file, add line-in-file). Add handlers to react to changes by restarting services. Add host variables and customize behavior per host. Add templates…

I think it is a great way to document what you have done too. Especially with larger setups this can be quite time-intensive.

Then add that you may want to dynamically reconfigure your systems to interact with each other and then Ansibles template-rendering comes in really handy.

Finally, it is standardized - so other peopke can work with it too (relevant in work context).

Oh wow, I did not expect to ever get an answer - thank you, stranger! The design looks very similar to early Thinkpads, maybe I’ll get one of them (I assume better terminal use than on my smartphone).

Thanks!

Does someone know what this mini-thing in front of the cats is?

Run “sudo dmesg -w”, put it to sleep and then look what the kernel tells you why he could not sleep.

Most common issue would be something with your system memory. I could imagine that this caused the timeout of your cpu, which waited for the startup code, which never arrived.

In case you want to test that, swap your memory sticks around. Or tell the kernel to ignore that cpu (see command line arguments of the kernel).

Just use xca as a simple GUI - it can do it all.