On Thu, Nov 13, 2014 at 01:39:52PM -0800, Russ Allbery wrote: > Patrick Ouellette <poue...@debian.org> writes: > > > We do tell users of Debian what to do - that's part of the problem right > > now. We told the users they will switch init systems, and a large > > portion (or at least a vocal portion) don't want to. > > Well, no, we didn't. We said that there would be a different default, > which is not the same thing. The project hasn't made a decision about > switching, and also, at present, sysvinit is still fully supported (modulo > the normal pre-release bugs). >
By making it the new default, and causing apt-get dist-upgrade to install systemd (which is what happened to one of my systems) in place of sysvinit we most certainly are. Did the system implode in a fiery pool - no, but I was forced to deal with the unexpected aftermath. There was some breakage, and some things did not work as expected. (Sure, people would say I shouldn't be following unstable or SID but then I wouldn't have development environments.) By not having a meta-package "init-system" provided by an actual package, we are forcing anyone who upgrades to also change init systems unless they take special precautions to not do so. For the record, I really don't care about the init system per-say. I am more annoyed with the systemd insistence on logging to binary files than anything. Log files should be plain text. Pat -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141113215610.gg16...@flying-gecko.net