>>> but rather, the inflexibility of the statically maintained ifupdown
>>> software on an ever evolving Debian/Ubuntu software ecosystem.
>> What exactly do you mean by "statically maintained"?
> WPA keys written to /etc/network/interfaces as outlined in
> /usr/share/doc/wpasupplicant/README.Debian.gz, Section 2. Mode #1:
> Managed Mode.
Ah. I would have perhaps called that "statically configured", not
"statically maintained software". Ok.
> That mode is pretty popular among debian users, properly documented,
> widely advocated and obviously also used by a lot of ubuntu users,
> judging from the numbers of duplicates of this bug.
I've never questioned the validity of the bug, only the fix.
>>> but rather, the inflexibility of the statically maintained ifupdown interfaces as outlined in doc/wpasupplica nt/README. Debian. gz, Section 2. Mode #1:
>>> software on an ever evolving Debian/Ubuntu software ecosystem.
>> What exactly do you mean by "statically maintained"?
> WPA keys written to /etc/network/
> /usr/share/
> Managed Mode.
Ah. I would have perhaps called that "statically configured", not
"statically maintained software". Ok.
> That mode is pretty popular among debian users, properly documented,
> widely advocated and obviously also used by a lot of ubuntu users,
> judging from the numbers of duplicates of this bug.
I've never questioned the validity of the bug, only the fix.