3 ms·
The containerisation approach on Linux isn't because of insularity or NIH - it's because the Linux kernel development process does not accept large, far-reachin
by caf 10y ago
The containerisation approach on Linux isn't because of insularity or NIH - it's because the Linux kernel development process does not accept large, far-reaching "big bang" code drops. Instead, changes that have wide impact across the core kernel are expected to be made in a series of smaller incremental improvements, each of which is more limited in impact and more easily reviewed.
- talideon 10y agoWhy would borrowing the APIs enabling existing containerisation approaches have lead to large, far-reaching big bang code drops?
- pcvarmint 10y agoSuch as systemd? :-)
- cbd1984 10y agoPlease stop flaming with irrelevant comments.
- caf 10y agosystemd isn't part of the kernel at all.
- legooolas 10y agoYet. (Does kdbus count?)
- digi_owl 10y agoGiven that they seem to have given up on kdbus, and is instead developing something called bus1 that appears they are not even planning to submit for inclusion, i find myself thinking that the systemd devs are these days working on enveloping the kernel. Meaning that you no longer use kernel syscalls, but instead program with systemd in mind and then systemd talks to the kernel as it sees fit. Just observe their actions regarding session tracking, where they are basically ignoring all data from the kernel about sessions.