Why? We already have a nix source of truth for fileSystems, mainly in hardware-configuration.nix on all hosts, why complicate drive setup and add traps to an existing and working declarative…
We use pkgsync, so putting it in maynothave should remove the package from all salted hosts
Or, perhaps at least document it, in case it was set this way for a good reason that we just forgot 😅
It is important to read the debian release notes for the new (and any intermediate) releases. E.g. https://www.debian.org/releases/stable/release-notes/issues.en.html#dovecot-configuration-changes…
Correction: When? Yesteryear!
From previous discussions, I think we have pretty much landed on:
- Use 3.5" drives. Servers/Chassis with 2.5" might be easier to source, but the disks are…
However, having your own .bash_history to not get other peoples histories messing up your autocomplete is cool, but you can implement that yourself without the need for this system everywhere
Logging who did what might be cool, but I think we should coordinate it with Drift/issues#138, and use something like auditd rather than a hacky script setting…
Some hosts, especially Microbel, needs a bit of fiddling with the cert files to work, so we should probably write a shell script that implements the procedure at https://wiki.pvv.ntnu.no/wiki/Drift…