The manic abuse by the glibc devs of the gnu symbol/module versioning makes linux ABI stability extremely attractive (actually even ISO work has a smell of plan

The manic abuse by the glibc devs of the gnu symbol/module versioning makes linux ABI stability extremely attractive (actually even ISO work has a smell of planned obsolescence nowdays). This is a very good idea... since I decided to do exactly that for many of my personal projects and I started years ago. That said, "clone" syscall is the easy part. For newcomer, a gentle introduction and explanation of the volontary cpu yielding "futex" synchronization primitive is kind of much more important, or we'll end up with spinlocks everywhere. Often, you need 2 "futexes" to build higher level synchronization primitives. One of the good things here is educational: it shows how much expensive a cpu yielding synchronization primitive is since usually it is "hidden" by the POSIX API.