Tools Snapshots of NiLuJe's hacks

[pghaworth]

Most excellent! Thank you!

[NiLuJe]

Public Service Announcement:

On Windows, make sure your unarchiving software isn't messing with line endings, because that will royally screw things up.
In particular, WinZip provides such a 'smart' setting, which may or may not be enabled by default. In any case: it's evil, kill it with fire.

[eschwartz]

Can we kill WinZip with fire?

Note to self -- I guess there is a reason why I prefer 7-Zip.

[GoSharks]

Originally Posted by NiLuJe

Public Service Announcement:

On Windows, make sure your unarchiving software isn't messing with line endings, because that will royally screw things up.
In particular, WinZip provides such a 'smart' setting, which may or may not be enabled by default. In any case: it's evil, kill it with fire.

Amen!!... (and NiLuJe is a very dedicated exorcist )

@NiLuJe: By the way, you have an interesting definition of "fun and interesting"...kind of like "eat'n people alive, where's that get fun?"

[NiLuJe]

Of particular attention to diags monkeys : I switched to a custom dropbear build in the Rescue Pack, w/ the same passwordless patches as in USBNet. It should also be using the same hostkeys as USBNet, and, provided the userstore isn't broken, handle your USBNet shared-keys setup. (But it is not the exact same build as USBNet, and as such doesn't absolutely require the userstore to be up to function).

(Also: ECDSA! Yaaaay.)

[pghaworth]

All of the KUAL files in the op were updated as of 12/1 except for KUAL. By design?

[NiLuJe]

@pghaworth: Yep, it's not part of the same code tree. I basically have three different packaging scripts, one for the K5 hacks, one for the Legacy hacks, and one for KUAL extensions. Only those three are (usually) always repackaged when I update the snapshots (that leaves KUAL & KindleTool alone). That doesn't necessarily means that stuff was changed, just that the packages were rebuilt. (Hence the detailed versioning: version tag, actual svn revision, packaging date/time).

[pghaworth]

Thanks.

[eschwartz]

I just tried to download one of these and got a Not Found error.

Excellent timing on your updates.

[NiLuJe]

Yup, container switches to ro during uploads, and I fixed a weird thingy during an upload, so it stayed ro a bit longer than anticipated .

[NiLuJe]

After nearly three years of downtime, I've just brought my good old (emphasis on old, it's the fairly old-school one-svn-repo-to-rule-them-all approach I've been using for nearly 10 years) Trac instance back up, for the more curious of you out there .

Do PM me if you encounter something wonky w/ it, like I said, been down for three years, I'm actually amazed that the upgrade went so relatively smooth .

[eschwartz]

Trying to access the barebones listing...

Unauthorized
This server could not verify that you are authorized to access the document you requested.

[NiLuJe]

@eschwartz: Yup, currently uploading updated packages .

[eschwartz]

Why is that always when I try checking...

[NiLuJe]

PSA: The latest snapshots introduced a rather important packaging change for legacy (K2/DX/K3) hacks: instead of being split in per-model packages, there's only one for the whole set of devices. That makes for less confusing and much, much smaller archives.

The downside is that only MRPI will be able to understand these packages.

If that's a deal-breaker, you can always repackage them yourself with KindleTool. For instance, given a package roughly named 'foo', and your target device being a WiFi K3:

kindletool convert update_foo.bin
kindletool create ota -d k3w update_foo_converted.tar.gz update_foo.bin

This new packaging layout is currently limited to the snapshots, but barring any uproar, that'll probably propagate to the next release packages too, because my time is much better spent doing interesting stuff rather than waiting for crap to finish uploading, and the legacy packages are rather beastly on that front .