[16:46] <ia_> Hello. Just to clarify - is this >[ https://web.archive.org/web/20160428030021/http://developer.ubuntu.com:80/en/snappy/guides/porting/ ] exact concept is dead for embedded devices? Yes, I know that I still can use and devel snap packages, but what about storage-based chromeos-like approach for a whole system? I mean system-a/system-b, switch between them, etc. And now looks like that rollbacks are implemented via simple copying >[ https://snapcraft.io/docs/core/updat
[16:46] <ia_> es ] instead of switching whole partition. Thanks in advance.
[17:07] <ogra_> ia_, the newer ubuntu core images use a single writable partition and snap packages on top ...  the rollback is done by switching between versions of the snaps not by switching partitions
[17:08] <ogra_> ia_, there is a core snap (the rootfs), a kernel snap and a gadget snap (the bootloader and basic system configs) ... to roll back you can just switch to a different core or kernel snap
[17:09] <ia_> ogra_, just like I thought - thank you for clarification.
[17:10] <ogra_> on the low level thats way less complex and on the top level way more reliable that way
[17:10] <ogra_> the former partition setup was a pain and very limited
[19:31] <Chipaca> zyga-suse: o/