Javier Martinez Canillas

> Since the replacing process needs to be supported in case `RENAME_EXCHANGE` is not available @dbnicholson FYI, I worked on a patch series to add `RENAME_EXCHANGE` support to vfat, latest...

FYI the patch-set got merged by a subsystem maintainer and are heading towards the Linux v6.0 release.

> I think we should create a higher level "protocol" between things writing data in `/boot` and the ESP and the bootloaders I believe that if that's the approach chosen...

> Would it be possible for OSTree to also be able to operate directly on /efi (systemd's preferred mount point for the ESP) Another option is to use the `renameat2(...,...

@luchonat there were a couple of issues that caused this in the past but these should had been solved in tpm2-abrmd 2.3.1 and I see that's the latest packaged version...

> What happens when `/boot` is on a filesystem without symlinks like FAT? Sorry, should probably look closer. If `/boot` is in a vfat partition then `ostree` won't work anyways,...

> Ah, right. That's another crappy downstream patch we have. I suppose if that's ever handled, it should work anyways since the FAT `/boot` is almost certainly a separate filesystem...

> It's horrible and I hope to be able to get this resolved upstream sooner or later. > > [endlessm/ostree@e178b1c](https://github.com/endlessm/ostree/commit/e178b1c228c0a9dd1669f1b9f61ecc3afe233b62) [endlessm/ostree@a8433f1](https://github.com/endlessm/ostree/commit/a8433f1204381f9b4a1b1f09ea17b35e4265f20c) Thanks for the links. I see the motivation there...

There's a third option, to convince the Linux aarch64 maintainers to add a decompressor in the kernel. They are were against doing it in the past, i.e: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-January/225277.html but really...

> of course, I'd prefer not having to deal with all this. I don't really understand why the decompression code that apparently already exists in the kernel and is regularly...