8

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.

you are viewing a single comment's thread
view the rest of the comments
[-] HelloRoot@lemy.lol 2 points 4 days ago* (last edited 4 days ago)

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.

this post was submitted on 13 Apr 2026
8 points (100.0% liked)

Linux Questions

3879 readers
9 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

Tips for giving and receiving help

Any rule violations will result in disciplinary actions

founded 2 years ago
MODERATORS