| === ^arcade_droid is now known as use_strategy_lol | ||
| === use_strategy_lol is now known as ^arcade_droid | ||
| === Justin`afk is now known as Justin` | ||
| === JanC_ is now known as JanC | ||
| === JoshStrobl is now known as JoshStrobl|AFK | ||
| === Justin` is now known as Justin`afk | ||
| === JoshStrobl|AFK is now known as JoshStrobl | ||
| 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. | 16:46 |
| 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:07 |
| 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:08 |
| ia_ | ogra_, just like I thought - thank you for clarification. | 17:09 |
| 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 | 17:10 |
| Chipaca | zyga-suse: o/ | 19:31 |
| === Justin`afk is now known as Justin` | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!