On Fri, May 09, 2014 at 10:56:43AM -0700, Steve Langasek wrote: > The default hasn't changed; sysvinit still lists sysvinit-core as the first > alternative for its pre-dependency on /sbin/init. What is forcing > systemd-sysv onto users systems in advance of this change?
Also, if the order of dependencies changes, that should not affect existing installations. On my system, I see systemd-sysv being pulled in by libpam-systemd, which is required by network-manager and policykit-1. libpam-systemd will accept systemd-shim instead of systemd-sysv as well, but it's listed later, so the user has to manually select it if they want to keep their init system. In a long list of "this needs to be changed to make the upgrade work", it's very easy to miss that it happens at all, and even if a user does see it, I don't think we can expect them to understand what it means, and go check if there is an alternative. I think it would be good for libpam-systemd to list systemd-shim first. That way, installations that already have systemd for some other reason (like it being the default from d-i) will still work, but it won't switch existing installations to a new init system unexpectedly. That being said, I don't really care much about the init system; sysv worked fine for me, and now I apparently have systemd and it doesn't seem to cause problems either. Thanks, Bas -- 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/20140509191302.gg10...@fmf.nl
