Package: usb-modeswitch
Version: 0.9.7-1
Severity: important
Hi,
When I tried configuring my 3G ZTE/onda MF626 usb key, I had a hard time
trying to understand why after setting the right value in
/etc/usb_modeswitch.conf and having it work manually (using "sudo
usb_modeswitch"), I couldn't get it to work automagically through udev.
The reason was that there is 2 lines in /etc/usb_modeswitch.conf for the
ZTE MF626 and only the second one (which is supposed to be the
"fallback" solution) is present in the file usb_modeswitch.rules
generated by mkrules.py.
My first idea to correct this bug was to ask to modify mkrules.py so it
includes the 2 lines, but I think this is probably the wrong approach.
My understanding of the rational behind mkrules.py is that is allows to
create a udev.rules that automatically contains entries for all the
devices in the mainstream package.
But in the actual form, on top of the actual bug I presented above, this
approach means you may have to modify 2 files to get your device working
in both manual and auto mode. This could lead to further discrepancies
in the configuration and imho is error prone.
Also, unless I've failed to notice something, I think it is useless
since if you don't specify parameters in the udev rule, usb_modeswitch
will get the right values from /etc/usb_modeswitch.conf.
Thus, I believe that it would be more elegant to have mkrules.py
generate a usb_modeswitch.rules file containing one line per
DefaultVendor:DefaultProduct pair, without any parameter to the
usb_modeswitch command.
Cheers,
Gildas Le Nadan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
