| 1 |
frederik.pfautsch: |
| 2 |
|
| 3 |
> > So, ideally, there is c): In a hypothetic case we would prepare |
| 4 |
> > a entire OS incl. our app (maybe via catalyst?) which would |
| 5 |
> > require a bootloader-like mini-OS on the customer's side, to |
| 6 |
> > receive updates over the internet, switch the OS at boot time, |
| 7 |
> > and fallback. I was recently playing with systemd-boot and it's |
| 8 |
> > interesting try-boot feature. |
| 9 |
> |
| 10 |
> So essentially it sounds like you want something similar to Yocto / Poky |
| 11 |
> / Petalinux for the non-embedded world (and based on Gentoo of course; |
| 12 |
> it sounds like catalyst is something like that)? |
| 13 |
|
| 14 |
I've had a look on that: Wow, another interesting approach to build |
| 15 |
customized OSes. Thanks! |
| 16 |
|
| 17 |
> Just throwing crazy ideas around, what about using net-boot for your |
| 18 |
> customer? This way they just need to store an image somewhere and can |
| 19 |
> update it whenever necessary. Or (ab-)using an initramfs. Or u-boot |
| 20 |
> bootloader, just like in the embedded world. Depending on the size of |
| 21 |
> the actual OS/rootfs, taking ideas from e.g. Android with their A/B |
| 22 |
> bootslots (i.e. two root-partitions or something, where one is active |
| 23 |
> and the other can be updated with clever scripts, after a reboot they |
| 24 |
> are swapped). |
| 25 |
|
| 26 |
... exactly what is on my wishlist currently! I am missing such an |
| 27 |
alternative when in need for updating a remote (customer's) OS, |
| 28 |
where ssh + emerge @world is just no option. If we had that, I'd see |
| 29 |
Gentoo (e.g. with catalyst or via Yocto) shining bright here as it |
| 30 |
is perfect in stipping down things to the required minimum. |
| 31 |
|
| 32 |
Thanks. |
Archives