|
Don't be a gatekeeper. Every guide on modding a Kindle starts with warnings about the risk of bricking the device. We're adults - I get it, I've been warned. If I brick it, then ¯_(ツ)_/¯ - it's not the end of the world.
> On KOReader side, if say KOReader crashes on startup, and it is part of upstart, the upstart will not be happy and send you to a restart. That means it will be in a loop, so that’s probably why I haven’t seen it done yet
If I do the following:
- Place the true startup script in userland - in a directory accessible via USB.
- Place a script that simply triggers that userland script in /etc/upstart.
Then a boot loop isn't that risky. If it happens, I can replace the userland script with a dummy bash echo script, and I'll escape the boot loop.
> What’s the main reason you would like to have KOReader start on boot anyway?
What's the reason people who mod consoles want the modded dashboard to start without any additional interaction? What's the reason people set up useless screensavers or other irrelevant modding stuff?
One reason is improving UX; another reason is pure curiosity or "just because." I believe many people in the modding scene do things just for the sake of doing them - just to prove that something perceived as undoable is actually doable.
|