Linux Sandboxes and Fil-C
Memory safety and sandboxing are two different things. It's reasonable to think of them as orthogonal: you could have memory safety but not be sandboxed, or you could be sandboxed but not memory safe.
Welcome to Fil-C, an actively supported memory safe implementation of the C and C++ programming languages you already know and love.
Visit fil-c.org → On Hacker News Sep 2025 – Jun 2026
Systems & Performance 6Security & Privacy 4Software Engineering 2
Memory safety and sandboxing are two different things. It's reasonable to think of them as orthogonal: you could have memory safety but not be sandboxed, or you could be sandboxed but not memory safe.
This document describes how Fil-C supports longjmp , setjmp , setcontext , getcontext , makecontext , and swapcontext in a totally memory-safe way. In particular, no misuse of those APIs in Fil-C can lead to stack corruption or any other violation of Fil-C's capability model.
Since Fil-C 0.685, memory-safe inline assembly is supported on both X86_64 and ARM64.
Pizlix is LFS (Linux From Scratch) 12.2 with some added components, where userland is compiled with Fil-C. This means you get the most memory safe Linux-like OS currently available.