
Originally Posted by
Ibidem
I don't care for kfreebsd, but as long as it gives a reason to stick with sysvinit, I'm all for it.
init should be init, that's it.
I don't wan't chroot upgrades failing, I don't want to recompile init if early stages need fixing, I don't need snapshotting, and DISK TOOLS DON"T BELONG IN INIT!
I can get 32 MB used with sysvinit and a ton of services, on debian; and chroot stuff works without any magic. I can't tell how a comparable systemd setup would be, but it beats Upstart, and systemd seems to have more of that garbage.
By the way, kfreebsd is not "experimental". It's officially supported.