Positions forming in the Debian init system discussion
Positions forming in the Debian init system discussion
Posted Jan 4, 2014 9:40 UTC (Sat) by smurf (subscriber, #17840)In reply to: Positions forming in the Debian init system discussion by wahern
Parent article: Positions forming in the Debian init system discussion
Umm, what advantage do these process descriptors have, compared to cgroups?
Do you want these in addition to, or as replacement of, cgroups?
Do you want these in addition to, or as replacement of, cgroups?
Anyway, systemd is there and it's the best tool for replacing init there is (IMHO). How long do you want to wait before replacing SysVinit, given that this Google Code project is a year from having widely-tested production code which can replace PID 1?
Also, Capsicum/Linux is implemented as an LSM. It's not yet part of the kernel. Plus there is no stacking of LSMs in the kernel yet (let alone one that's tested widely enough). So you'd have to tell people that they can't use AppArmor or SElinux any more. For this reason alone, Capsicum may be interesting, but its chance of being adopted as "the" init by Debian are precisely zero.