Michael Biebl <email@example.com> (2014-08-11): > That is > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754987 > https://lists.debian.org/debian-user/2014/07/msg01509.html > > I know a workaround, but haven't figured out the underlying cause yet. FWIW I spent some time on #debian-systemd and idly noticed some mentions of a boot-time timeout; when Ben mentioned net.agent I finally connected the dots and we stopped spending more time on it. > > Surprisingly, the bug vanished suddenly today when I started checking > > latest parted changes! Because: tada, systemd was my brand new shiny > > init! > > > > I haven't been able to perform any testing on non-Linux, but I think I'm > > OK with a release even if we finally find out that these images need a > > fix at some point. > > Hm, was that a desktop installation? This might explain that > systemd-sysv was installed by default (via libpam-systemd). No, it was not. Just a minimal installation (standard tools or whatever it's called in English, I do localized installation most of the time to spot i18n issues). And there was indeed no libpam-systemd. > A minimal installation should still pull sysvinit-core as it is the > first alternative in "init". Since that's not happening I'm going to guess that systemd-sysv's priority being higher than sysvinit-core's might be the important (no pun intended) difference here. I'll try to confirm/infirm that later on. Mraw, KiBi.
Description: Digital signature