I’m comparing options for an embedded Linux product and trying to separate durable support from a polished sales pitch. Which providers or approaches would you look at, and what should I verify?
Who’s worth talking to for long-term embedded Linux support?
Asked by
crumbtrail
Answers
First pin down what “support” means here. A long maintenance window for a general-purpose distribution is not the same thing as someone maintaining your board support package, kernel, bootloader, and device drivers. Get the exact hardware and software components covered in writing, including how security fixes are delivered and what happens when a component reaches end of support.
For a Yocto or OpenEmbedded-based product, Wind River Linux and ENEA are names to evaluate for commercial support. Ask for references on products with similar hardware and lifecycle needs, and have engineering review the support terms rather than judging by the presentation alone.
Reply to this answer
If the device can use a standard distribution, Red Hat, Ubuntu, Debian, and SUSE are reasonable starting points. Compare the support contract and the exact packages you depend on, not just the headline number of years. Extended support can have separate costs or limits.
For embedded hardware, none of that automatically means the vendor will maintain your board’s drivers or boot chain. Confirm that separately before treating a distro lifecycle as the product lifecycle.
Reply to this answer
Yocto is a build system, not a support company. It gives a team a way to build and maintain a tailored Linux image, but somebody still has to own the recipes, patches, and hardware-specific pieces over time. A commercial provider can help with that, or your own team can, but the responsibility should be explicit.
Buildroot can be a simpler fit for a smaller device. The tradeoff is still there: simplicity does not make long-term patching and maintenance happen by itself.
BZZT:
So I’d compare the support plan and the internal maintenance capacity, not just the build tools.
Reply to this answer
I’d ask each candidate for a sample lifecycle plan: supported kernel and package versions, security-fix process, response expectations, and what changes if the original hardware is revised. Also ask how long they support the specific board or platform, not only their Linux distribution.
If they cannot clearly separate what they maintain from what the hardware supplier maintains, that’s a warning sign. The best-known brand is not necessarily the best fit for a particular device.
Reply to this answer
Add your answer
Answers are reviewed before publication.
crumbtrail:
That distinction helps. The board-specific maintenance is probably the part I need to scrutinize most.