So using your manifest example and my partition scheme from earlier ...
So your manifest might look like:
[update]
compatible=rauc-example
version=2021.05-1
[bundle]
format=verity
[image.kernel]
filename=kernel.img
[image.rootfs]
filename=rootfs.tar
[image.appfs]
filename=appfs.tar
Best regards,
Jan
My system.conf (using my example partition layout for earlier email) file would look something like:
[system]
compatible=rauc-example
bootloader=uboot
[keyring]
path=/etc/rauc/ca.cert.pem
[slot.kernel.0]
device=/dev/mmcblk2gp0p1
type=vfat
parent=rootfs.0
[slot.kernel.1]
device=/dev/mmcblk2gp1p1
type=vfat
parent=rootfs.1
[slot.rootfs.0]
device=/dev/mmcblk2gp0p2
type=ext4
bootname=A
[slot.rootfs.1]
device=/dev/mmcblk2gp1p2
type=ext4
bootname=B
[slot.appfs.0]
device=/dev/mmcblk2p1
type=ext4
parent=rootfs.0
[slot.appfs.1]
device=/dev/mmcblk2p2
type=ext4
parent=rootfs.1
So I should use "parent" to tie both kernel and appfs slots to the rootfs?
And for now, the rootfs is r/w on a ext4 filesystem, but in the future it will be a squashfs. So once that happens would 'type=ext4' then change to 'type=raw'?
Just trying to make sure I understand how to make manifest and system.conf map together for making bundles etc.
Regards,
Brian