9396 2016-04-05 13:17:54 +0000 wic does not handle --fsoptions properly in kickstart file 2016-04-14 15:09:01 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.0 Other arm RESOLVED FIXED Medium+ normal 2.1 M4 1 vesa.jaaskelainen eduard.bartosh ross.burton --- --- Don't know oldest_to_newest 60800 0 vesa.jaaskelainen 2016-04-05 13:17:54 +0000 When using kickstart file like following: part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 1024 --size 64M --overhead-factor 1 --extra-space 0 part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label root --align 1024 --size 1000M --overhead-factor 1 --extra-space 0 part /foo --ondisk mmcblk0 --fstype=ext4 --fsoptions="noatime,nodiratime,ro,nodev,nosuid" --label foo --align 1024 --size 1000M --overhead-factor 1 --extra-space 0 part /bar --ondisk mmcblk0 --fstype=ext4 --fsoptions="noatime,nodiratime,rw,nodev,nosuid" --label bar --align 1024 --size 5500M --overhead-factor 1 --extra-space 0 Then do: wic create my-kickstart-file.wks -e my-image -o img/ SD card image is created with only first two partitions /boot and /. If --fsoptions settings is removed altogether then we get all four partitions but with incorrect mounting options. Alternative way to solve file system mount option problem is to give user an option to leave fstab as is and just create image file as requested. Now wic insist on modifying fstab with its own entries. What I am expecting is to get SD card image with partitions: /boot (image : files needed for booting) / (image : rootfs) /foo (empty formatted partition) /bar (emtpy formatted partition) This was with yocto-2.0.1. 61131 1 eduard.bartosh 2016-04-13 09:47:32 +0000 Fix has been sent for review: http://lists.openembedded.org/pipermail/openembedded-core/2016-April/120212.html 61228 2 eduard.bartosh 2016-04-14 15:09:01 +0000 The fix has been merged to master: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f7352ca2c483ef695c7276296d1f08b3ff4c1d2e