Hey there,

 

we are using the Olimex Lime (A20) and the Debian Wheezy image of Igor. Great work.

 

We were wondering what you strategies are concerning updating all relevant system parts (bootloader/kernel/application).

 

Is there any reference implementation that anyone could recommend? 

We are following the trend of building "Murphy-compatible" (https://www.kernel.org/doc/ols/2005/ols2005v1-pages-21-36.pdf)

update mechanisms, but are looking how it is best done. 

 

Application wise this can be fairly easy be done via docker - which we are using - but what mechanisms are used for the bootloader itself and the kernel. The should be an atomic update procedure and automatic fallback/rollback mechanisms.

 

Would love to get some insights from you!

 

Regards,

Andy

 

Thank you!

 

Our updating part is done classic Debian way and this is consumer Linux level defaults. Most of distributions in this area are not even here.

 

You want to know if we would bring Armbian to industrial / "Murphy-compatible" level? No, we won't. Current level of support is already heavily sponsored with our free time - most of people are working on the project for free. Bringing Armbian to this level would only bring more work on all areas, testing and maintenance. On top of this for things which most people doesn't care.

 

Those few who understand and need such level of service are willing to pay lots of bucks for this. Industrial level of Armbian, Armbian "plus"  could be done, but it's not possible to be free, unless someone is willing to sponsor it.

Hi Igor,

 

thank you for your quick reply!

 

I didn´t mean to say that the team should bring this to armbian, this was more of an question of how other users are handling this and to share experiences/information.

 

Have you evaluated options yourself for Armbian plus? I think this could be a viable business model.