On 15 June 2010 18:47, Michael Meskes <mes...@debian.org> wrote:
> Is it possible to keep the old stuff as a fall back solution? Would that make
> sense at all?
I think it would be hard to do (the main problem is that rfkill
devices are not uniquely linked to wireless interfaces, so trying to
use both systems would lead to any kind of trouble), and I don't know
if it makes sense. Is it really a common use case to update
acpi-support while still using a very old kernel?
> There seems to be a problem with that file though as it adds a dependency on
> wicd. Is this on purpose?
Mmm, does it? if you mean the line
/usr/share/wicd/daemon/autoconnect.py || :
it won't fail if wicd isn't installed, since it's ORred with true
(well, it spits an error line, but then it returns 0), and I don't
propose to make acpi-support depend on wicd. It's just that wicd
doesn't reconnect after toggling wifi off and on if you don't poke it
(wpa_supplicant and Network Manager do, AFAIK)
I can change it with
[ -x /usr/share/wicd/daemon/autoconnect.py ] &&
/usr/share/wicd/daemon/autoconnect.py
if you prefer.
Cheers,
Luca
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
