Dan Williams schrieb:
The problem with usb_modeswitch now is that even after installing it and
its udev rules, the user has to manually uncomment the item in the
config file for their specific modem, which will never just work out of
the box.
Fortunately, there is an enlightened path now :-)
Config files - still simple text files - are collected in
/etc/usb_modeswitch.d. Names contain USB IDs and optionally further
strings to check with sysfs data to overcome ID ambiguities (which
bugged me for quite a while).
The rules entries all call one wrapper script (similar to "sane")
which takes lots of information from udev as parameters and does the
details of the identification stuff; after a successful switch it
checks for new serial devices; if there aren't any, the "option"
driver is used with the device ID via "new_id".
Two lines are syslogged, one on program start and one on
success/failure.
To add a device, a line with the IDs is appended to the udev rule,
and a corresponding config file goes into the collection folder.
My idea situation is probably just to use usb_modeswitch, but as a
distribution packager (for Fedora) I need the tool to work automatically
whenever anyone plugs in a modem that usb_modeswitch knows about,
instead of requiring that user to modify a config file.
Of course you are right, manual config file editing is unsuitable
for distributions. On the other hand, I'd like to have an automatic
configuration open enough to easily add new devices between release
cycles - and manageable by the average user with some guidance.
Feel free to contact me directly to avoid offtopicness ...
Josua Dietze
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
