nemi92 / adb Goto Github PK

Welcome to Termux!

Communities: https://termux.org/community
Gitter chat: https://gitter.im/termux/termux
IRC channel: #termux on libera.chat

Working with packages:

• Search packages: pkg search
• Install a package: pkg install
• Upgrade packages: pkg upgrade

Subscribing to additional repositories:

• Root: pkg install root-repo
• X11: pkg install x11-repo

Report issues at https://termux.org/issues

.../DCIM/Screenshots $ ..cd
No command ..cd found, did you mean:
Command hcd in package hfsutils
Command ircd in package ircd-irc2
Command mcd in package mtools
.../DCIM/Screenshots $ cd
~ $ screenshot
screenshot: command not found
~ $ sd cart
error: the following required arguments were not provided:
<REPLACE_WITH>

Usage: sd <REPLACE_WITH> [FILES]...

For more information, try '--help'.
~ $ sd
error: the following required arguments were not provided:

<REPLACE_WITH>

Usage: sd <REPLACE_WITH> [FILES]...

For more information, try '--help'.
~ $ lsb
lsb: need at least one file to send
Try `lsb --help' for more information.
~ $ z
No command z found, did you mean:
Command c in package c-script
Command [ in package coreutils
Command hz in package hz
Command k in package kona
Command lz in package mtools
Command o in package o-editor
Command 7z in package p7zip
Command q in package q-dns-client
Command X in package xorg-server
Command xz in package xz-utils
Command z3 in package z3
~ $ usb
No command usb found, did you mean:
Command lsb in package lrzsz
~ $ lrzsz
No command lrzsz found, did you mean:
Command trzsz in package trzsz-go
~ $ trzsz
usage: trzsz [-h] [-v] [-r] [-t] [-d] [-z] command line

Wrapping command line to support trzsz ( trz / tsz ).

positional arguments:
command line the original command line

optional arguments:
-h, --help show this help message and exit
-v, --version show version number and exit
-r, --relay run as a trzsz relay server
-t, --tracelog eanble trace log for debugging
-d, --dragfile enable drag file(s) to upload
-z, --zmodem enable zmodem lrzsz ( rz / sz )
~ $ -z
No command -z found, did you mean:
Command hz in package hz
Command lz in package mtools
Command 7z in package p7zip
Command xz in package xz-utils
~ $ ls
Mail dead.letter localhost_20231118122630.txt termux.properties type
a.out devel printf test unalias
arm64 downloads storage trap
~ $ cd downloads
~/downloads $ ls
18_11_2023_18_24_40.png
'Andronix App.txt'
CODE_OF_CONDUCT.txt
'Hello termux install Linux .py'
Heloo
Hex
IMG-20231226-WA0000.jpg
IMG-20231226-WA0001.jpg
IMG-20231226-WA0002.jpg
IMG-20240111-WA0001.jpg
JetBrainsMono-2.304.zip
'Report Text.txt'
'Screenshot_20231118-151423_Network - WiFi Info & SIM Tools.jpg'
Screenshot_20231212-051702.png
Screenshot_20231229-233907_Settings.jpg
Vendor_18d1_Product_5018.kcm
'Zdielanie vzdialeného pracoviska s 0.txt'
apt
gdb-4.17.0.12-4.17.0.13.diff.gz
iUSB_-_WiFi_USB_Flash_Drive_f02f9b0a.apk
lastsync
linux-firmware-20231211.tar.xz
localhost_20231118122549.txt
manifest.xml
mosh-1.4.0.pkg
nethunter-2023.4-generic-armhf-kalifs-full.zip
nethunterpro-2023.4-pinephonepro-phosh.tar.xz
nethunterpro-2023.4-pinephonepro-phosh.tar.xz.torrent
nextersoft_banner_k.png
printf
public.libraries.txt.backup
received_836029701868932.jpeg
termux.properties
trace-exynos9810-QP1A.190711.020-2023-10-09-03-03-48.perfetto-trace
trace-exynos9810-QP1A.190711.020-2023-12-15-03-30-35.perfetto-trace
wireless-tools
~/downloads $ nethunter-2023.4-generic-armhf-kalifs-full.zip -extracht
nethunter-2023.4-generic-armhf-kalifs-full.zip: command not found
~/downloads $ nethunter-2023.4-generic-armhf-kalifs-full.zip -extracht
nethunter-2023.4-generic-armhf-kalifs-full.zip: command not found
~/downloads $ nethunter-2023.4-generic-armhf-kalifs-full.zip -extracht -info
nethunter-2023.4-generic-armhf-kalifs-full.zip: command not found
~/downloads $ install load <nethunter-2023.4-generic-armhf-kalifs-full>.zip
bash: nethunter-2023.4-generic-armhf-kalifs-full: No such file or directory
~/downloads $ install load <nethunter-2023.4-generic-armhf-kalifs-full>.zip -help
bash: nethunter-2023.4-generic-armhf-kalifs-full: No such file or directory
~/downloads $ nethunter-2023.4-generic-armhf-kalifs-full.zip help
nethunter-2023.4-generic-armhf-kalifs-full.zip: command not found
~/downloads $ nethunter-2023.4-generic-armhf-kalifs-full.zip help-z
nethunter-2023.4-generic-armhf-kalifs-full.zip: command not found
~/downloads $ nethunter-2023.4-generic-armhf-kalifs-full.zip help -Z
nethunter-2023.4-generic-armhf-kalifs-full.zip: command not found
~/downloads $ nethunter-2023.4-generic-armhf-kalifs-full.zip help --
nethunter-2023.4-generic-armhf-kalifs-full.zip: command not found
~/downloads $ .zip
No command .zip found, did you mean:
Command gzip in package gzip
Command hzip in package hunspell
Command lzip in package lzip
Command mzip in package mtools
Command zip in package zip
~/downloads $ zip help

zip error: Nothing to do! (help.zip)
~/downloads $ zip--
No command zip-- found, did you mean:
Command zip in package zip
~/downloads $ zip-
No command zip- found, did you mean:
Command zip in package zip
~/downloads $ package
No command package found, did you mean:
Command jpackage in package openjdk-17
~/downloads $ openjdk-17
openjdk-17: command not found
~/downloads $ jpackage
Usage: jpackage
Use jpackage --help (or -h) for a list of possible options
~/downloads $ jpackage --help
Usage: jpackage

Sample usages:

Generate an application package suitable for the host system:
    For a modular application:
        jpackage -n name -p modulePath -m moduleName/className
    For a non-modular application:
        jpackage -i inputDir -n name \
            --main-class className --main-jar myJar.jar
    From a pre-built application image:
        jpackage -n name --app-image appImageDir
Generate an application image:
    For a modular application:
        jpackage --type app-image -n name -p modulePath \
            -m moduleName/className
    For a non-modular application:
        jpackage --type app-image -i inputDir -n name \
            --main-class className --main-jar myJar.jar
    To provide your own options to jlink, run jlink separately:
        jlink --output appRuntimeImage -p modulePath \
            --add-modules moduleName \
            --no-header-files [<additional jlink options>...]
        jpackage --type app-image -n name \
            -m moduleName/className --runtime-image appRuntimeImage
Generate a Java runtime package:
    jpackage -n name --runtime-image <runtime-image>

Generic Options:
@
Read options and/or mode from a file
This option can be used multiple times.
--type -t
The type of package to create
Valid values are: {"app-image", "rpm", "deb"}
If this option is not specified a platform dependent
default type will be created.
--app-version
Version of the application and/or package
--copyright
Copyright for the application
--description
Description of the application
--help -h
Print the usage text with a list and description of each valid
option for the current platform to the output stream, and exit
--icon
Path of the icon of the application package
(absolute path or relative to the current directory)
--name -n
Name of the application and/or package
--dest -d
Path where generated output file is placed
(absolute path or relative to the current directory)
Defaults to the current working directory.
--temp
Path of a new or empty directory used to create temporary files
(absolute path or relative to the current directory)
If specified, the temp dir will not be removed upon the task
completion and must be removed manually.
If not specified, a temporary directory will be created and
removed upon the task completion.
--vendor
Vendor of the application
--verbose
Enables verbose output
--version
Print the product version to the output stream and exit.

Options for creating the runtime image:
--add-modules [,...]
A comma (",") separated list of modules to add
This module list, along with the main module (if specified)
will be passed to jlink as the --add-module argument.
If not specified, either just the main module (if --module is
specified), or the default set of modules (if --main-jar is
specified) are used.
This option can be used multiple times.
--module-path -p ...
A : separated list of paths
Each path is either a directory of modules or the path to a
modular jar.
(Each path is absolute or relative to the current directory.)
This option can be used multiple times.
--jlink-options
A space separated list of options to pass to jlink
If not specified, defaults to "--strip-native-commands
--strip-debug --no-man-pages --no-header-files".
This option can be used multiple times.
--runtime-image
Path of the predefined runtime image that will be copied into
the application image
(absolute path or relative to the current directory)
If --runtime-image is not specified, jpackage will run jlink to
create the runtime image using options:
--strip-debug, --no-header-files, --no-man-pages, and
--strip-native-commands.

Options for creating the application image:
--input -i
Path of the input directory that contains the files to be packaged
(absolute path or relative to the current directory)
All files in the input directory will be packaged into the
application image.

Options for creating the application launcher(s):
--add-launcher =
Name of launcher, and a path to a Properties file that contains
a list of key, value pairs
(absolute path or relative to the current directory)
The keys "module", "main-jar", "main-class",
"arguments", "java-options", "app-version", "icon", and
"win-console" can be used.
These options are added to, or used to overwrite, the original
command line options to build an additional alternative launcher.
The main application launcher will be built from the command line
options. Additional alternative launchers can be built using
this option, and this option can be used multiple times to
build multiple additional launchers.
--arguments

Options for creating the application package:
--about-url
URL of the application's home page
--app-image
Location of the predefined application image that is used
to build an installable package
(absolute path or relative to the current directory)
--file-associations
Path to a Properties file that contains list of key, value pairs
(absolute path or relative to the current directory)
The keys "extension", "mime-type", "icon", and "description"
can be used to describe the association.
This option can be used multiple times.
--install-dir
Absolute path of the installation directory of the application
--license-file
Path to the license file
(absolute path or relative to the current directory)
--resource-dir
Path to override jpackage resources
Icons, template files, and other resources of jpackage can be
over-ridden by adding replacement resources to this directory.
(absolute path or relative to the current directory)
--runtime-image
Path of the predefined runtime image to install
(absolute path or relative to the current directory)
Option is required when creating a runtime package.

Platform dependent options for creating the application package:
--linux-package-name
Name for Linux package, defaults to the application name
--linux-deb-maintainer
Maintainer for .deb package
--linux-menu-group
Menu group this application is placed in
--linux-package-deps
Required packages or capabilities for the application
--linux-rpm-license-type
Type of the license ("License: " of the RPM .spec)
--linux-app-release
Release value of the RPM .spec file or
Debian revision value of the DEB control file
--linux-app-category
Group value of the RPM .spec file or
Section value of DEB control file
--linux-shortcut
Creates a shortcut for the application.

~/downloads $

alone. (The ASCII tab character should also be included for good
measure in a production script.)

At this point, we have data consisting of words separated by blank
space. The words only contain alphanumeric characters (and the
underscore). The next step is break the data apart so that we have one
word per line. This makes the counting operation much easier, as we
will see shortly.

 $ tr '[:upper:]' '[:lower:]' < whats.gnu | tr -cd '[:alnum:]_ \n' |
 > tr -s ' ' '\n' | ...

This command turns blanks into newlines. The ‘-s’ option squeezes
multiple newline characters in the output into just one, removing blank lines. (The ‘>’ is the shell’s “secondary prompt.” This is what the
shell prints when it notices you haven’t finished typing in all of a
command.)

We now have data consisting of one word per line, no punctuation, all
one case. We’re ready to count each word:

 $ tr '[:upper:]' '[:lower:]' < whats.gnu | tr -cd '[:alnum:]_ \n' |
 > tr -s ' ' '\n' | sort | uniq -c | ...

At this point, the data might look something like this:

      60 a
       2 able
       6 about
       1 above
       2 accomplish
       1 acquire
       1 actually
       2 additional

The output is sorted by word, not by count! What we want is the most
frequently used words first. Fortunately, this is easy to accomplish,
with the help of two more ‘sort’ options:

‘-n’
do a numeric sort, not a textual one

‘-r’
reverse the order of the sort

The final pipeline looks like this:

 $ tr '[:upper:]' '[:lower:]' < whats.gnu | tr -cd '[:alnum:]_ \n' |
 > tr -s ' ' '\n' | sort | uniq -c | sort -n -r
 ⊣    156 the
 ⊣     60 a
 ⊣     58 to
 ⊣     51 of
 ⊣     51 and
 ...

Whew! That’s a lot to digest. Yet, the same principles apply. With
six commands, on two lines (really one long one split for convenience),
we’ve created a program that does something interesting and useful, in
much less time than we could have written a C program to do the same
thing.

A minor modification to the above pipeline can give us a simple
spelling checker! To determine if you’ve spelled a word correctly, all
you have to do is look it up in a dictionary. If it is not there, then
chances are that your spelling is incorrect. So, we need a dictionary.
The conventional location for a dictionary is ‘/usr/share/dict/words’.

Now, how to compare our file with the dictionary? As before, we
generate a sorted list of words, one per line:

-----Info: (coreutils)Putting the tools together, 317 lines --60%------------------

notes and collecting material for the -app