MobileRead Forums - View Single Post

knc1 · 06-17-2012, 08:55 AM

@GM and anyone else with useful input.

Should we (the MobileRead web-site members, not just You and I)...

Be packaging these images and matching kernels as compressed archives (both kernel and image in the same archive)?

Any of the common multi-file archive should do the job:

*.tar.gz (a.k.a: *.tgz)
*.zip
*.7z

There are Linux/MacOSx/Windows utilities to handle them all.

As GM has pointed out in other posts, it is rare that the kernel needs to be re-installed, but it is so small a file that it is a "good practice" to replace it when re-installing a system image.

This seems to be the major remaining problem with Kindle Recovery. Not having "matched pairs" of kernel and system image files.

One other possibility -
My K3-v3.2.1 system image has an:
/etc/version.txt
file in the system image.

The content looks like this:

Code:

System Software Version: 015-S2-057629
Sat Apr 16 20:18:46 PDT 2011

That might be enough information that a "pair testing" script could be devised.
Hmm... Would have to lookup where in the kernel image the build info string is at so it could be pulled out with od for comparison.

Comments? Discussion?

06-17-2012, 08:55 AM	#1
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Recovery Binaries @GM and anyone else with useful input. Should we (the MobileRead web-site members, not just You and I)... Be packaging these images and matching kernels as compressed archives (both kernel and image in the same archive)? Any of the common multi-file archive should do the job: .tar.gz (a.k.a: .tgz) .zip .7z There are Linux/MacOSx/Windows utilities to handle them all. As GM has pointed out in other posts, it is rare that the kernel needs to be re-installed, but it is so small a file that it is a "good practice" to replace it when re-installing a system image. This seems to be the major remaining problem with Kindle Recovery. Not having "matched pairs" of kernel and system image files. One other possibility - My K3-v3.2.1 system image has an: /etc/version.txt file in the system image. The content looks like this: Code: System Software Version: 015-S2-057629 Sat Apr 16 20:18:46 PDT 2011 That might be enough information that a "pair testing" script could be devised. Hmm... Would have to lookup where in the kernel image the build info string is at so it could be pulled out with od for comparison. Comments? Discussion?