Control: -1 tags moreinfo Hi
As Michael Biebl suggested, a direct involvement of systemd is pretty unlikely (but nothing can ever be called impossible). Likewise there are no specific dependencies or conflicts/ breaks that would force a specific init from wpasupplicant's point of view, it does support- and integrate with all three contenders (well, there is only a very shallow direct integration, at most initiation the DBus interface in case of systemd, the actual configuration or startup sequence of wpasupplicant is not handled by any init system directly, but by the networking dæmons supervising wpasupplicant). In order to debug this further, it would help tremenduously to get an idea about your system state (before the upgrade and now), just as well as your network configuration. The most important data for now would be: - versions of ifupdown before and after the upgrade - versions of wpasupplicant before and after the upgrade - when was your last full (dist-)upgrade, did you try to do partial upgrades to avoid systemd from getting installed (anything relevant held back)? - your /etc/network/interfaces and wpasupplicant configuration, make sure to obfuscate personal information and passwords(!), but retain its structure and syntax. - what exactly is failing, did it work before - any hints in dmesg or when running wpa_cli - systemd (not systemd-sysv) is co-installable to sysvinit-core, accordingly you can switch between systemd as pid1 and sysvinit as pid1 with a simple kernel parameter (init=/lib/systemd/systemd), this can help to determine if sysvinit or systemd really makes a difference in your situation without changing any of the installed packages or modifying any of your configuration files Regards Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.