3 ms·
This is great. It will give Debian access to features like a faster startup, a sane way of restarting daemons that die, better power management and process man
by cmccabe 13y ago
This is great. It will give Debian access to features like a faster startup, a sane way of restarting daemons that die, better power management and process management.
- sciurus 13y agoWhat is great? Debian hasn't decided to switch to systemd.
- shmerl 13y agoBut systemd already works in Debian. Though it's optional: http://wiki.debian.org/systemd http://wiki.debian.org/systemd
- asb 13y agoBut the latest systemd even in sid is version 44, which is ancient.
- cmccabe 13y agoThis seems pretty clear: How will this work? In the short-term future, maintainers add systemd support to their packages. This does not imply dropping sysvinit support. As outlined in my post about the transition, systemd service files can coexist with sysvinit scripts. In the mid-term future, both sysvinit and systemd are supported — this is the only way we can do a gradual transition, and Debian clearly does not want a flag day. In the long term, we could switch the default from sysvinit to systemd on Debian GNU/Linux, in case we agree that’s a reasonable decision at that time. Non-Linux ports will still use sysvinit. We can argue over the exact meaning of "switch to" (seems pretty pointless to me), but it seems fairly clear that in the near future nearly all debian users will be using systemd.
- sciurus 13y agoReread this part of your quote- "in the long term, we could switch... in case we agree that's a reasonable decision at that time" This is a blog post by a Debian developer that would like the project to switch the default init system. It includes some discussion of how Debian could make the transition. It's nothing the project has committed to, so saying "that in the near future nearly all debian users will be using systemd" is unwarranted.