EH21 - Maintainable Embedded Linux Solutions

Smaller Linux images are better for maintenance and security - less code means fewer interfaces and attack surfaces to maintain

Three main approaches to building embedded Linux:

• From scratch (Yocto, Buildroot)
• Golden image (based on existing distro like Raspberry Pi OS)
• Remix approach (using Debian packages with tools like Elbe, Debos)

Key considerations for choosing an approach:

• Project lifetime/maintenance requirements
• Need for optimization and customization
• Available development time and resources
• Security requirements
• Team expertise and learning curve

Yocto provides:

• Complete control and customization
• Cross-compilation support
• Board support packages
• Security monitoring
• Steeper learning curve

Package-based approaches (Elbe, Debos):

• Easier maintenance through package updates
• Faster initial development
• Less optimization potential
• Dependent on distribution maintenance

For long-term maintained systems:

• Document all configuration decisions
• Consider future security updates
• Plan for package/distribution upgrades
• Choose tools based on maintenance burden

Performance considerations:

• SystemD vs SysV init impacts startup time
• Cross-compilation vs native builds affects build time
• Package selection significantly impacts image size
• Process count affects resource usage

Tools comparison:

• Yocto/Buildroot: Most flexible, highest complexity
• Elbe/Debos: Faster development, Debian-based
• KiwiNG: More IT-focused, less embedded-oriented