Stefan Agner

This is something which is on my todo list. At this point I am not aware of a show-stopper for using genimage. There is a bit a of MBR magic...

> migrating from rauc to swupdate Such a change would be a bit more involved, and would need a convincing reason to do it. Besides OS, it would need changes...

What you are seeing is U-Boot trying to boot through network since it wasn't able to find the OS on the SD card. So the root problem is that U-Boot...

> Surprisingly downgrading to 7.6 with (ha os update --version 7.6) and even to core 2022.6.3 didn't fix the problem. That is weird. There most be something else in play...

We use a bind mount of `/dev` from the host so we don't have to manage udev rules to add new devices etc. The read-only mount seems not to affect...

So it seems that the network configuration got changed to disabled in all cases? The Supervisor handles the network configuration, so this is likely caused by the Supervisor.

Just to be clear on how the system should behave in absence of network (e.g. DHCP server not reachable): - The network will continue to try to wait for network...

In general we don't have a good way to mount any storage device persistently. Along with that, mounting network file system is also still "unsolved". > I think the missing...

According to the [Linux Kernel documentation](https://www.kernel.org/doc/html/latest/admin-guide/sysctl/fs.html#max-user-watches), the default of this value depends on the amount of memory your system has. By default the system allows to allocate file system watcher...

> Now looking into quick, it is recommended to increase the UDP buffer size by running (see [here](https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size)): > > sysctl -w net.core.rmem_max=2500000 Sounds fair. I wonder if we can...