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

wic/engine: use up all free space when expanding partitions

2018-07-18T09:18:42+00:00

Currently we just divide up the free space by the number of partitions that need to be re-sized. This leads to problems when a user has explicitly specified a subset of partitions (but not all) that need to re-sized along with the sizes. As an example, for an image with 3 partitions, if we use: wic write image.wic /dev/sdb --expand 1:10G This would lead to paritions 2 and 3 each being re-sized to one thirds of the free space instead of half. Change the behavior to use up all the free space. (From OE-Core rev: a88f1b5d88dbc5fb28be24b9787d73b9e0cdf183) Signed-off-by: Anuj Mittal Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

wic/engine: fix errors when expanding partitions

2018-07-18T09:18:42+00:00

The UEFI spec implies that GPT partitions should be assumed to be on a 2048 sector boundary (for a 512 byte sector) and the current logic just divides the free sectors available by the number of partitions that need re-sizing, which may or may not align and the final result might overshoot the limits imposed after alignment. Since we are expanding already aligned partitions, just divide up the free space in multiples of 2048. Also use the exec_cmd wrapper instead of the subprocess call directly. Fixes [YOCTO #12840] (From OE-Core rev: 5eef63f5afdfbab8e30748cb1bf42bf2e6524759) Signed-off-by: Anuj Mittal Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

wic: isoimage-isohybrid: debloat image of redundant rootfs

2018-06-29T10:07:45+00:00

There's no reason to have that rootfs.img filesystem in the image: it's not used for anything because both the EFI and legacy boot paths use the /initrd which contains the same contents as the rootfs.img, only compressed. It was probably forgotten in there :) My iso went down from 224 to 94 mb. Tested using UEFI/legacy boots on CD-roms, usb dongle and qemu VM's. (From OE-Core rev: 4c784379524cb12807ef87a02ef1514ed45c1cc3) Signed-off-by: Ioan-Adrian Ratiu Signed-off-by: Richard Purdie

wic: isoimage-isohybrid: fix UEFI spec breakage

2018-06-29T10:07:44+00:00

It's really good that OE supports multiple EFI_PROVIDERs and that commit 9a1709278de87 ("wic: isoimage-isohybrid: use grub-efi from deploy dir") makes re-use of the grub-efi built image, but we should still respect the standard otherwise the ISO will not boot, so install grub images as boot[x64|ia32].efi not ${PN}-boot[x64|ia32].efi. (From OE-Core rev: 1608129692d92c239b5fb9244b649a32b9009254) Signed-off-by: Ioan-Adrian Ratiu Signed-off-by: Richard Purdie

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