Kai Lüke

PR in https://github.com/flatcar/bootengine/pull/52 We can leave this open to use `CONFIG_EFI_ZBOOT` as final improvement for arm64.

Now with the 6.1 update the amd64 kernel is quite large, even larger than the arm64 kernel. Some configs got changed unexpectedly, this could have caused it, too.

Differences were also discussed in https://github.com/flatcar/Flatcar/issues/968 and the last PR (:crossed_fingers:) is filed to complete the docs migration to Butane: https://github.com/flatcar/flatcar-docs/pull/299

Writing `/etc/flatcar/update.conf` through Ignition should work. The `/etc/coreos` symlink to `/etc/flatcar` is there for compatibility but as long as you use a new image `/etc/coreos` won't be a directory, even...

We can close this now, or? The initial bug was addressed. Please report any problems again as new issue.

Thanks for the explorations! Because @tormath1 wants to look into using the quadlet podman systemd generator, I had a quick look at the sysext image and found that it misses...

PR https://github.com/flatcar/scripts/pull/1964 merged but we don't have docs and the kola tests yet, see https://github.com/flatcar/scripts/pull/1964#pullrequestreview-2037448109 for links to the locations.

Each node identifies itself with the machine id from `/etc/machine-id` which must be unique. You can add human understandable context in the `MACHINE_ALIAS` entry: https://www.flatcar.org/docs/latest/setup/releases/update-conf/ Put `MACHINE_ALIAS=something` as a new...

What error message did you get? I tried this on Fedora 39 with the `systemd-sysext` binary from `v256~rc1` and it works without errors: ``` $ getenforce Permissive $ ls -l...

Just for your reference, there was also https://github.com/smoltcp-rs/smoltcp/pull/450 and https://github.com/cbranch/smoltcp/commits/cbranch/cc (other non-upstreamed things are also public: https://github.com/cbranch/smoltcp/branches/stale, and if you are looking into BBR there is https://github.com/quinn-rs/quinn/tree/0.8.0)