D7net Mini Sh3LL v1
Current File : //libx32/../share/snapd/../locale/ia/../../doc/info/../libroken18-heimdal/../usbmuxd/../liberror-perl/../grub2-common/../libjpeg8/../php7.4-mysql/../gnupg/../python3-apt/../netplan.io/../wget/../libcurl3-gnutls/../libthai-data/../python3-six/../screen/../maria/../libxaw7/../libmnl0/../netplan/../gdisk/../systemd-sysv/../grep/../udisks2/../libacl1/../libxmlb1/../libperl5.30/../automake/../libmpfr6/../libisl22/../libext2fs2/../libcrypt1/../libtiff5/../zerofree/../libudev1/../debianutils/../diffutils/../libpython3.8/../kbd/../gawk/../libblockdev-utils2/../lbt/../libgssapi3-heimdal/../libsm6/../libxmlb1/../libalgorithm-merge-perl/../procps/../usb-modeswitch-data/README.Debian |
===== usb-modeswitch-data =====
=== Overriding entries from the database tarball ===
From its 1.1.7 version, usb-modeswitch searches for device switching data in
the usb-modeswitch-data database tarball [0]. This heavily reduces the
database disk space, but makes configuration investigation harder. To solve
this issue, usb-modeswitch is shipped with a patch that allows administrators
to override the database entries from the tarball [0] with files under /etc.
[0] /usr/share/usb_modeswitch/configPack.tar.gz
= Example =
Let's assume one has a 3G dongle "05c6:1000 Qualcomm", which matching database
entry [1] is 05c6:1000:uMa=Option , but isn't correctly switched. Hacking this
database entry can be done as following:
# cd /etc/usb_modeswitch.d
# tar xzf /usr/share/usb_modeswitch/configPack.tar.gz 05c6:1000:uMa=Option
Now the /etc/usb_modeswitch.d/05c6\:1000\:uMa=Option file will get used by
usb_modeswitch_dispatcher when the "05c6:1000 Qualcomm" device gets plugged
in.
When a correct database entry is found, please report it on the upstream
forum:
http://www.draisberghof.de/usb_modeswitch/bb/
[1] One can find exactly which database entry is matching a given device gets
matched with by activating logs (/etc/usb_modeswitch.conf) and reading
them from /var/log/usb_modeswitch*.
AnonSec - 2021 | Recode By D7net