Yeah, while it's always pretty great seeing people using and sharing our stuff, I'm usually a tiny bit wary of third-party documentation, because, by nature (third-party, not familiar with the code and possibly even how the device works) it usually doesn't quite grasp the hows and the whys, and thus can sometimes be confusing, not quite accurate, or just plain wrong
. (I'm of course assuming we're all decent human beings, and that credit is given where credit is due
).
To be fair, this one is pretty much almost not wrong at all, and when it is, it's usually a pretty minor nitpick, so, yeah, kudos, because I'm painfully aware of how hard it is to actually write good doc (which I very much don't claim to be able to do myself ^^)
.
So, a couple of corrections, in order of appearance:
* The first thing it should mention is that you should NOT be using a Special offers device (and point to the MYK page for those poor souls using one)
.
* The official update files aren't mirrored (for obvious reasons), even on ixtab's page, that's just a redirection to Amazon
.
* The rescue pack patches & enables access to the 'diags' system, it doesn't install/spawn an SSH daemon on the main system (that's USBNetwork's job).
* The Python package doesn't install a KUAL extension, that's the ScreenSavers package
.
* And right after the initial install is where I would recommend people to STOP, and check that it actually works before playing with the settings (that's actually an advice that you can apply to a lot of stuff, but I digress ;p).
* Once you've confirmed it does, THEN you can start playing with the settings, which I would *strongly* recommend to do through the KUAL extension, both because it's easier, and also because it takes the mutually exclusive stuff into account. (And if it doesn't work, to start by checking the FAQ I linked to earlier).
* Enabling multiple modes should not cause crashes, it just probably won't work as intended (there's a priority order, last || cover > everything). That said, not enabling multiple modes is a good practice, because, while it shouldn't cause real issues, I can't really guarantee it won't behave weirdly either
.
* The autoreboot mode is disabled by default on fresh installs in the latest releases, but if you're updating, disabling it is still a good advice
.
* The 'reboot' trigger file depends on the autoreboot mode being enabled, and it was indeed mostly useful for some Calibre plugins, although that was mostly on previous devices, on the K5, the only plugin that used this is jackie's plugin (can't remember the exact name OTOH, sorry) that put book covers in the screensavers pool, which is now of course superseded by the 'cover' mode
. [Hence why it was disabled for fresh installs in the latest version, that, plus KUAL, made the feature clunky & redundant]
* I won't mention the rest of the trigger files that tweak the cover mode behavior, because you should be using KUAL for that anyway, but there are quite a few (most notably the fitting modes, and the border color).
(I don't have an account on this website, so feel free to link to this post in their comments section
).