View Single Post
Old 12-11-2023, 05:35 PM   #10
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Quote:
Originally Posted by mergen3107 View Post
Ultimately, I can just nuke the "factory_reset" binary (by replacing it with a /dev/null link), but it sits in /bin/ , and I am hesitant to touch it (in contrast to logging things, that sit in /usr/bin/ and /usr/sbin).
Welcome to the future: https://www.freedesktop.org/wiki/Sof...orTheUsrMerge/

Fun Linux bikeshedding aside, I agree with @Quoth, don't? ;p

You can probably achieve a saner recovery path in case of brainfart by forcing a reboot and killing the passcode over SSH or something (which is trivial, as you're probably aware, c.f., KOReader's startup script), as I would hope the pin lock doesn't inhibit hard reboots?
NiLuJe is offline   Reply With Quote