Building Safe Systems with Linux
summary
SIL2LinuxMP summarizes three years of work and concludes Linux can be a candidate for safety-related systems but only via standards mapping and rigorous evidence not by buying pre-certified binaries. It classifies modern projects as Type B systems requiring return to IEC 61508 and rejects proven-in-use for complex platforms, instead prescribing assessment of non-compliant development (route 3). It warns there is no certified multi-core hardware, expects frequent kernel updates (roughly one stable patch per week, ~1/30 safety-relevant), and outlines selection, architecture and process controls.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:18What standard to use
- 2:36Domain standards
- 6:00Compliance
- 10:50Type A Systems
- 22:52Linux for Safety
- 30:18System Design
- 33:47Interpretation Mapping
- 37:35Extensions
- 38:32Certification
related talks
42mDecoding Safe(ty) Linux Architectural Approaches for Critical Systems
42mEnabling Linux in Safety-Critical Applications
44mPanel Discussion: Enabling Linux in Safety Applications
42mBoF: Safety + Open Source Software: Where it Started & Where It's Going
19mAutomotive Linux for RISC-V
27mDebating Linux in Aerospace: Objections and Paths Forward
02mSafe Systems with Linux MC Wrap up and next steps
39mCivil Infrastructure Platform: State of Industrial Grade Linux