Thurstylark

Finally time to update manjarno.snorlax.sh again -_-

Oh my god, thank you so much for this. I have always had the hardest time finding these exact same requirements, and this is perfect. All metal construction and coexisting with keys has always been a priority for me, but it seems like everyone is inexplicably fine with copping out by just dangling their data on this flimsy little string tied to a brittle plastic case and I cannot understand it.

I’m not currently looking for one at this exact moment, but I will be returning here when I am. You’re doing the lord’s work out here!

There is a title he currently holds, and which deserves a higher rank by mere exclusivity’s sake…

Impeached Former President

I agree that if there was enough space in the recovery partition to begin with, this wouldn’t be a problem, but the user isn’t the party that specified that size or the party that decided to add enough stuff to the recovery partition to exceed that spec.

MS knows that this is a widely-deployed configuration (they deployed it), but they’re going ahead with an automatic update that is incompatible with that configuration anyway, failing to communicate to the user why the failure occurred, and refusing to automate a fix to the thing their automation broke in the first place.

Waow. MS can’t decide if their users should have control of their hardware or not.

Your linux bootloader and efi config? That belongs to Windows, and it will make changes as much as it wants. A recovery partition that has no usefulness outside their own ecosystem? Yeah, they know it’s fucked, and they fucked it, but it’s your computer, you fix it!