View Single Post
Old 06-05-2012, 03:33 PM   #279
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 7,052
Karma: 6359394
Join Date: Feb 2012
Device: Too many.
Ref:
The link (chain) -> download link page -> the second link under the "K5 (touch) links for de-bricking", shown here in part as:
u/29927061/mmcblk0p1-kt-5.1.0.img.tar.bz2

I found the following:
Code:
k510 $ find . -type f | wc -l
4954
k510 $ wc -l opt/factory/rootfs_md5_list
5609 opt/factory/rootfs_md5_list
Question:
Is this the expected "normal" condition for this image?
That is, to have 5,609 files listed in the rootfs_md5_list but only 4,954 actually present.

As in, maybe that list is from the lab126 development setup rather than the end-user image.
Note: There where no checksum errors uncompressing or unarchiving the image.

The only reason for this question is that I am looking for the "best" 5.1.0 system image file to use as a "development system base".
If this one is as complete as they come...
Well, then this is the one I will use.

Last edited by knc1; 06-05-2012 at 03:44 PM.
knc1 is offline   Reply With Quote