timemaster5

> I have this stuff mostly implemented. One thing I need to mention is that we only need a single entry for bootloader slot in the system.conf > > ```...

> So the only missing thing for me currently is that the `uboot.env` is being written to /boot, which means on updating the boot partition, that files gets removed and...

> Here is the fdisk output. > > Before > > ``` > root@raspberrypi4-64:~# fdisk /dev/mmcblk0 -l > Disk /dev/mmcblk0: 14.43 GiB, 15485370368 bytes, 30244864 sectors > Units: sectors of...

> So it seems I needed to change `/etc/fw_env.config` to tell `fw_printenv` where to look for the env you're too fast, I will try to respond to the rest during...

Anyway, I need to change my statement above, and maybe we need to change the title of this issue. According to @om26er 's findings, this is not an A/B deployment...

> Here is what I did to write a vfat image file, these functions are called through`ROOTFS_POSTPROCESS_COMMAND` > > ``` > python create_boot_img() { > import shutil, os > from...

Thank you for pointing this out. I haven't seen this part of the documentation. I believe, that it is not applicable to our case. They are talking specifically about updating...

> > If we want a real A/B deployment of /boot partition, we would need this bit, which already works for @om26er to atomically update u-boot only, and then let...

I know, but there is no such option in xen. I mean I can’t choose between ide and scsi, if I am correct there is a proprietary blkdev driver in...

Yep, you're right. The official way doesn't work. That's why I am mentioning this. It might be actually useful to support other hypervisors too, as at this point we can't...