Yocto Linux for a robotics product: a rebuildable image, kernel CVE patching, and a sprint/release cadence that treated patching as ordinary work.
Prior program of Arpan Patel, proprietor and principal of ASHNAY SOFTWARE. Not an ASHNAY company case study. ASHNAY SOFTWARE did not ship this work.
Prior program
Problem
The product needed a Linux image that could be rebuilt and patched after the first bring-up — including kernel CVEs that arrive on someone else’s schedule.
Notes
Robotics images accumulate history: a kernel someone pinned, a userspace package nobody wants to touch, a CVE that is already in the tracker. The work is to make patching a release activity instead of an emergency.
That means a rebuild you can repeat, a place in the layer for the patch, and a test you can point at when someone asks whether this week’s image is the one you meant. The Insights note on Yocto CVE practice is the public write-up of that habit.
ASHNAY did not ship this robot. The principal ran this class of Linux work. That is the only claim on this page.
