Quote:
Originally Posted by geekmaster
Okay, I will examine the header in more detail. It started as a quick "one-liner" hack that served its purpose at the time, but more work is required these days.
|
Nope, it still works just as written.
It **never** passed the mkimage verify command.
And it does not matter the way it is being used, both then and now.
= = = =
Note:
It **might** break at any time in the future without notice.
The mkimage format is recursive -
Each mkimage file (segment) might contain additional mkimage segments, each with their own header.
Amazon was not using that feature when I made the checks at the time of my posting.
But they could, and should -
that is how you pass the kernel binary image, the initramfs, the device table, the initial environment - all as individual mkimage segments, wrapped inside a single mkimage file.
And if they go much new than the 3.0 kernel - they will have to.
