4 ms·

so if Vsinit is stable and bug free right now, why switch to something that isn't? Also, systemd has had two bad exoploits over the course of about a year. The

so if Vsinit is stable and bug free right now, why switch to something that isn't? Also, systemd has had two bad exoploits over the course of about a year. The flaws in Vsinit you point out were two years apart, and the former of the two could only be triggered by someone who was already an admin, and gave no opportunity for privesc. Given, init panicking is never acceptable, but it's a heck of a lot better than what systemd did.

JdeBP 10y ago
Anyone who erroneously thinks that van Smoorenburg rc is bug free hasn't spent time fixing the whole host of faulty, incomplete, and rickety van Smoorenburg rc scripts that exist. It is also erroneous to propound the old There Is Only System 5 init And systemd fallacy, which is just bunkum. * https://news.ycombinator.com/item?id=13477512 https://news.ycombinator.com/item?id=13477512
- qwertyuiop924 10y ago
  I'm well aware there are other inits: OpenRC, BSDinit, Runit, s6/s6-rc, and many others are all better alternatives to both sysvinit and systemd. I was making the sysvinit comparison here for simplicity's sake. >Anyone who erroneously thinks that van Smoorenburg rc is bug free hasn't spent time fixing the whole host of faulty, incomplete, and rickety van Smoorenburg rc scripts that exist. I never said it was bug-free, I said that the problems with the rc scripts aren't inherent to the sysvinit model.