The old version doesn't give you any advantage as there's nothing that qualifies a "release" that other shas don't give you, except that it's tagged at some point in time as "release". But sticking to

Anyway, this doesn't answer the questions? Kind regards, Christian

Hm, so you explicitly enumerate all scripts except for cryptroot so that you run (hopefully right?) thereafter. Isn't it sufficient to make cryptroot dependent on this? Looks too verbose and complicat

Hm, shouldn't size be configurable? Is this the right point in time? Isn't /tmp needed before this? Kind regards, Christian

Hm, why do you replace/create those services instead of augmenting the current default ones via conf.d'lets? Why is this one here dependent on network? Why does this differ that much from upstream ser

Why not upgrade to a newer version of SWUpdate instead of backporting stuff? There's no real advantage to stay on a "release" as SWUpdate follows rolling releases -- granted, you have to do the qualif

A note where this comes from, where it's supposed to go in oder to get rid of this patch here eventually would be helpful. Kind regards, Christian

Well, meanwhile, this pattern has been deprecated in favor of using https://github.com/sbabic/libubootenv I guess it's about time for EFI Boot Guard to catch up.. Kind regards, Christian

Hi Quirin, Did you intentionally go from UIDs to PATHs? Why not uniformly using UIDs? Are you sure you really need setting ustate these days? Kind regards, Christian

Hi, If I understand the idea correctly, there's then a Linux companion agent that does, e.g., the cloud communication and sets up the update payload to be consumed and applied by the UEFI firmware upd

Hi Scott, Well, just for the record.... Balena{,OS} revolves around Docker, e.g., to fetch the firmware (=container) images prior to extracting them to the spare partition in A/B deployments. Granted,

Hi Suzuki, I meant (A) to spare you (re)exploring the path I went :) I'd like to show off some features you may find useful along the way as well. Just let me know when you're ready and I'll setup the

Hi Suzuki, OK, then I'd propose having a meeting about this so that I can explain how this variant works and how we make use of it. When do you think you'll come to this point so that a meeting makes

Hi Suzuki, You're always welcome. That sounds good! Glad I could help here. Sounds reasonable, good to have it sorted out. This is because SWUpdate is designed around a multi-process model with IPC am

Hi Suzuki, Ah, OK, didn't try that myself yet. Looks good as / is mounted ro. Question is whether this is done via a remount,ro or whether it's ro right from the start? To find out what's touching the

Hi Suzuki, OK, from the diffs it seems that temporary storage directories such as /run and /var/tmp are not separate mount points from your roots? You can use tune2fs -l /dev/<rootdevicenode> and look

Hi, Hm, did you check that you didn't flash the filesystem you have currently booted, i.e., are you overwriting the currently running root filesystem? I have seen such errors when I did this by accide

Hi Akihiro, First of all, thanks for the detailed report! It was of great help to reproduce the issue locally. Your test environment is fine. Hence, what you found is a bug. The reason for this bug is