linux/poky.git/scripts/lib/wic, branch uninative-2.1

wic/bootimg-efi.py: recognize initrd when using grub

2018-06-04T14:15:00+00:00

Make sure that we're able to use the initrd value specified in the wks file when using grub-efi bootloader with bootimg-efi wic plugin. Fixes [YOCTO #12689] (From OE-Core rev: f1d5bb1f21e11714357aff4ae7e52421e3756c5a) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

wic/engine.py: improve error message when required tools are missing

2018-06-04T14:15:00+00:00

Instead of showing that command 'None' was found, show the name of actual command that wasn't found on the host machine or at the native sysroot path provided by user. (From OE-Core rev: 3157ebb131e01e74689b1f87a35278350f315e7d) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

qemux86-directdisk.wks: remove uvesafb.mode_option

2018-06-04T14:15:00+00:00

Let this be dictated by the module parameter value being set by qemu machine configuration. (From OE-Core rev: c40b241e8d40c8bc1c9e6065b12e260662f5bba4) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

wic: Fix partition files UIDs on multi rootfs images

2018-05-22T12:13:32+00:00

When a wks makes reference to multiple rootfs, libspeudo data is not properly chossen. This results in filesystems with invalid UIDs for all the files. This can be tested with this .wks file: part / --source rootfs --fstype=ext4 --rootfs-dir=core-image-base part /mnt/data1/ --fstype=ext4 --source rootfs --rootfs-dir=core-image-minimal part /mnt/data2/ --fstype=ext4 --source rootfs --rootfs-dir=core-image-minimal And this script $bitbake core-image-minimal core-image-base syslinux $losetup --partscan --find --read-only --show test*direct $sudo mount /dev/loop0p1 /mnt $ls -lan /mnt otal 40 drwxr-xr-x 18 0 0 1024 May 11 16:11 . drwxr-xr-x 25 0 0 4096 May 6 06:31 .. drwxr-xr-x 2 1000 1000 3072 May 11 15:51 bin drwxr-xr-x 2 1000 1000 1024 May 11 13:59 boot drwxr-xr-x 2 1000 1000 1024 May 11 13:59 dev drwxr-xr-x 25 1000 1000 3072 May 11 15:51 etc drwxr-xr-x 3 1000 1000 1024 May 11 13:59 home drwxr-xr-x 6 1000 1000 3072 May 11 15:51 lib drwx------ 2 0 0 12288 May 11 16:11 lost+found drwxr-xr-x 2 1000 1000 1024 May 11 13:59 media drwxr-xr-x 3 1000 1000 1024 May 11 15:50 mnt drwxr-xr-x 2 1000 1000 1024 May 11 13:59 proc drwxr-xr-x 2 1000 1000 1024 May 11 15:51 run drwxr-xr-x 2 1000 1000 3072 May 11 15:51 sbin drwxr-xr-x 2 1000 1000 1024 May 11 13:59 sys drwxr-xr-t 2 1000 1000 1024 May 11 13:59 tmp drwxr-xr-x 10 1000 1000 1024 May 11 14:54 usr drwxr-xr-x 8 1000 1000 1024 May 11 14:55 var $sudo losetup -d /dev/loop0 (From OE-Core rev: 450335ba5e73a375eb9932b4c4cf37979640dbfc) Signed-off-by: Ricardo Ribalda Delgado Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

wic/imager/direct: Ensure correct ROOTFS_DIR is shown

2018-04-20T07:19:46+00:00

This changes the output of "wic create mkefidisk -e core-image-sato" from: The following build artifacts were used to create the image(s): ROOTFS_DIR: /media/build1/poky/build/tmp.wic.ybraavmb/rootfs_copy to: The following build artifacts were used to create the image(s): ROOTFS_DIR: /media/build1/poky/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r0/rootfs which s much less confusing for the user. [YOCTO #12564] (From OE-Core rev: a4941af2d3624aecc5dcd7ff54b7ea8c9e9dee8b) Signed-off-by: Richard Purdie

wic: add wks file to make use of exclude-path functionality

2018-03-06T14:35:42+00:00

Using --exclude-path and a wks.in file we can create an image that takes the /boot/ directory for the boot partition, has an empty /boot/ directory in the rootfs partition. The boot partition gets mounted to /boot/ after startup. (From OE-Core rev: db904053e8ee80fb6930c5e7e22287927e0f25e2) Signed-off-by: California Sullivan Signed-off-by: Richard Purdie

wic: Set a miniumum FAT16 volume size.

2018-03-04T11:35:40+00:00

Set a miniumum FAT16 volume size because images are not valid to parted if this minimum value is not respected. The value set is determined experimentally forr a logical sector size of 512. This fixed my local problem but, there may be better solutions. (From OE-Core rev: f7dfb4d43247d3c13a4e0a3853007d63b9512b83) Signed-off-by: Paulo Neves Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

wic: partition plugin wrongly assumes it is rootfs

2018-03-04T11:35:40+00:00

The partition plugin is used as the base for other plugins. One of the methods the plugins use, is the prepare_rootfs method. The prepare_rootfs method wrongly assumes that the value ROOTFS_SIZE from bitbake datastore is relevant to every invocation of prepare_rootfs, which it clearly is not, for example in the bootimg-partition case. This commit adds an optional argument to prepare_rootfs where a caller can tell prepare_rootfs if it is an actual rootfs and whether related rootfs information retrieved from bitbake is valid. The default behavior of this optional argument is to assume that the invocation is an actual rootfs, to maintain compatibility with previous implementations. (From OE-Core rev: 654d72d55194ec41bc1aacfcc6b2c8c9a305b042) Signed-off-by: Paulo Neves Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

wic: Add post operation hook for SourcePlugin

2018-03-04T11:35:40+00:00

do_post_partition hook is needed if some operations like security signing the parition needs to be done. source plugins can make use of this to implement post operatiosn in do_post_partition. do_post_partition is called after do_prepare_partition if present. (From OE-Core rev: 5055489b9ab3fda32a285d0d165d080d11a4d432) Signed-off-by: Parthiban Nallathambi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

wic: if we can't get from ioctl, try from os.stat()

2018-01-14T09:11:57+00:00

Under some conditions, ioctl FIGETBSZ can't return real value. We can try to use fallback via os.stat() to get block size. Source of patch: https://github.com/intel/bmap-tools/commit/17365f4fe9089df7ee9800a2a0ced177ec4798a4 (From OE-Core rev: d8f7cf2d38934c248be91101236f7537d0d31ea7) Signed-off-by: Dogukan Ergun Signed-off-by: Ross Burton Signed-off-by: Richard Purdie