Am 11.08.2014 22:51, schrieb Cyril Brulebois: > Michael Biebl <email@example.com> (2014-08-11): > > Your second mail: >> Btw, since "init" still pulls in sysvinit-core atm, lowering the >> severity of sysvinit and sysvinit-core shouldn't have an effect for >> d-i. >> >> If it does, could you elaborate, what happened/went wrong? > > AFAICT right now, nothing went wrong; quite the contrary. I had been > experiencing the net.agent 30s hang since beginning of August when I > started getting stuff into shape. After some bits of debugging and > sharing test results (#debian-kernel), Ben and I found out that "apt-get > install systemd" was a fix, so we didn't investigate any further. 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. > 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). A minimal installation should still pull sysvinit-core as it is the first alternative in "init". Anyway, this will change soonish and then we finally have consistent and reliably behaviour upon fresh jessie system installations no matter whether you install a desktop system or a minimal one. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature