Felix Homann wrote:
Justification: breaks the whole system
Please be a bit less dramatic with error descriptions/justifications ;-)
I tried upgrading wpasupplicant from 0.4.7-4 to 0.4.8-4 on a remote system
that is connected to the network via a WPA connection using wpa_supplicant.
The system is a "server only" system: It does not have a video card or
keyboard but is maintained via SSH.
After upgrading everything seemed to work as usual until reboot. After reboot
the system could not connect to the network anymore and was therefore
unmaintainable.
Need more info here please. How was wpasupplicant started on this system?
Reason: /etc/wpa_suplicant.conf was renamed without warning.
Solution: Don't rename /etc/wpa_supplicant.conf on upgrade.
Okay, I can agree with this conclusion, somewhat. We are not supplying a
wpa_supplicant.conf by default any more, but should we really rename a
working, personally maintained conffile?
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
