I've been researching information about /etc/machine-id, a file that contains an ever-persistent machine ID that identifies the install across hardware or netwotk changes, and that is world-readable.
Most documentation I've seen says it is mostly safe to change this file and generate a new ID on shutdown, and there are example scripts to do it via eg.: systemd or rc.shutdown . That's nice, but... we're on Linux, we don't "shutdown" our machines, what do they think we are, Windows users? We don't shutdown at least intentionally.
So, I was wondering, is it feasible to regenerate this ID on hibernate? It's another instance where the machine powers down, there are ACPI hooks to run scripts on hibernate/wakeup, and I feel at least for a laptop it's a more common use case than a shutdown.
Omg absolutely separate from the purpose of this thread, but would you happen to have copies of such scripts or could you recommend some tutorials on KDE activities? I usually prefer lean DEs, but every once in a while KDE makes it so difficult for me to say no to them.
Really thank you for sharing your insight and experience on this.
Here you go:
Everything should be documented there
https://git.sr.ht/~deckweiss/x11_activity_session
It probably can be adopted to wayland (or even native kde tiling) with a bit of tinkering.
I'm instacloning this. I get from the files and from previous experience with KDE that it can be done, I just haven't gotten enough tinkering experience outside of the classics such as wmctrl to do that yet.
KDE activities don't get much dev love, so be warned.
The activity script hooks are (or were for a long time, idk how it is now) an undocumented feature.
I'll dig all the stuff out for you later today.