Pretty sure it is called The Talos Principle but glad you found this gem!
Pretty sure it is called The Talos Principle but glad you found this gem!
My go-to solution is to use a vm and pass it raw access to the os disk on my normal desktop. Then I just put the disk into the server.
I never understood why everyone uses it as a ignore list. In my own and work repositories I always exclude everything by default and re-add stuff explicitly. I have had enough random crap checked in in the past by coworkers. Granted, the whole source folder is fully included but that has never been a problem.
Man, I always found that weird but never looked it up…
And I thought that “8” had something to do with “netes” because it somewhat resembles the pronunciation 🤦♂️
Yeah, if you get this exception and not doing anything not-“normal” then the chance is high that there are multiple versions of the same class. A possible way to trigger this is when extracting code to a separate module without changing the package. If you copy instead of move and change something you will have a bad time. It is also possible that the IDE complains but building and executing works.
Fun times!
First time I read in windows update “we are commited to reduce co2 emissions” I was like “wtf”.
Appimage might also be a way
I have never seen an implementation of e.g. a mirror that gives up on disagreements of both disks. Repairing/redundnancy is what raid is there for.
Edit: maybe old hardware raid does not check?
I started using it on my NAS and also on root. Then I switched my personal machine to ZFS on root. I manually created both setups (somehow). This is the worst part in my opinion. The best decision, though, was to ditch grub in favor of zfsbootmenu. Skips all the brittle steps with grub and its boot partition. Now I just have zfsbootmenu directly loaded by UEFI from the EFI partition. Everything important is directly on ZFS, including… well, everything. Can also use snapshots but I have not needed that yet.