this post was submitted on 24 Jul 2026
356 points (99.2% liked)
PC Gaming
15108 readers
228 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Does it follow me after Linux install?
Well, there is
/etc/machine-idon Linux...Just want to point out that
/etc/machine-idis unique to systemd systems. AlpineLinux, for example, doesn't generate this file on install.We tossed systemd out the window on our Debian. Stuff broke when we removed /etc/machine-id.
Turns out dbus ALSO uses it, but if it's not in /etc, it makes its own at /var/lib/dbus/machine-id (which was symlinked to /etc/machine-id on our system).
So we just wrote 00000000000000000000000000000000 to it instead. 🙃
-- Frost
What happens if you erase it though? System32 moment?
You can check the man pages for this file, but in short it gets regenerated. It's used to determine whether this is the first boot or not.
Honestly not sure. I wouldn't be surprised if it breaks something with D-Bus based on skimming the man pages, but I've never dug into it. Its not exposed in containers I run though, and I haven't run into anything that broke there as a result... 🤷️