Comment 3 for bug 1010642

please excuse me for the my comment #2, I accidentally posted the comment.

I checked the packages in the hwpack and looks like there is only one vmlinuz as part of the linux-image-3.3.1-39-linaro-lt-omap*deb file.
So this confirms the problem seems to be coming from developer images. On checking the rootfs it shows that we have binary/boot/filesystem.dir/boot/vmlinuz-3.3.1-38-linaro-lt-omap
and binary/boot/filesystem.dir/vmlinuz in it. I believe that the vmlinuz is part of the hwpack and not something to be part of the rootfs and it presence seems to be bug introduced somehow.
On verifying the images logs on s.l.o it showed linux-image-3.3.1-38-linaro-lt-omap l-m-c throws an error as it is finding 2 vmlinuz one from hwpack and the other from rootfs (referring to log http://snapshots.linaro.org/precise/images/developer/181/linaro-precise-developer-20120611-181.build-log.txt).
I verified the nano and devloper images and the reference to the linux-image-* is in only the developer images. I guess this is a bug in live builder ?

Apart from this when verifying the build logs I noticied reference to exynos linux-image (http://snapshots.linaro.org/precise/images/developer/130/linaro-precise-developer-20120517-130.build-log.txt). This does not seem right either.

On the other note, should we check on improving the l-m-c to give a choice to the user on selecting the desired file?