.˙ eepy · · · on Nostr: FIXED ARCH apparently device number is being fucking randomized every reboot (but ...
FIXED ARCH apparently device number is being fucking randomized every reboot (but only for NVMe drives
) and I tried to decrypt Windows because I stupidly believed that it didn't change number, so if I tried enough it had 50% chance of booting when it generated the number that point at the right drive. I changed it to UUID now so it never happens again but holy fuck people creating Linux are just the best at creating issues because idk just write good software for the love of god
Published at
2024-06-08 20:06:43Event JSON
{
"id": "c55f5851ff7a8aebc17e9d6b80a7c0d48a64430f49171c02dccc57640e71e24e",
"pubkey": "a6642c96f2c73dfe73c30f41562dec3ecc2147df7e8350c31e45ae5e527bb062",
"created_at": 1717877203,
"kind": 1,
"tags": [
[
"emoji",
"sbbook",
"https://bunnyanarchy.org/emoji/pony/sbbook.png"
],
[
"proxy",
"https://bunnyanarchy.org/objects/46520c00-e6d2-4eb8-87d2-e65a67a14127",
"activitypub"
]
],
"content": "FIXED ARCH apparently device number is being fucking randomized every reboot (but only for NVMe drives :sbbook:) and I tried to decrypt Windows because I stupidly believed that it didn't change number, so if I tried enough it had 50% chance of booting when it generated the number that point at the right drive. I changed it to UUID now so it never happens again but holy fuck people creating Linux are just the best at creating issues because idk just write good software for the love of god",
"sig": "43dfff4b097e9fd86b8992392b7361e060f066ace167b7e588dabc607ae819ba7dae6a95a0d472cfd2fb0c13194788addf2b3000e799becea7d925e005206135"
}