neulab/tldr huggingface dataset:
-c, --cache-file cachefile Read from cachefile instead of reading from the default cache file (see the CONFIGURATION FILE section for more details). If you want to start with a clean cache (i.e., don’t report devices previously scanned but not necessarily available at this time), specify /dev/null.
-d, --no-encoding Don’t encode non-printing characters. The non-printing characters are encoded by ^ and M- notation by default. Note that the --output udev output format uses a different encoding which cannot be disabled.
-D, --no-part-details Don’t print information (PART_ENTRY_* tags) from partition table in low-level probing mode.
-g, --garbage-collect Perform a garbage collection pass on the blkid cache to remove devices which no longer exist.
-H, --hint setting Set probing hint. The hints are optional way how to force probing functions to check for example another location. The currently supported is "session_offset=number" to set session offset on multi-session UDF.
-i, --info Display information about I/O Limits (aka I/O topology). The 'export' output format is automatically enabled. This option can be used together with the --probe option.
-k, --list-filesystems List all known filesystems and RAIDs and exit.
-l, --list-one Look up only one device that matches the search parameter specified with the --match-token option. If there are multiple devices that match the specified search parameter, then the device with the highest priority is returned, and/or the first device found at a given priority (but see below note about udev). Device types in order of decreasing priority are: Device Mapper, EVMS, LVM, MD, and finally regular block devices. If this option is not specified, blkid will print all of the devices that match the search parameter.
This option forces blkid to use udev when used for LABEL or UUID tokens in --match-token. The goal is to provide output consistent with other utils (like mount(8), etc.) on systems where the same tag is used for multiple devices.
-L, --label label Look up the device that uses this filesystem label; this is equal to --list-one --output device --match-token LABEL=label. This lookup method is able to reliably use /dev/disk/by-label udev symlinks (dependent on a setting in /etc/blkid.conf). Avoid using the symlinks directly; it is not reliable to use the symlinks without verification. The --label option works on systems with and without udev.
Unfortunately, the original blkid(8) from e2fsprogs uses the -L option as a synonym for -o list. For better portability, use -l -o device -t LABEL=label and -o list in your scripts rather than the -L option.
-n, --match-types list Restrict the probing functions to the specified (comma-separated) list of superblock types (names). The list items may be prefixed with "no" to specify the types which should be ignored. For example:
blkid --probe --match-types vfat,ext3,ext4 /dev/sda1
probes for vfat, ext3 and ext4 filesystems, and
blkid --probe --match-types nominix /dev/sda1
probes for all supported formats except minix filesystems. This option is only useful together with --probe.
-o, --output format Use the specified output format. Note that the order of variables and devices is not fixed. See also option -s. The format parameter may be:
full print all tags (the default)
value print the value of the tags
list print the devices in a user-friendly format; this output format is unsupported for low-level probing (--probe or --info).
This output format is DEPRECATED in favour of the lsblk(8) command.
device print the device name only; this output format is always enabled for the --label and --uuid options
udev print key="value" pairs for easy import into the udev environment; the keys are prefixed by ID_FS_ or ID_PART_ prefixes. The value may be modified to be safe for udev environment; allowed is plain ASCII, hex-escaping and valid UTF-8, everything else (including whitespaces) is replaced with '_'. The keys with _ENC postfix use hex-escaping for unsafe chars.
The udev output returns the ID_FS_AMBIVALENT tag if more superblocks are detected, and ID_PART_ENTRY_* tags are always returned for all partitions including empty partitions.
This output format is DEPRECATED.
export print key=value pairs for easy import into the environment; this output format is automatically enabled when I/O Limits (--info option) are requested.
The non-printing characters are encoded by ^ and M- notation and all potentially unsafe characters are escaped.
-O, --offset offset Probe at the given offset (only useful with --probe). This option can be used together with the --info option.
-p, --probe Switch to low-level superblock probing mode (bypassing the cache).
Note that low-level probing also returns information about partition table type (PTTYPE tag) and partitions (PART_ENTRY_* tags). The tag names produced by low-level probing are based on names used internally by libblkid and it may be different than when executed without --probe (for example PART_ENTRY_UUID= vs PARTUUID=). See also --no-part-details.
-s, --match-tag tag For each (specified) device, show only the tags that match tag. It is possible to specify multiple --match-tag options. If no tag is specified, then all tokens are shown for all (specified) devices. In order to just refresh the cache without showing any tokens, use --match-tag none with no other options.
-S, --size size Override the size of device/file (only useful with --probe).
-t, --match-token NAME=value Search for block devices with tokens named NAME that have the value value, and display any devices which are found. Common values for NAME include TYPE, LABEL, and UUID. If there are no devices specified on the command line, all block devices will be searched; otherwise only the specified devices are searched.
-u, --usages list Restrict the probing functions to the specified (comma-separated) list of "usage" types. Supported usage types are: filesystem, raid, crypto and other. The list items may be prefixed with "no" to specify the usage types which should be ignored. For example:
blkid --probe --usages filesystem,other /dev/sda1
probes for all filesystem and other (e.g., swap) formats, and
blkid --probe --usages noraid /dev/sda1
probes for all supported formats except RAIDs. This option is only useful together with --probe.
-U, --uuid uuid Look up the device that uses this filesystem uuid. For more details see the --label option.
If the specified device or device addressed by specified token (option --match-token) was found and it’s possible to gather any information about the device, an exit status 0 is returned. Note the option --match-tag filters output tags, but it does not affect exit status.
If the specified token was not found, or no (specified) devices could be identified, or it is impossible to gather any information about the device identifiers or device content an exit status of 2 is returned.
For usage or other errors, an exit status of 4 is returned.
If an ambivalent probing result was detected by low-level probing mode (-p), an exit status of 8 is returned.
The standard location of the /etc/blkid.conf config file can be overridden by the environment variable BLKID_CONF. The following options control the libblkid library:
SEND_UEVENT=<yes|not> Sends uevent when /dev/disk/by-{label,uuid,partuuid,partlabel}/ symlink does not match with LABEL, UUID, PARTUUID or PARTLABEL on the device. Default is "yes".
CACHE_FILE=<path> Overrides the standard location of the cache file. This setting can be overridden by the environment variable BLKID_FILE. Default is /run/blkid/blkid.tab, or /etc/blkid.tab on systems without a /run directory.
EVALUATE=<methods> Defines LABEL and UUID evaluation method(s). Currently, the libblkid library supports the "udev" and "scan" methods. More than one method may be specified in a comma-separated list. Default is "udev,scan". The "udev" method uses udev /dev/disk/by-* symlinks and the "scan" method scans all block devices from the /proc/partitions file.
Setting LIBBLKID_DEBUG=all enables debug output.
blkid was written by Andreas Dilger for libblkid and improved by Theodore Ts’o and Karel Zak.
libblkid(3), findfs(8), lsblk(8), wipefs(8)
The blkid command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
NPROC(1)                          User Commands                         NPROC(1)
nproc - print the number of processing units available
nproc [OPTION]...
Print the number of processing units available to the current process, which may be less than the number of online processors
--all  print the number of installed processors
--ignore=N if possible, exclude N processing units
Written by Giuseppe Scrivano.
Full documentation <https://www.gnu.org/software/coreutils/nproc> or available locally via: info '(coreutils) nproc invocation'
lpstat(1)                         OpenPrinting                         lpstat(1)
lpstat - print cups status information
lpstat [ -E ] [ -H ] [ -U username ] [ -h hostname[:port] ] [ -l ] [ -W which-jobs ] [ -a [ destination(s) ] ] [ -c [ class(es) ] ] [ -d ] [ -e ] [ -o [ destination(s) ] ] [ -p [ printer(s) ] ] [ -r ] [ -R ] [ -s ] [ -t ] [ -u [ user(s) ] ] [ -v [ printer(s) ] ]
lpstat displays status information about the current classes, jobs, and printers.  When run with no arguments, lpstat will list active jobs queued by the current user.
The lpstat command supports the following options:
-H   Shows the server hostname and port.
-R   Shows the ranking of print jobs.
-W which-jobs Specifies which jobs to show, "completed" or "not-completed" (the default).  This option must appear before the -o option and/or any printer names, otherwise the default ("not-completed") value will be used in the request to the scheduler.
-a [printer(s)] Shows the accepting state of printer queues.  If no printers are specified then all printers are listed.
-c [class(es)] Shows the printer classes and the printers that belong to them.  If no classes are specified then all classes are listed.
-d   Shows the current default destination.
-e   Shows all available destinations on the local network.
-h server[:port] Specifies an alternate server.
-l   Shows a long listing of printers, classes, or jobs.
-o [destination(s)] Shows the jobs queued on the specified destinations.  If no destinations are specified all jobs are shown.
-p [printer(s)] Shows the printers and whether they are enabled for printing.  If no printers are specified then all printers are listed.
-r   Shows whether the CUPS server is running.
-s   Shows a status summary, including the default destination, a list of classes and their member printers, and a list of printers and their associated devices.  This is equivalent to using the -d, -c, and -v options.
-t   Shows all status information.  This is equivalent to using the -r, -d, -c, -v, -a, -p, and -o options.
-u [user(s)] Shows a list of print jobs queued by the specified users.  If no users are specified, lists the jobs queued by the current user.
-v [printer(s)] Shows the printers and what device they are attached to.  If no printers are specified then all printers are listed.
Unlike the System V printing system, CUPS allows printer names to contain any printable character except SPACE, TAB, "/", and "#".  Also, printer and class names are not case-sensitive.
The -h, -e, -E, -U, and -W options are unique to CUPS.
The Solaris -f, -P, and -S options are silently ignored.
cancel(1), lp(1), lpq(1), lpr(1), lprm(1), CUPS Online Help (http://localhost:631/help)
DNSRECON(1)              dnsrecon - DNS Enumeration Tool             DNSRECON(1)
dnsrecon - DNS Enumueration and Scanning Tool
dnsrecon <options>
-d, --domain      <domain> Domain to Target for enumeration.
-r, --range       <range> IP Range for reverse look-up brute force in formats (first-last) or in (range/bitmask).
-n, --name_server <name> Domain server to use, if none is given the SOA of the target will be used
-D, --dictionary  <file> Dictionary file of sub-domain and hostnames to use for brute force.
-f     Filter out of Brute Force Domain lookup records that resolve to the wildcard defined IP Address when saving records.
-t, --type        <types>
Specify the type of enumeration to perform (comma separated): std      To Enumerate general record types, enumerates. SOA, NS, A, AAAA, MX and SRV if AXRF on the NS Servers fail. rvl      To Reverse Look Up a given CIDR IP range.
brt      To Brute force Domains and Hosts using a given dictionary.
srv      To Enumerate common SRV Records for a given domain.
axfr     Test all NS Servers in a domain for misconfigured zone transfers.
goo      Perform Google search for sub-domains and hosts.
bing     Perform Bing search for sub-domains and hosts.
crt      Perform crt.sh search for subdomains and hosts.
snoop    To Perform a Cache Snooping against all NS servers for a given domain, testing all with file containing the domains, file given with -D option.
tld      Will remove the TLD of given domain and test against all TLD's registered in IANA
zonewalk Will perform a DNSSEC Zone Walk using NSEC Records. -a          Perform AXFR with the standard enumeration.
-s          Perform Reverse Look-up of ipv4 ranges in the SPF Record of the targeted domain with the standard enumeration.
-g          Perform Google enumeration with the standard enumeration.
-b       Perform Bing enumeration with the standard enumeration.
-k       Perform crt.sh enumeration with standard enumeration.
-w          Do deep whois record analysis and reverse look-up of IP ranges found thru whois when doing standard query.
-z          Performs a DNSSEC Zone Walk with the standard enumeration.
--threads    <number> Number of threads to use in Range Reverse Look-up, Forward Look-up Brute force and SRV Record Enumeration
--lifetime  <number> Time to wait for a server to response to a query.
--db        <file>   SQLite 3 file to save found records.
--xml       <file>   XML File to save found records.
--iw                 Continue brute forcing a domain even if a wildcard records are discovered.
-c, --csv   <file>   Comma separated value file.
-j, --json  <file>   JSON file.
-v          Show attempts in the bruteforce modes.
I wrote this tool back in late 2006 and it has been my favorite tool for enumeration thru DNS, in great part because I wrote it and it gives the output in a way that I can manipulate it in my own style.  One of the features that I used the most and gave me excellent results is the SRV record enumeration.
The script will perform the following: Standard Record Enumeration for a given domain (A, NS, SOA and MX). Top Leven Domain Expansion for a given domain.  Zone Transfer against all NS records of a given domain.  Reverse Lookup against a given IP Range given a start and end IP.
SRV Record enumeration, enumerating: _gc._tcp. _kerberos._tcp. _kerberos._udp. _ldap._tcp. _test._tcp. _sips._tcp. _sip._udp. _sip._tcp. _aix._tcp. _aix._tcp. _finger._tcp. _ftp._tcp. _http._tcp. _nntp._tcp. _telnet._tcp. _whois._tcp. _h323cs._tcp. _h323cs._udp. _h323be._tcp. _h323be._udp. _h323ls._tcp. _h323ls._udp.
Brute force hostnames and subdomains of a given target domain using a wordlist.
Carlos Perez, Carlos_Perez@darkoperator.com
Copyright (C) 2012 Carlos Perez
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; Applies version 2 of the License.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
lspci(8)                        The PCI Utilities                       lspci(8)
lspci - list all PCI devices
lspci [options]
lspci is a utility for displaying information about PCI buses in the system and devices connected to them.
By default, it shows a brief list of devices. Use the options described below to request either a more verbose output or output intended for parsing by other programs.
If you are going to report bugs in PCI device drivers or in lspci itself, please include output of "lspci -vvx" or even better "lspci -vvxxx" (however, see below for possible caveats).
Some parts of the output, especially in the highly verbose modes, are probably intelligible only to experienced PCI hackers. For exact definitions of the fields, please consult either the PCI specifications or the header.h and /usr/include/linux/pci.h include files.
Access to some parts of the PCI configuration space is restricted to root on many operating systems, so the features of lspci available to normal users are limited. However, lspci tries its best to display as much as available and mark all other information with <access denied> text.
Basic display modes -m     Dump PCI device data in a backward-compatible machine readable form.  See below for details.
-mm    Dump PCI device data in a machine readable form for easy parsing by scripts.  See below for details.
-t     Show a tree-like diagram containing all buses, bridges, devices and connections between them.
Display options -v     Be verbose and display detailed information about all devices.
-vv    Be very verbose and display more details. This level includes everything deemed useful.
-vvv   Be even more verbose and display everything we are able to parse, even if it doesn't look interesting at all (e.g., undefined memory regions).
-k     Show kernel drivers handling each device and also kernel modules capable of handling it.  Turned on by default when -v is given in the normal mode of output.  (Currently works only on Linux with kernel 2.6 or newer.)
-x     Show hexadecimal dump of the standard part of the configuration space (the first 64 bytes or 128 bytes for CardBus bridges).
-xxx   Show hexadecimal dump of the whole PCI configuration space. It is available only to root as several PCI devices crash when you try to read some parts of the config space (this behavior probably doesn't violate the PCI standard, but it's at least very stupid). However, such devices are rare, so you needn't worry much.
-xxxx  Show hexadecimal dump of the extended (4096-byte) PCI configuration space available on PCI-X 2.0 and PCI Express buses.
-b     Bus-centric view. Show all IRQ numbers and addresses as seen by the cards on the PCI bus instead of as seen by the kernel.
-D     Always show PCI domain numbers. By default, lspci suppresses them on machines which have only domain 0.
-P     Identify PCI devices by path through each bridge, instead of by bus number.
-PP    Identify PCI devices by path through each bridge, showing the bus number as well as the device number.
Options to control resolving ID's to names -n     Show PCI vendor and device codes as numbers instead of looking them up in the PCI ID list.
-nn    Show PCI vendor and device codes as both numbers and names.
-q     Use DNS to query the central PCI ID database if a device is not found in the local pci.ids file. If the DNS query succeeds, the result is cached in ~/.pciids-cache and it is recognized in subsequent runs even if -q is not given any more. Please use this switch inside automated scripts only with caution to avoid overloading the database servers.
-qq    Same as -q, but the local cache is reset.
-Q     Query the central database even for entries which are recognized locally.  Use this if you suspect that the displayed entry is wrong.
Options for selection of devices -s [[[[<domain>]:]<bus>]:][<device>][.[<func>]] Show only devices in the specified domain (in case your machine has several host bridges, they can either share a common bus number space or each of them can address a PCI domain of its own; domains are numbered from 0 to ffff), bus (0 to ff), device (0 to 1f) and function (0 to 7).  Each component of the device address can be omitted or set to "*", both meaning "any value". All numbers are hexadecimal.  E.g., "0:" means all devices on bus 0, "0" means all functions of device 0 on any bus, "0.3" selects third function of device 0 on all buses and ".4" shows only the fourth function of each device.
-d [<vendor>]:[<device>][:<class>] Show only devices with specified vendor, device and class ID. The ID's are given in hexadecimal and may be omitted or given as "*", both meaning "any value".
Other options -i <file> Use <file> as the PCI ID list instead of /usr/share/hwdata/pci.ids.
-p <file> Use <file> as the map of PCI ID's handled by kernel modules. By default, lspci uses /lib/modules/kernel_version/modules.pcimap. Applies only to Linux systems with recent enough module tools.
-M     Invoke bus mapping mode which performs a thorough scan of all PCI devices, including those behind misconfigured bridges, etc. This option gives meaningful results only with a direct hardware access mode, which usually requires root privileges.  Please note that the bus mapper only scans PCI domain 0.
--version Shows lspci version. This option should be used stand-alone.
PCI access options The PCI utilities use the PCI library to talk to PCI devices (see pcilib(7) for details). You can use the following options to influence its behavior:
-A <method> The library supports a variety of methods to access the PCI hardware.  By default, it uses the first access method available, but you can use this option to override this decision. See -A help for a list of available methods and their descriptions.
-O <param>=<value> The behavior of the library is controlled by several named parameters.  This option allows to set the value of any of the parameters. Use -O help for a list of known parameters and their default values.
-H1    Use direct hardware access via Intel configuration mechanism 1. (This is a shorthand for -A intel-conf1.)
-H2    Use direct hardware access via Intel configuration mechanism 2. (This is a shorthand for -A intel-conf2.)
-F <file> Instead of accessing real hardware, read the list of devices and values of their configuration registers from the given file produced by an earlier run of lspci -x.  This is very useful for analysis of user-supplied bug reports, because you can display the hardware configuration in any way you want without disturbing the user with requests for more dumps.
-G     Increase debug level of the library.
If you intend to process the output of lspci automatically, please use one of the machine-readable output formats (-m, -vm, -vmm) described in this section. All other formats are likely to change between versions of lspci.
All numbers are always printed in hexadecimal. If you want to process numeric ID's instead of names, please add the -n switch.
Simple format (-m) In the simple format, each device is described on a single line, which is formatted as parameters suitable for passing to a shell script, i.e., values separated by whitespaces, quoted and escaped if necessary.  Some of the arguments are positional: slot, class, vendor name, device name, subsystem vendor name and subsystem name (the last two are empty if the device has no subsystem); the remaining arguments are option-like:
-rrev  Revision number.
-pprogif Programming interface.
The relative order of positional arguments and options is undefined.  New options can be added in future versions, but they will always have a single argument not separated from the option by any spaces, so they can be easily ignored if not recognized.
Verbose format (-vmm) The verbose output is a sequence of records separated by blank lines. Each record describes a single device by a sequence of lines, each line containing a single `tag: value' pair. The tag and the value are separated by a single tab character.  Neither the records nor the lines within a record are in any particular order.  Tags are case-sensitive.
The following tags are defined:
Slot   The name of the slot where the device resides ([domain:]bus:device.function).  This tag is always the first in a record.
Class  Name of the class.
Vendor Name of the vendor.
Device Name of the device.
SVendor Name of the subsystem vendor (optional).
SDevice Name of the subsystem (optional).
PhySlot The physical slot where the device resides (optional, Linux only).
Rev    Revision number (optional).
ProgIf Programming interface (optional).
Driver Kernel driver currently handling the device (optional, Linux only).
Module Kernel module reporting that it is capable of handling the device (optional, Linux only). Multiple lines with this tag can occur.
NUMANode NUMA node this device is connected to (optional, Linux only).
IOMMUGroup IOMMU group that this device is part of (optional, Linux only).
New tags can be added in future versions, so you should silently ignore any tags you don't recognize.
Backward-compatible verbose format (-vm) In this mode, lspci tries to be perfectly compatible with its old versions.  It's almost the same as the regular verbose format, but the Device tag is used for both the slot and the device name, so it occurs twice in a single record. Please avoid using this format in any new code.
/usr/share/hwdata/pci.ids A list of all known PCI ID's (vendors, devices, classes and subclasses). Maintained at https://pci-ids.ucw.cz/, use the update-pciids utility to download the most recent version.
/usr/share/hwdata/pci.ids.gz If lspci is compiled with support for compression, this file is tried before pci.ids.
~/.pciids-cache All ID's found in the DNS query mode are cached in this file.
Sometimes, lspci is not able to decode the configuration registers completely.  This usually happens when not enough documentation was available to the authors.  In such cases, it at least prints the <?> mark to signal that there is potentially something more to say. If you know the details, patches will be of course welcome.
Access to the extended configuration space is currently supported only by the linux_sysfs back-end.
setpci(8), pci.ids(5), update-pciids(8), pcilib(7)
The PCI Utilities are maintained by Martin Mares <mj@ucw.cz>.
SCREENFETCH(1)                    User Commands                   SCREENFETCH(1)
screenFetch - The Bash Screenshot Information Tool
screenfetch [OPTIONAL FLAGS]
This handy Bash script can be used to generate one of those nifty terminal theme information + ASCII distribution logos you see in everyone's screenshots nowadays. It will auto-detect your distribution and display an ASCII version of that distribution's logo and some valuable information to the right. There are options to specify no ASCII art, colors, taking a screenshot upon displaying info, and even customizing the screenshot command!  This script is very easy to add to and can easily be extended.
Supported GNU/Linux Distributions:
ALDOS, Alpine Linux, Amazon Linux, Antergos, Arch Linux (Old and Current Logos), Artix Linux, blackPanther OS, BLAG, BunsenLabs, CentOS, Chakra, Chapeau, Chrome OS, Chromium OS, CrunchBang, CRUX, Debian, Deepin, DesaOS, Devuan, Dragora, elementary OS, Evolve OS, Exherbo, Fedora, Frugalware, Fuduntu, Funtoo, Fux, Gentoo, gNewSense, Guix System, Hyperbola GNU/Linux-libre, Jiyuu Linux, Kali Linux, KaOS, KDE neon, Kogaion, Korora, LinuxDeepin, Linux Mint, LMDE, Logos, Mageia, Mandriva/Mandrake, Manjaro, Mer, Netrunner, NixOS, OBRevenge, openSUSE, OS Elbrus, Oracle Linux, Parabola GNU/Linux-libre, Pardus, Parrot Security, PCLinuxOS, PeppermintOS, Proxmox VE, PureOS, Qubes OS, Raspbian, Red Hat Enterprise Linux, ROSA, Sabayon, SailfishOS, Scientific Linux, Siduction, Slackware, Solus, Source Mage GNU/Linux, SparkyLinux, SteamOS, SUSE Linux Enterprise, SwagArch, TinyCore, Trisquel, Ubuntu, Viperr, Void and Zorin OS.
Other Supported Systems:
Dragonfly/Free/Open/Net BSD, Haiku, Mac OS X, Windows+Cygwin and Windows+MSYS2.
Supported Desktop Managers:
KDE, GNOME, Unity, Xfce, LXDE, Cinnamon, MATE, Deepin, CDE, RazorQt and Trinity.
Supported Window Managers:
2bwm, 9wm, Awesome, Beryl, Blackbox, Cinnamon, chromeos-wm, Compiz, deepin-wm, dminiwm, dwm, dtwm, E16, E17, echinus, Emerald, FluxBox, FLWM, FVWM, herbstluftwm, howm, IceWM, KWin, Metacity, monsterwm, Musca, Gala, Mutter, Muffin, Notion, OpenBox, PekWM, Ratpoison, Sawfish, ScrotWM, SpectrWM, StumpWM, subtle, sway, TWin, WindowMaker, WMFS, wmii, Xfwm4, XMonad and i3.
-o 'OPTIONS' Allows for setting script variables on the command line. Must be in the following format: 'OPTION1="OPTIONARG1";OPTION2="OPTIONARG2"'
-d '+var;-var;var' Allows for setting what information is displayed on the command line. You can add displays with +var,var.  You can delete displays with -var,var. Setting without + or - will set display to that explicit combination. Add and delete statements may be used in conjunction by placing a ; between them as so: +var,var,var;-var,var.
-n     Do not display ASCII distribution logo.
-L     Display ASCII distribution logo only.
-N     Strip all color from output.
-w     Wrap long lines.
-t     Truncate output based on terminal width (Experimental!).
-p     Output in portrait mode, with logo above info.
-s [-u IMGHOST] Using this flag tells the script that you want it to take a screenshot. Use the -u flag if you would like to upload the screenshots to one of the pre-configured locations. These include: teknik, imgur, mediacrush and hmp.
-c string You may change the outputted colors with -c. The format is as follows: [0-9][0-9],[0-9][0-9]. The first argument controls the ASCII logo colors and the label colors. The second argument controls the colors of the information found. One argument may be used without the other.
-a 'PATH' You can specify a custom ASCII art by passing the path to a Bash script, defining startline and fulloutput variables, and optionally labelcolor and textcolor. See the asciiText function in the source code for more information on the variables format.
-S 'COMMAND' Here you can specify a custom screenshot command for the script to execute. Surrounding quotes are required.
-D 'DISTRO' Here you can specify your distribution for the script to use. Surrounding quotes are required.
-A 'DISTRO' Here you can specify the distribution art that you want displayed. This is for when you want your distro detected but want to display a different logo.
-E     Suppress output of errors.
-V, --version Display current script version.
-h, --help Display this help.
http://github.com/KittyKatt/screenFetch
Created by and licensed to Brett Bohnenkamper <kittykatt@kittykatt.us>. OS X porting done almost solely by shrx <https://github.com/shrx> and John D. Duncan, III <https://github.com/JohnDDuncanIII>.
This manual page was written by djcj <djcj@gmx.de>
Report bugs to <https://github.com/KittyKatt/screenFetch/issues>
This is free software; you can redistribute it and/or modify it under the terms of the GNU GPL version 3 or (at your option) any later version. There is NO warranty; not even MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
GIT-DELTA(1)                       Git Extras                       GIT-DELTA(1)
git-delta - Lists changed files
git-delta [<branch>] [<filter>]
Lists all files that differ from a branch. By default, lists files that have been added, copied, or modified as compared to the master branch.
Lists all modified and renamed files vs. master:
$ git delta master MR
Lists all deleted files vs. example:
$ git delta example D
Written by Ivan Malopinsky <hello@imsky.co>
wasm-objdump â€” print information about a wasm binary
wasm-objdump [options] file ...
wasm-objdump prints information about a wasm binary, similar to objdump.
-h, --headers Print headers
-j, --section=SECTION Select just one section
-s, --full-contents Print raw section contents
-d, --disassemble Disassemble function bodies
--debug Print extra debug information
-x, --details Show section details
-r, --reloc Show relocations inline with disassembly
$ wasm-objdump test.wasm
wasm-interp(1), wasm-opcodecnt(1), wasm-strip(1), wasm-validate(1), wasm2c(1), wasm2wat(1), wast2json(1), wat-desugar(1), wat2wasm(1), spectest-interp(1)
evhttp_request(3)           Library Functions Manual           evhttp_request(3)
evhttp_request -
the request structure that a server receives.
#include <evhttp.h>
Data Fields void(* cb )(struct evhttp_request *, void *) void * cb_arg void(* chunk_cb )(struct evhttp_request *, void *) int chunked struct evhttp_connection * evcon int flags struct evbuffer * input_buffer struct evkeyvalq * input_headers enum evhttp_request_kind kind char major char minor struct { struct evhttp_request * tqe_next struct evhttp_request ** tqe_prev } next ev_int64_t ntoread struct evbuffer * output_buffer struct evkeyvalq * output_headers char * remote_host u_short remote_port int response_code char * response_code_line enum evhttp_cmd_type type char * uri
Detailed Description the request structure that a server receives.
WARNING: expect this structure to change. I will try to provide reasonable accessors.
Author Generated automatically by Doxygen for libevent from the source code.
LOGGER(1)                         User Commands                        LOGGER(1)
logger - enter messages into the system log
logger [options] message
logger makes entries in the system log.
When the optional message argument is present, it is written to the log. If it is not present, and the -f option is not given either, then standard input is logged.
-d, --udp Use datagrams (UDP) only. By default the connection is tried to the syslog port defined in /etc/services, which is often 514.
See also --server and --socket to specify where to connect.
-e, --skip-empty Ignore empty lines when processing files. An empty line is defined to be a line without any characters. Thus a line consisting only of whitespace is NOT considered empty. Note that when the --prio-prefix option is specified, the priority is not part of the line. Thus an empty line in this mode is a line that does not have any characters after the priority prefix (e.g., <13>).
-f, --file file Log the contents of the specified file. This option cannot be combined with a command-line message.
-i Log the PID of the logger process with each line.
--id[=id] Log the PID of the logger process with each line. When the optional argument id is specified, then it is used instead of the logger command’s PID. The use of --id=$$ (PPID) is recommended in scripts that send several messages.
Note that the system logging infrastructure (for example systemd when listening on /dev/log) may follow local socket credentials to overwrite the PID specified in the message. logger(1) is able to set those socket credentials to the given id, but only if you have root permissions and a process with the specified PID exists, otherwise the socket credentials are not modified and the problem is silently ignored.
--journald[=file] Write a systemd journal entry. The entry is read from the given file, when specified, otherwise from standard input. Each line must begin with a field that is accepted by journald; see systemd.journal-fields(7) for details. The use of a MESSAGE_ID field is generally a good idea, as it makes finding entries easy. Examples:
logger --journald <<end MESSAGE_ID=67feb6ffbaf24c5cbec13c008dd72309 MESSAGE=The dogs bark, but the caravan goes on. DOGS=bark CARAVAN=goes on end
logger --journald=entry.txt
Notice that --journald will ignore values of other options, such as priority. If priority is needed it must be within input, and use PRIORITY field. The simple execution of journalctl(1) will display MESSAGE field. Use journalctl --output json-pretty to see rest of the fields.
+ To include newlines in MESSAGE, specify MESSAGE several times. This is handled as a special case, other fields will be stored as an array in the journal if they appear multiple times.
--msgid msgid Sets the RFC 5424 <https://tools.ietf.org/html/rfc5424> MSGID field. Note that the space character is not permitted inside of msgid. This option is only used if --rfc5424 is specified as well; otherwise, it is silently ignored.
-n, --server server Write to the specified remote syslog server instead of to the system log socket. Unless --udp or --tcp is specified, logger will first try to use UDP, but if this fails a TCP connection is attempted.
--no-act Causes everything to be done except for writing the log message to the system log, and removing the connection or the journal. This option can be used together with --stderr for testing purposes.
--octet-count Use the RFC 6587 <https://tools.ietf.org/html/rfc6587> octet counting framing method for sending messages. When this option is not used, the default is no framing on UDP, and RFC6587 non-transparent framing (also known as octet stuffing) on TCP.
-P, --port port Use the specified port. When this option is not specified, the port defaults to syslog for udp and to syslog-conn for tcp connections.
-p, --priority priority Enter the message into the log with the specified priority. The priority may be specified numerically or as a facility.level pair. For example, -p local3.info logs the message as informational in the local3 facility. The default is user.notice.
--prio-prefix Look for a syslog prefix on every line read from standard input. This prefix is a decimal number within angle brackets that encodes both the facility and the level. The number is constructed by multiplying the facility by 8 and then adding the level. For example, local0.info, meaning facility=16 and level=6, becomes <134>.
If the prefix contains no facility, the facility defaults to what is specified by the -p option. Similarly, if no prefix is provided, the line is logged using the priority given with -p.
This option doesn’t affect a command-line message.
--rfc3164 Use the RFC 3164 <https://tools.ietf.org/html/rfc3164> BSD syslog protocol to submit messages to a remote server.
--rfc5424[=without] Use the RFC 5424 <https://tools.ietf.org/html/rfc5424> syslog protocol to submit messages to a remote server. The optional without argument can be a comma-separated list of the following values: notq, notime, nohost.
The notq value suppresses the time-quality structured data from the submitted message. The time-quality information shows whether the local clock was synchronized plus the maximum number of microseconds the timestamp might be off. The time quality is also automatically suppressed when --sd-id timeQuality is specified.
The notime value (which implies notq) suppresses the complete sender timestamp that is in ISO-8601 format, including microseconds and timezone.
The nohost value suppresses gethostname(2) information from the message header.
The RFC 5424 protocol has been the default for logger since version 2.26.
-s, --stderr Output the message to standard error as well as to the system log.
--sd-id name[@digits] Specifies a structured data element ID for an RFC 5424 message header. The option has to be used before --sd-param to introduce a new element. The number of structured data elements is unlimited. The ID (name plus possibly @digits) is case-sensitive and uniquely identifies the type and purpose of the element. The same ID must not exist more than once in a message. The @digits part is required for user-defined non-standardized IDs.
logger currently generates the timeQuality standardized element only. RFC 5424 also describes the elements origin (with parameters ip, enterpriseId, software and swVersion) and meta (with parameters sequenceId, sysUpTime and language). These element IDs may be specified without the @digits suffix.
--sd-param name=value Specifies a structured data element parameter, a name and value pair. The option has to be used after --sd-id and may be specified more than once for the same element. Note that the quotation marks around value are required and must be escaped on the command line.
logger --rfc5424 --sd-id zoo@123             \ --sd-param tiger="hungry"   \ --sd-param zebra="running"  \ --sd-id manager@123         \ --sd-param onMeeting="yes"  \ "this is message"
produces:
<13>1 2015-10-01T14:07:59.168662+02:00 ws kzak - - [timeQuality tzKnown="1" isSynced="1" syncAccuracy="218616"][zoo@123 tiger="hungry" zebra="running"][manager@123 onMeeting="yes"] this is message
-S, --size size Sets the maximum permitted message size to size. The default is 1KiB characters, which is the limit traditionally used and specified in RFC 3164. With RFC 5424, this limit has become flexible. A good assumption is that RFC 5424 receivers can at least process 4KiB messages.
Most receivers accept messages larger than 1KiB over any type of syslog protocol. As such, the --size option affects logger in all cases (not only when --rfc5424 was used).
Note: the message-size limit limits the overall message size, including the syslog header. Header sizes vary depending on the selected options and the hostname length. As a rule of thumb, headers are usually not longer than 50 to 80 characters. When selecting a maximum message size, it is important to ensure that the receiver supports the max size as well, otherwise messages may become truncated. Again, as a rule of thumb two to four KiB message size should generally be OK, whereas anything larger should be verified to work.
--socket-errors[=mode] Print errors about Unix socket connections. The mode can be a value of off, on, or auto. When the mode is auto, then logger will detect if the init process is systemd(1), and if so assumption is made /dev/log can be used early at boot. Other init systems lack of /dev/log will not cause errors that is identical with messaging using openlog(3) system call. The logger(1) before version 2.26 used openlog, and hence was unable to detected loss of messages sent to Unix sockets.
The default mode is auto. When errors are not enabled lost messages are not communicated and will result to successful exit status of logger(1) invocation.
-T, --tcp Use stream (TCP) only. By default the connection is tried to the syslog-conn port defined in /etc/services, which is often 601.
-t, --tag tag Mark every line to be logged with the specified tag. The default tag is the name of the user logged in on the terminal (or a user name based on effective user ID).
-u, --socket socket Write to the specified socket instead of to the system log socket.
-- End the argument list. This allows the message to start with a hyphen (-).
The logger utility exits 0 on success, and >0 if an error occurs.
Valid facility names are:
auth authpriv for security information of a sensitive nature cron
daemon ftp kern cannot be generated from userspace process, automatically converted to user
lpr mail news syslog user uucp local0 to local7 security deprecated synonym for auth
Valid level names are:
emerg alert crit err warning notice info debug panic deprecated synonym for emerg error deprecated synonym for err warn deprecated synonym for warning
For the priority order and intended purposes of these facilities and levels, see syslog(3).
The logger command is expected to be IEEE Std 1003.2 ("POSIX.2") compatible.
logger System rebooted logger -p local0.notice -t HOSTIDM -f /dev/idmc logger -n loghost.example.com System rebooted
The logger command was originally written by University of California in 1983-1993 and later rewritten by Karel Zak <kzak@redhat.com>, Rainer Gerhards <rgerhards@adiscon.com>, and Sami Kerola <kerolasa@iki.fi>.
journalctl(1), syslog(3), systemd.journal-fields(7)
The logger command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
SSH(1)                     BSD General Commands Manual                    SSH(1)
ssh — OpenSSH remote login client
ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-B bind_interface] [-b bind_address] [-c cipher_spec] [-D [bind_address:]port] [-E log_file] [-e escape_char] [-F configfile] [-I pkcs11] [-i identity_file] [-J destination] [-L address] [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port] [-Q query_option] [-R address] [-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]] destination [command [argument ...]]
ssh (SSH client) is a program for logging into a remote machine and for executing commands on a remote machine.  It is intended to provide secure encrypted communications between two untrusted hosts over an insecure network.  X11 connections, arbitrary TCP ports and UNIX-domain sockets can also be forwarded over the secure channel.
ssh connects and logs into the specified destination, which may be specified as either [user@]hostname or a URI of the form ssh://[user@]hostname[:port].  The user must prove their identity to the remote machine using one of several methods (see below).
If a command is specified, it will be executed on the remote host instead of a login shell.  A complete command line may be specified as command, or it may have additional arguments.  If supplied, the arguments will be appended to the command, separated by spaces, before it is sent to the server to be executed.
-4      Forces ssh to use IPv4 addresses only.
-6      Forces ssh to use IPv6 addresses only.
-A      Enables forwarding of connections from an authentication agent such as ssh-agent(1).  This can also be specified on a per-host basis in a configuration file.
Agent forwarding should be enabled with caution.  Users with the ability to bypass file permissions on the remote host (for the agent's UNIX-domain socket) can access the local agent through the forwarded connection.  An attacker cannot obtain key material from the agent, however they can perform operations on the keys that enable them to authenticate using the identities loaded into the agent.  A safer alternative may be to use a jump host (see -J).
-a      Disables forwarding of the authentication agent connection.
-B bind_interface Bind to the address of bind_interface before attempting to connect to the destination host.  This is only useful on systems with more than one address.
-b bind_address Use bind_address on the local machine as the source address of the connection.  Only useful on systems with more than one address.
-C      Requests compression of all data (including stdin, stdout, stderr, and data for forwarded X11, TCP and UNIX-domain connections).  The compression algorithm is the same used by gzip(1).  Compression is desirable on modem lines and other slow connections, but will only slow down things on fast networks.  The default value can be set on a host-by-host basis in the configuration files; see the Compression option.
-c cipher_spec Selects the cipher specification for encrypting the session. cipher_spec is a comma-separated list of ciphers listed in order of preference.  See the Ciphers keyword in ssh_config(5) for more information.
-D [bind_address:]port Specifies a local “dynamic” application-level port forwarding. This works by allocating a socket to listen to port on the local side, optionally bound to the specified bind_address.  Whenever a connection is made to this port, the connection is forwarded over the secure channel, and the application protocol is then used to determine where to connect to from the remote machine.  Currently the SOCKS4 and SOCKS5 protocols are supported, and ssh will act as a SOCKS server.  Only root can forward privileged ports.  Dynamic port forwardings can also be specified in the configuration file.
IPv6 addresses can be specified by enclosing the address in square brackets.  Only the superuser can forward privileged ports.  By default, the local port is bound in accordance with the GatewayPorts setting.  However, an explicit bind_address may be used to bind the connection to a specific address.  The bind_address of “localhost” indicates that the listening port be bound for local use only, while an empty address or ‘*’ indicates that the port should be available from all interfaces.
-E log_file Append debug logs to log_file instead of standard error.
-e escape_char Sets the escape character for sessions with a pty (default: ‘~’). The escape character is only recognized at the beginning of a line. The escape character followed by a dot (‘.’) closes the connection; followed by control-Z suspends the connection; and followed by itself sends the escape character once.  Setting the character to “none” disables any escapes and makes the session fully transparent.
-F configfile Specifies an alternative per-user configuration file.  If a configuration file is given on the command line, the system-wide configuration file (/etc/ssh/ssh_config) will be ignored.  The default for the per-user configuration file is ~/.ssh/config.  If set to “none”, no configuration files will be read.
-f      Requests ssh to go to background just before command execution. This is useful if ssh is going to ask for passwords or passphrases, but the user wants it in the background.  This implies -n.  The recommended way to start X11 programs at a remote site is with something like ssh -f host xterm.