[OE-core] The different behavior of images built with different PACKAGE_CLASSES

[Luo Zhenhua]

Hello all, 

I use the same Yocto build environment to generated two sets of images, one is built by setting PACKAGE_CLASSES to "package_rpm", the other is built by setting PACKAGE_CLASSES to "package_deb". 

With the same uImage and dtb, the board can be boot up normally with rootfs image which is built by package_rpm setting, but can't be boot up with rootfs that is built with package_deb setting, it will hang with the following boot logs:
RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 180K (804a6000 - 804d3000)
Bad inittab entry at line 5
can't open /dev/si: No such file or directory
can't open /dev/~~: No such file or directory
can't open /dev/l0: No such file or directory
can't open /dev/l1: No such file or directory
can't open /dev/l2: No such file or directory
can't open /dev/l3: No such file or directory
can't open /dev/l4: No such file or directory
can't open /dev/l5: No such file or directory
can't open /dev/l6: No such file or directory
can't open /dev/z6: No such file or directory
can't open /dev/S0: No such file or directory
can't open /dev/S1: No such file or directory

Does somebody meet the same issue previously? Can you please suggest on what's the reason and how to solve the issue? 

I am using daisy branch and FSL ls1021atwr(armv7) board. 


Best Regards,

Zhenhua