The GR doesn't attempt to change the default init for Jessie (Score: 1) by seriously@pipedot.org on 2014-10-18 07:27 (#2TEX) from the GR itself, section 3:The TC's decision on the default init system for Linux in jessie stands undisturbed.In other words, to systemd supporters: "don't panic", to systemd haters: "they're trying to find a solution that's good for everyone".Is this vote an attempt to delay the inevitable?On the one hand, there is no delaying systemd as the default init, that's a given. On the other hand, indeed, the main concern is that we're supposed to be only 3 weeks away from Jessie's freeze and that GR could delay the whole thing (as in a 2-month to 2-year delay depending on many factors). Re: The GR doesn't attempt to change the default init for Jessie (Score: 2) by skarjak@pipedot.org on 2014-10-18 13:32 (#2TF1) When I wrote that, I meant that I saw as inevitable that systemd would eventually be the only init system with decent support from developpers. It's been adopted to be at the heart of pretty much every major distro now. In that sense, by trying to make it so the next version of Debian has to offer support for other init systems, they would be delaying the inevitable, since presumably the next version after that would get rid of this support. Although I guess you could argue the delay would help transition. Re: The GR doesn't attempt to change the default init for Jessie (Score: 1) by nadaou@pipedot.org on 2014-10-19 05:55 (#2TFB) I see it differently, and so do the BSDs which will continue to evolve new generations of init system designs which the various cross-platform daemons will remain compatible with. If you are talking about GNOME's desktop notification daemons, they are perfectly expendable in the long run. Users choosing not to use systemd will likely not feel much loss at losing the likes of PulseAudio, NetworkManager, and D-Bus too. udev could be annoying, but it's not like we haven't replaced that before in the past and so couldn't do it again.As the resolution and others have said, even with systemd as the default init, allowing it to position itself as a non-modular single supplier not able to be replaced is a much bigger problem than its run-time deficiencies.
Re: The GR doesn't attempt to change the default init for Jessie (Score: 2) by skarjak@pipedot.org on 2014-10-18 13:32 (#2TF1) When I wrote that, I meant that I saw as inevitable that systemd would eventually be the only init system with decent support from developpers. It's been adopted to be at the heart of pretty much every major distro now. In that sense, by trying to make it so the next version of Debian has to offer support for other init systems, they would be delaying the inevitable, since presumably the next version after that would get rid of this support. Although I guess you could argue the delay would help transition. Re: The GR doesn't attempt to change the default init for Jessie (Score: 1) by nadaou@pipedot.org on 2014-10-19 05:55 (#2TFB) I see it differently, and so do the BSDs which will continue to evolve new generations of init system designs which the various cross-platform daemons will remain compatible with. If you are talking about GNOME's desktop notification daemons, they are perfectly expendable in the long run. Users choosing not to use systemd will likely not feel much loss at losing the likes of PulseAudio, NetworkManager, and D-Bus too. udev could be annoying, but it's not like we haven't replaced that before in the past and so couldn't do it again.As the resolution and others have said, even with systemd as the default init, allowing it to position itself as a non-modular single supplier not able to be replaced is a much bigger problem than its run-time deficiencies.
Re: The GR doesn't attempt to change the default init for Jessie (Score: 1) by nadaou@pipedot.org on 2014-10-19 05:55 (#2TFB) I see it differently, and so do the BSDs which will continue to evolve new generations of init system designs which the various cross-platform daemons will remain compatible with. If you are talking about GNOME's desktop notification daemons, they are perfectly expendable in the long run. Users choosing not to use systemd will likely not feel much loss at losing the likes of PulseAudio, NetworkManager, and D-Bus too. udev could be annoying, but it's not like we haven't replaced that before in the past and so couldn't do it again.As the resolution and others have said, even with systemd as the default init, allowing it to position itself as a non-modular single supplier not able to be replaced is a much bigger problem than its run-time deficiencies.