3 ms·
I hope the automotive vendors will embrace the security maintendance experience of the likes of suse, redhat, canonicalfor their Linux based performance ECUs.
by froh 5y ago
I hope the automotive vendors will embrace the security maintendance experience of the likes of suse, redhat, canonicalfor their Linux based performance ECUs. I sense however the yocto style patch everything and tweak it to my likings embedded chaos will reign for a while. the reluctance of the arm ecosystem to mainline their BSPs doesn't help.
but how do you explain the value add of a built once used and validated everywhere binary? and a standardized security architecture and frozen version maintenance? to yocto embedded folks?
- varjag 5y agoPackage management systems are available in Yocto as well. Nobody uses those because running package based updates on headless, operator-inaccessible, embedded devices is corporate suicide. Full image update is a better engineering practice, that's why it is done this way.
- froh 5y agothat's deployment. yocto only has half baked support for a binary layers, let alone binary sdk layers, where you add more packages, for the target or the build host, and more layers come further down. this is for you to use the binary packages to build your images. which you then deploy, as you suggest. key thing: you use suse/ubuntu/redhat binary packages to build and create your add-ons which you then deploy, as image-on-the-fly (created on target during traditional Linux install/update), or as precooked image (qemu, container or, new: embedded flash image)
- varjag 5y agoWhy on Earth would you use a third party binary package when the true upstream source is available?