neulab/tldr huggingface dataset:
sendemail.multiEdit If true (default), a single editor instance will be spawned to edit files you have to edit (patches when --annotate is used, and the summary when --compose is used). If false, files will be edited one after the other, spawning a new editor each time.
sendemail.confirm Sets the default for whether to confirm before sending. Must be one of always, never, cc, compose, or auto. See --confirm in the previous section for the meaning of these values.
Use gmail as the smtp server To use git send-email to send your patches through the GMail SMTP server, edit ~/.gitconfig to specify your account settings:
[sendemail] smtpEncryption = tls smtpServer = smtp.gmail.com smtpUser = yourname@gmail.com smtpServerPort = 587
If you have multi-factor authentication set up on your Gmail account, you will need to generate an app-specific password for use with git send-email. Visit https://security.google.com/settings/security/apppasswords to create it.
If you do not have multi-factor authentication set up on your Gmail account, you will need to allow less secure app access. Visit https://myaccount.google.com/lesssecureapps to enable it.
Once your commits are ready to be sent to the mailing list, run the following commands:
$ git format-patch --cover-letter -M origin/master -o outgoing/ $ edit outgoing/0000-* $ git send-email outgoing/*
The first time you run it, you will be prompted for your credentials. Enter the app-specific or your regular password as appropriate. If you have credential helper configured (see git-credential(1)), the password will be saved in the credential store so you won’t have to type it the next time.
Note: the following core Perl modules that may be installed with your distribution of Perl are required: MIME::Base64, MIME::QuotedPrint, Net::Domain and Net::SMTP. These additional Perl modules are also required: Authen::SASL and Mail::Address.
git-format-patch(1), git-imap-send(1), mbox(5)
runit(8)                     System Manager's Manual                    runit(8)
runit - a UNIX process no 1
runit must be run as Unix process no 1.  It performs the system's booting, running, and shutdown in three stages:
STAGE 1 runit runs /etc/runit/1 and waits for it to terminate.  The system's one time tasks are done here.  /etc/runit/1 has full control of /dev/console to be able to start an emergency shell if the one time initialization tasks fail. If /etc/runit/1 crashes, or exits 100, runit will skip stage 2 and enter stage 3.
STAGE 2 runit runs /etc/runit/2, which should not return until system shutdown; if it crashes, or exits 111, it will be restarted.  Normally /etc/runit/2 starts runsvdir(8).  runit is able to handle the ctrl-alt-del keyboard request in stage 2, see below.
STAGE 3 If runit is told to shutdown the system, or stage 2 returns, it terminates stage 2 if it is running, and runs /etc/runit/3.  The systems tasks to shutdown and possibly halt or reboot the system are done here. If stage 3 returns, runit checks if the file /run/runit.reboot exists and has the execute by owner permission set.  If so, the system is rebooted, it's halted otherwise.  If /etc/runit/nosync exists, runit doesn't invoke sync(). This is useful in vservers.
CTRL-ALT-DEL If runit receives the ctrl-alt-del keyboard request and the file /etc/runit/ctrlaltdel exists and has the execute by owner permission set, runit runs /etc/runit/ctrlaltdel, waits for it to terminate, and then sends itself a CONT signal.
runit only accepts signals in stage 2.
If runit receives a CONT signal and the file /run/runit.stopit exists and has the execute by owner permission set, runit is told to shutdown the system.
If runit receives a PWR signal, runit is told to shutdown the system.
if runit receives an INT signal, a ctrl-alt-del keyboard request is triggered.
When the runitdir=name variable is set and runit is init, runit will check if a directory named name exists in /etc/runit/runsvdir/ and then will use runsvchdir to change the directory of runsvdir to name in place of the default.
If runitdir is set to runitdir=solo runit will use the solo directory for runsvdir and it will also refrain from start any sysv service that is enabled in /etc/rc2.d/ This is intended for use with containers that need to start only some selected services.
runit-init(8), runsvdir(8), runsvchdir(8), sv(8), runsv(8), chpst(8), utmpset(8), svlogd(8)
NODE(1)                    BSD General Commands Manual                   NODE(1)
node — server-side JavaScript runtime
node [options] [v8-options] [-e string | script.js | -] [--] [arguments ...] node inspect [-e string | script.js | - | <host>:<port>] ... node [--v8-options]
Node.js is a set of libraries for JavaScript which allows it to be used outside of the browser.  It is primarily focused on creating simple, easy- to-build network clients and servers.
Execute node without arguments to start a REPL.
-       Alias for stdin, analogous to the use of - in other command-line utilities.  The executed script is read from stdin, and remaining arguments are passed to the script.
--      Indicate the end of command-line options.  Pass the rest of the arguments to the script.
If no script filename or eval/print script is supplied prior to this, then the next argument will be used as a script filename.
--abort-on-uncaught-exception Aborting instead of exiting causes a core file to be generated for analysis.
--completion-bash Print source-able bash completion script for Node.js.
-C, --conditions string Use custom conditional exports conditions.  string
--cpu-prof Start the V8 CPU profiler on start up, and write the CPU profile to disk before exit. If --cpu-prof-dir is not specified, the profile will be written to the current working directory with a generated file name.
--cpu-prof-dir The directory where the CPU profiles generated by --cpu-prof will be placed.  The default value is controlled by the --diagnostic-dir.  command-line option.
--cpu-prof-interval The sampling interval in microseconds for the CPU profiles generated by --cpu-prof.  The default is 1000.
--cpu-prof-name File name of the V8 CPU profile generated with --cpu-prof.
--diagnostic-dir Set the directory for all diagnostic output files.  Default is current working directory.  Set the directory to which all diagnostic output files will be written to.  Defaults to current working directory.  Affects the default output directory of: --cpu-prof-dir.  --heap-prof-dir.  --redirect-warnings.
--disable-proto=mode Disable the `Object.prototype.__proto__` property. If mode is `delete`, the property will be removed entirely. If mode is `throw`, accesses to the property will throw an exception with the code `ERR_PROTO_ACCESS`.
--disallow-code-generation-from-strings Make built-in language features like `eval` and `new Function` that generate code from strings throw an exception instead. This does not affect the Node.js `vm` module.
--enable-fips Enable FIPS-compliant crypto at startup.  Requires Node.js to be built with ./configure --openssl-fips.
--enable-source-maps Enable Source Map V3 support for stack traces.
--experimental-import-meta-resolve Enable experimental ES modules support for import.meta.resolve().
--experimental-json-modules Enable experimental JSON interop support for the ES Module loader.
--experimental-loader=module Specify the module to use as a custom module loader.
--experimental-policy Use the specified file as a security policy.
--no-experimental-repl-await Disable top-level await keyword support in REPL.
--experimental-specifier-resolution Select extension resolution algorithm for ES Modules; either 'explicit' (default) or 'node'.
--experimental-vm-modules Enable experimental ES module support in VM module.
--experimental-wasi-unstable-preview1 Enable experimental WebAssembly System Interface support.
--experimental-wasm-modules Enable experimental WebAssembly module support.
--force-context-aware Disable loading native addons that are not context-aware.
--force-fips Force FIPS-compliant crypto on startup (Cannot be disabled from script code).  Same requirements as --enable-fips.
--frozen-intrinsics Enable experimental frozen intrinsics support.
--heapsnapshot-near-heap-limit=max_count Generate heap snapshot when the V8 heap usage is approaching the heap limit.  No more than the specified number of snapshots will be generated.
--heapsnapshot-signal=signal Generate heap snapshot on specified signal.
--heap-prof Start the V8 heap profiler on start up, and write the heap profile to disk before exit. If --heap-prof-dir is not specified, the profile will be written to the current working directory with a generated file name.
--heap-prof-dir The directory where the heap profiles generated by --heap-prof will be placed.  The default value is controlled by the --diagnostic-dir.  command-line option.
--heap-prof-interval The average sampling interval in bytes for the heap profiles generated by --heap-prof.  The default is 512 * 1024.
--heap-prof-name File name of the V8 heap profile generated with --heap-prof.
--icu-data-dir=file Specify ICU data load path.  Overrides NODE_ICU_DATA.
--input-type=type Set the module resolution type for input via --eval, --print or STDIN.
--inspect-brk=[host:]port Activate inspector on host:port and break at start of user script.
--inspect-port=[host:]port Set the host:port to be used when the inspector is activated.
--inspect-publish-uid=stderr,http Specify how the inspector WebSocket URL is exposed.  Valid values are stderr and http.  Default is stderr,http.
--inspect=[host:]port Activate inspector on host:port.  Default is 127.0.0.1:9229.
V8 Inspector integration allows attaching Chrome DevTools and IDEs to Node.js instances for debugging and profiling.  It uses the Chrome DevTools Protocol.
--insecure-http-parser Use an insecure HTTP parser that accepts invalid HTTP headers. This may allow interoperability with non-conformant HTTP implementations. It may also allow request smuggling and other HTTP attacks that rely on invalid headers being accepted. Avoid using this option.
--jitless Disable runtime allocation of executable memory. This may be required on some platforms for security reasons. It can also reduce attack surface on other platforms, but the performance impact may be severe.
This flag is inherited from V8 and is subject to change upstream. It may disappear in a non-semver-major release.
--max-http-header-size=size Specify the maximum size of HTTP headers in bytes. Defaults to 16 KB.
--napi-modules This option is a no-op.  It is kept for compatibility.
--no-deprecation Silence deprecation warnings.
--no-extra-info-on-fatal-exception Hide extra information on fatal exception that causes exit.
--no-force-async-hooks-checks Disable runtime checks for `async_hooks`.  These will still be enabled dynamically when `async_hooks` is enabled.
--no-addons Disable the `node-addons` exports condition as well as disable loading native addons. When `--no-addons` is specified, calling `process.dlopen` or requiring a native C++ addon will fail and throw an exception.
--no-global-search-paths Do not search modules from global paths.
--no-warnings Silence all process warnings (including deprecations).
--node-memory-debug Enable extra debug checks for memory leaks in Node.js internals. This is usually only useful for developers debugging Node.js itself.
--openssl-config=file Load an OpenSSL configuration file on startup.  Among other uses, this can be used to enable FIPS-compliant crypto if Node.js is built with ./configure --openssl-fips.
--pending-deprecation Emit pending deprecation warnings.
--policy-integrity=sri Instructs Node.js to error prior to running any code if the policy does not have the specified integrity. It expects a Subresource Integrity string as a parameter.
--preserve-symlinks Instructs the module loader to preserve symbolic links when resolving and caching modules other than the main module.
--preserve-symlinks-main Instructs the module loader to preserve symbolic links when resolving and caching the main module.
--prof  Generate V8 profiler output.
--prof-process Process V8 profiler output generated using the V8 option --prof.
--redirect-warnings=file Write process warnings to the given file instead of printing to stderr.
--report-compact Write diagnostic reports in a compact format, single-line JSON.
--report-dir --report-directory Location at which the diagnostic report will be generated.  The `file` name may be an absolute path. If it is not, the default directory it will be written to is controlled by the --diagnostic-dir.  command-line option.
--report-filename Name of the file to which the diagnostic report will be written.
--report-on-fatalerror Enables the diagnostic report to be triggered on fatal errors (internal errors within the Node.js runtime such as out of memory) that leads to termination of the application. Useful to inspect various diagnostic data elements such as heap, stack, event loop state, resource consumption etc. to reason about the fatal error.
--report-on-signal Enables diagnostic report to be generated upon receiving the specified (or predefined) signal to the running Node.js process. Default signal is SIGUSR2.
--report-signal Sets or resets the signal for diagnostic report generation (not supported on Windows). Default signal is SIGUSR2.
--report-uncaught-exception Enables diagnostic report to be generated on un-caught exceptions. Useful when inspecting JavaScript stack in conjunction with native stack and other runtime environment data.
--secure-heap=n Specify the size of the OpenSSL secure heap. Any value less than 2 disables the secure heap. The default is 0. The value must be a power of two.
--secure-heap-min=n Specify the minimum allocation from the OpenSSL secure heap. The default is 2. The value must be a power of two.
--throw-deprecation Throw errors for deprecations.
--title=title Specify process.title on startup.
--tls-cipher-list=list Specify an alternative default TLS cipher list.  Requires Node.js to be built with crypto support. (Default)
--tls-keylog=file Log TLS key material to a file. The key material is in NSS SSLKEYLOGFILE format and can be used by software (such as Wireshark) to decrypt the TLS traffic.
--tls-max-v1.2 Set default  maxVersion to 'TLSv1.2'. Use to disable support for TLSv1.3.
--tls-max-v1.3 Set default  maxVersion to 'TLSv1.3'. Use to enable support for TLSv1.3.
--tls-min-v1.0 Set default minVersion to 'TLSv1'. Use for compatibility with old TLS clients or servers.
--tls-min-v1.1 Set default minVersion to 'TLSv1.1'. Use for compatibility with old TLS clients or servers.
--tls-min-v1.2 Set default minVersion to 'TLSv1.2'. This is the default for 12.x and later, but the option is supported for compatibility with older Node.js versions.
--tls-min-v1.3 Set default minVersion to 'TLSv1.3'. Use to disable support for TLSv1.2 in favour of TLSv1.3, which is more secure.
--trace-atomics-wait Print short summaries of calls to Atomics.wait().
--trace-deprecation Print stack traces for deprecations.
--trace-event-categories categories A comma-separated list of categories that should be traced when trace event tracing is enabled using --trace-events-enabled.
--trace-event-file-pattern pattern Template string specifying the filepath for the trace event data, it supports ${rotation} and ${pid}.
--trace-events-enabled Enable the collection of trace event tracing information.
--trace-exit Prints a stack trace whenever an environment is exited proactively, i.e. invoking `process.exit()`.
--trace-sigint Prints a stack trace on SIGINT.
--trace-sync-io Print a stack trace whenever synchronous I/O is detected after the first turn of the event loop.
--trace-tls Prints TLS packet trace information to stderr.
--trace-uncaught Print stack traces for uncaught exceptions; usually, the stack trace associated with the creation of an Error is printed, whereas this makes Node.js also print the stack trace associated with throwing the value (which does not need to be an Error instance).
Enabling this option may affect garbage collection behavior negatively.
--trace-warnings Print stack traces for process warnings (including deprecations).
--track-heap-objects Track heap object allocations for heap snapshots.
--unhandled-rejections=mode Define the behavior for unhandled rejections. Can be one of `strict` (raise an error), `warn` (enforce warnings) or `none` (silence warnings).
--use-bundled-ca, --use-openssl-ca Use bundled Mozilla CA store as supplied by current Node.js version or use OpenSSL's default CA store.  The default store is selectable at build-time.
The bundled CA store, as supplied by Node.js, is a snapshot of Mozilla CA store that is fixed at release time.  It is identical on all supported platforms.
Using OpenSSL store allows for external modifications of the store. For most Linux and BSD distributions, this store is maintained by the distribution maintainers and system administrators.  OpenSSL CA store location is dependent on configuration of the OpenSSL library but this can be altered at runtime using environment variables.
See SSL_CERT_DIR and SSL_CERT_FILE.
--use-largepages=mode Re-map the Node.js static code to large memory pages at startup. If supported on the target system, this will cause the Node.js static code to be moved onto 2 MiB pages instead of 4 KiB pages.
mode must have one of the following values: `off` (the default value, meaning do not map), `on` (map and ignore failure, reporting it to stderr), or `silent` (map and silently ignore failure).
--v8-options Print V8 command-line options.
--v8-pool-size=num Set V8's thread pool size which will be used to allocate background jobs.  If set to 0 then V8 will choose an appropriate size of the thread pool based on the number of online processors.  If the value provided is larger than V8's maximum, then the largest value will be chosen.
--zero-fill-buffers Automatically zero-fills all newly allocated Buffer and SlowBuffer instances.
-c, --check Check the script's syntax without executing it.  Exits with an error code if script is invalid.
-e, --eval string Evaluate string as JavaScript.
-h, --help Print command-line options.  The output of this option is less detailed than this document.
-i, --interactive Open the REPL even if stdin does not appear to be a terminal.
-p, --print string Identical to -e, but prints the result.
-r, --require module Preload the specified module at startup.  Follows `require()`'s module resolution rules.  module may be either a path to a file, or a Node.js module name.
-v, --version Print node's version.
FORCE_COLOR Used to enable ANSI colorized output. The value may be one of: 1 , true , or an empty string to indicate 16-color support, 2 to indicate 256-color support, or 3 to indicate 16 million-color support. When used and set to a supported value, both the NO_COLOR and NODE_DISABLE_COLORS environment variables are ignored. Any other value will result in colorized output being disabled.
NO_COLOR Alias for NODE_DISABLE_COLORS
NODE_DEBUG modules... Comma-separated list of core modules that should print debug information.
NODE_DEBUG_NATIVE modules... Comma-separated list of C++ core modules that should print debug information.
NODE_DISABLE_COLORS When set to 1, colors will not be used in the REPL.
NODE_EXTRA_CA_CERTS file When set, the well-known “root” CAs (like VeriSign) will be extended with the extra certificates in file.  The file should consist of one or more trusted certificates in PEM format.
If file is missing or misformatted, a message will be emitted once using process.emitWarning(), but any errors are otherwise ignored.
This environment variable is ignored when `node` runs as setuid root or has Linux file capabilities set.
The NODE_EXTRA_CA_CERTS environment variable is only read when the Node.js process is first launched.  Changing the value at runtime using process.env.NODE_EXTRA_CA_CERTS has no effect on the current process.
NODE_ICU_DATA file Data path for ICU (Intl object) data.  Will extend linked-in data when compiled with small-icu support.
NODE_NO_WARNINGS When set to 1, process warnings are silenced.
NODE_OPTIONS options... A space-separated list of command-line options, which are interpreted as if they had been specified on the command line before the actual command (so they can be overridden).  Node.js will exit with an error if an option that is not allowed in the environment is used, such as --print or a script file.
NODE_PATH directories... A colon-separated list of directories prefixed to the module search path.
NODE_PENDING_DEPRECATION When set to 1, emit pending deprecation warnings.
NODE_PRESERVE_SYMLINKS When set to 1, the module loader preserves symbolic links when resolving and caching modules.
NODE_REDIRECT_WARNINGS file Write process warnings to the given file instead of printing to stderr.  Equivalent to passing --redirect-warnings file on the command line.
NODE_REPL_HISTORY file Path to the file used to store persistent REPL history.  The default path is ~/.node_repl_history, which is overridden by this variable.  Setting the value to an empty string ("" or " ") will disable persistent REPL history.
NODE_SKIP_PLATFORM_CHECK When set to 1, the check for a supported platform is skipped during Node.js startup.  Node.js might not execute correctly.  Any issues encountered on unsupported platforms will not be fixed.
NODE_TLS_REJECT_UNAUTHORIZED When set to 0, TLS certificate validation is disabled.
NODE_V8_COVERAGE dir When set, Node.js writes JavaScript code coverage information to dir.
OPENSSL_CONF file Load an OpenSSL configuration file on startup.  Among other uses, this can be used to enable FIPS-compliant crypto if Node.js is built with ./configure --openssl-fips.
If the --openssl-config command-line option is used, this environment variable is ignored.
SSL_CERT_DIR dir If --use-openssl-ca is enabled, this overrides and sets OpenSSL's directory containing trusted certificates.
SSL_CERT_FILE file If --use-openssl-ca is enabled, this overrides and sets OpenSSL's file containing trusted certificates.
UV_THREADPOOL_SIZE size Sets the number of threads used in libuv's threadpool to size.
Bugs are tracked in GitHub Issues: https://github.com/nodejs/node/issues
Copyright Node.js contributors.  Node.js is available under the MIT license.
Node.js also includes external libraries that are available under a variety of licenses.  See https://github.com/nodejs/node/blob/HEAD/LICENSE for the full license text.
Website: https://nodejs.org/
Documentation: https://nodejs.org/api/
GitHub repository and issue tracker: https://github.com/nodejs/node
IRC (general questions): libera.chat #node.js (unofficial)
Written and maintained by 1000+ contributors: https://github.com/nodejs/node/blob/HEAD/AUTHORS
electrum(1)                  General Commands Manual                 electrum(1)
electrum - Lightweight bitcoin client
electrum [options] command [options]
Electrum is a lightweight bitcoin client. Electrum protects from losing bitcoins in a backup mistake or computer failure. It allows recovery of wallet from a passphrase which you can learn by heart or write it down on a paper. Since electrum does not download the entire bitcoin block chain there is no waiting time when the client is started.
-g GUI, --gui=GUI Select user interface, possible values are  qt, lite, gtk or text
-w WALLET_PATH, --wallet=WALLET_PATH Use wallet from WALLET_PATH, default is electrum.dat.
-o, --offline Remain offline.
-a, --all Show all addresses.
-b, --balance Show the balance of listed addresses
-l, --labels Show the labels of listed addresses
-f TX_FEE, --fee=TX_FEE set tx fee
-F FROM_ADDR, --fromad dr=FROM_ADDR
set source address for payto/mktx. if it isn't in the wallet, it will ask for the private key unless supplied in the format public_key:private_key. It's not saved in the wallet.
-c CHANGE_ADDR, --changeaddr=CHANGE_ADDR
set the change address for payto/mktx. default is a spare address, or the source address if it's not in the wallet.
-s SERVER, --server=SERVER set server host:port:protocol, where protocol is t or h
-p PROXY, --proxy=PROXY set proxy [type:]host[:port], where type is socks4,socks5 or http
-v, --verbose show debugging information
-P, --portable portable wallet
-L LANGUAGE, --lang=LANGUAGE defaut language used in GUI
-u, --usb Turn on support for hardware wallets (EXPERIMENTAL).
Electrum client was initially written by ThomasV <thomasv@gitorious> This manual page was written by Vasudev Kamath <kamathvasudev@gmail.com> for Debian Project (but can be used by others).
lrzip(1)                                                                lrzip(1)
lrzip - a large-file compression program
lrzip [OPTIONS] <file> lrzip -d [OPTIONS] <file> lrunzip [OPTIONS] <file> lrzcat [OPTIONS] <file> lrztar [lrzip options] <directory> lrztar -d [lrzip options] <directory> lrzuntar [lrzip options] <directory> lrz [lrz options] <directory> LRZIP=NOCONFIG [lrzip|lrunzip] [OPTIONS] <file>
LRZIP is a file compression program designed to do particularly well on very large files containing long distance redundancy.  lrztar is a wrapper for LRZIP to simplify compression and decompression of directories.
Here is a summary of the options to lrzip.
General options: -c, --check             check integrity of file written on decompression -d, --decompress        decompress -e, --encrypt[=password] password protected sha512/aes128 encryption on compression -h, -?, --help          show help -H, --hash              display md5 hash integrity information -i, --info              show compressed file information -q, --quiet             don't show compression progress -r, --recursive         operate recursively on directories -t, --test              test compressed file integrity -v[v], --verbose        Increase verbosity -V, --version           show version Options affecting output: -D, --delete            delete existing files -f, --force             force overwrite of any existing files -k, --keep-broken       keep broken or damaged output files -o, --outfile filename  specify the output file name and/or path -O, --outdir directory  specify the output directory when -o is not used -S, --suffix suffix     specify compressed suffix (default '.lrz') Options affecting compression: -b, --bzip2             bzip2 compression -g, --gzip              gzip compression using zlib -l, --lzo               lzo compression (ultra fast) -n, --no-compress       no backend compression - prepare for other compressor -z, --zpaq              zpaq compression (best, extreme compression, extremely slow) Low level options: -L, --level level       set lzma/bzip2/gzip compression level (1-9, default 7) -N, --nice-level value  Set nice value to value (default 19) -p, --threads value     Set processor count to override number of threads -m, --maxram size       Set maximum available ram in hundreds of MB overrides detected amount of available ram -T, --threshold         Disable LZ4 compressibility testing -U, --unlimited         Use unlimited window size beyond ramsize (potentially much slower) -w, --window size       maximum compression window in hundreds of MB default chosen by heuristic dependent on ram and chosen compression
LRZIP=NOCONFIG environment variable setting can be used to bypass lrzip.conf. TMP environment variable will be used for storage of temporary files when needed. TMPDIR may also be stored in lrzip.conf file.
If no filenames or "-" is specified, stdin/out will be used.
General options -c     This option enables integrity checking of the file written to disk on decompression. All decompression is tested internally in lrzip with either crc32 or md5 hash checking depending on the version of the archive already.  However the file written to disk may be corrupted for other reasons to do with other userspace problems such as faulty library versions, drivers, hardware failure and so on. Enabling this option will make lrzip perform an md5 hash check on the file that's written to disk. When the archive has the md5 value stored in it, it is compared to this. Otherwise it is compared to the value calculated during decompression. This offers an extra guarantee that the file written is the same as the original archived.
-d     Decompress. If this option is not used then lrzip looks at the name used to launch the program. If it contains the string "lrunzip" then the -d option is automatically set. If it contains the string "lrzcat" then the -d -o - options are automatically set.
--encrypt[=password] Encrypt. This option enables high grade password encryption using a combination of multiply sha512 hashed password, random salt and aes128 CBC encryption.  Passwords up to 500 characters long are supported, and the encryption mechanism used virtually guarantees that the same file created with the same password will never be the same. Furthermore, the password hashing is increased according to the date the file is encrypted, increasing the number of CPU cycles required for each password attempt in accordance with Moore's law, thus making the difficulty of attempting brute force attacks proportional to the power of modern computers.
-h|-?  Print an options summary page
-H     This shows the md5 hash value calculated on compressing or decompressing an lrzip archive. By default all compression has the md5 value calculated and stored in all archives since version 0.560. On decompression, when an md5 value has been found, it will be calculated and used for integrity checking.  If the md5 value is not stored in the archive, it will not be calculated unless explicitly specified with this option, or check integrity (see below) has been requested.
-i     This shows information about a compressed file. It shows the compressed size, the decompressed size, the compression ratio, what compression was used and what hash checking will be used for internal integrity checking.  Note that the compression mode is detected from the first block only and it will show no compression used if the first block was incompressible, even if later blocks were compressible. If verbose options -v or -vv are added, a breakdown of all the internal blocks and progressively more information pertaining to them will also be shown.
-q     If this option is specified then lrzip will not show the percentage progress while compressing. Note that compression happens in bursts with lzma compression which is the default compression. This means that it will progress very rapidly for short periods and then stop for long periods.
-r     If this option is specified, lrzip will recursively enter the directories specified, compressing or decompressing every file individually in the same directory. Note for better compression it is recommended to instead combine files in a tar file rather than compress them separately, either manually or with the lrztar helper.
-t     This tests the compressed file integrity. It does this by decompressing it to a temporary file and then deleting it.
-v[v]  Increases verbosity. -vv will print more messages than -v.
-V     Print the lrzip version number
Options affecting output -D     If this option is specified then lrzip will delete the source file after successful compression or decompression. When this option is not specified then the source files are not deleted.
-f     If this option is not specified (Default) then lrzip will not overwrite any existing files. If you set this option then rzip will silently overwrite any files as needed.
-k     This option will keep broken or damaged files instead of deleting them.  When compression or decompression is interrupted either by user or error, or a file decompressed fails an integrity check, it is normally deleted by LRZIP.
-o     Set the output file name. If this option is not set then the output file name is chosen based on the input name and the suffix. The -o option cannot be used if more than one file name is specified on the command line.
-O     Set the output directory for the default filename. This option cannot be combined with -o.
-S     Set the compression suffix. The default is '.lrz'.
Options affecting compression -b     Bzip2 compression. Uses bzip2 compression for the 2nd stage, much like the original rzip does.
-g     Gzip compression. Uses gzip compression for the 2nd stage. Uses libz compress and uncompress functions.
-l     LZO Compression. If this option is set then lrzip will use the ultra fast lzo compression algorithm for the 2nd stage. This mode of compression gives bzip2 like compression at the speed it would normally take to simply copy the file, giving excellent compression/time value.
-n     No 2nd stage compression. If this option is set then lrzip will only perform the long distance redundancy 1st stage compression. While this does not compress any faster than LZO compression, it produces a smaller file that then responds better to further compression (by eg another application), also reducing the compression time substantially.
-z     ZPAQ compression. Uses ZPAQ compression which is from the PAQ family of compressors known for having some of the highest compression ratios possible but at the cost of being extremely slow on both compress and decompress (4x slower than lzma which is the default).
Low level options -L 1..9 Set the compression level from 1 to 9. The default is to use level 7, which gives good all round compression. The compression level is also strongly related to how much memory lrzip uses. See the -w option for details.
-N value The default nice value is 19. This option can be used to set the priority scheduling for the lrzip backup or decompression. Valid nice values are from -20 to 19. Note this does NOT speed up or slow down compression.
-p value Set the number of processor count to determine the number of threads to run.  Normally lrzip will scale according to the number of CPUs it detects. Using this will override the value in case you wish to use less CPUs to either decrease the load on your machine, or to improve compression. Setting it to 1 will maximise compression but will not attempt to use more than one CPU.
-T     Disables the LZ4 compressibility threshold testing when a slower compression back-end is used. LZ4 testing is normally performed for the slower back-end compression of LZMA and ZPAQ. The reasoning is that if it is completely incompressible by LZ4 then it will also be incompressible by them. Thus if a block fails to be compressed by the very fast LZ4, lrzip will not attempt to compress that block with the slower compressor, thereby saving time. If this option is enabled, it will bypass the LZ4 testing and attempt to compress each block regardless.
-U     Unlimited window size. If this option is set, and the file being compressed does not fit into the available ram, lrzip will use a moving second buffer as a "sliding mmap" which emulates having infinite ram. This will provide the most possible compression in the first rzip stage which can improve the compression of ultra large files when they're bigger than the available ram. However it runs progressively slower the larger the difference between ram and the file size, so is best reserved for when the smallest possible size is desired on a very large file, and the time taken is not important.
-w n   Set the maximum allowable compression window size to n in hundreds of megabytes.  This is the amount of memory lrzip will search during its first stage of pre-compression and is the main thing that will determine how much benefit lrzip will provide over ordinary compression with the 2nd stage algorithm. If not set (recommended), the value chosen will be determined by an internal heuristic in lrzip which uses the most memory that is reasonable, without any hard upper limit. It is limited to 2GB on 32bit machines. lrzip will always reduce the window size to the biggest it can be without running out of memory.
"make install" or just install lrzip somewhere in your search path.
LRZIP operates in two stages. The first stage finds and encodes large chunks of duplicated data over potentially very long distances in the input file. The second stage is to use a compression algorithm to compress the output of the first stage. The compression algorithm can be chosen to be optimised for extreme size (zpaq), size (lzma - default), speed (lzo), legacy (bzip2 or gzip) or can be omitted entirely doing only the first stage. A one stage only compressed file can almost always improve both the compression size and speed done by a subsequent compression program.
The key difference between lrzip and other well known compression algorithms is its ability to take advantage of very long distance redundancy. The well known deflate algorithm used in gzip uses a maximum history buffer of 32k. The block sorting algorithm used in bzip2 is limited to 900k of history. The history buffer in lrzip can be any size long, not even limited by available ram.
It is quite common these days to need to compress files that contain long distance redundancies. For example, when compressing a set of home directories several users might have copies of the same file, or of quite similar files. It is also common to have a single file that contains large duplicated chunks over long distances, such as pdf files containing repeated copies of the same image. Most compression programs won't be able to take advantage of this redundancy, and thus might achieve a much lower compression ratio than lrzip can achieve.
LRZIP recognises a configuration file that contains default settings. This configuration is searched for in the current directory, /etc/lrzip, and $HOME/.lrzip. The configuration filename must be lrzip.conf.
By default, lrzip will search for and use a configuration file, lrzip.conf.  If the user wishes to bypass the file, a startup ENV variable may be set. LRZIP = NOCONFIG [lrzip|lrunzip] [OPTIONS] <file> which will force lrzip to ignore the configuration file.
HISTORY - Notes on rzip by Andrew Tridgell The ideas behind rzip were first implemented in 1998 while I was working on rsync. That version was too slow to be practical, and was replaced by this version in 2003.  LRZIP was created by the desire to have better compression and/or speed by Con Kolivas on blending the lzma and lzo compression algorithms with the rzip first stage, and extending the compression windows to scale with increasing ram sizes.
Nil known.
lrzip.conf(5), lrunzip(1), lrzcat(1), lrztar(1), lrzuntar(1), lrz(1), bzip2(1), gzip(1), lzop(1), rzip(1), zip(1)
AUTHOR and CREDITS lrzip is being extensively bastardised from rzip by Con Kolivas. rzip was written by Andrew Tridgell. lzma was written by Igor Pavlov. lzo was written by Markus Oberhumer. zpaq was written by Matt Mahoney. Peter Hyman added informational output, updated LZMA SDK, and added lzma multi-threading capabilities.
If you wish to report a problem, or make a suggestion, then please email Con at kernel@kolivas.org
lrzip is released under the GNU General Public License version 2.  Please see the file COPYING for license details.
COFFEE(1)                         User Commands                        COFFEE(1)
coffee - interpreter and compiler for the CoffeeScript language
coffee [options] path/to/script.coffee -- [args]
If called without options, `coffee` will run your script.
-b, --bare compile without a top-level function wrapper
-c, --compile compile to JavaScript and save as .js files
-e, --eval pass a string from the command line as input
-i, --interactive run an interactive CoffeeScript REPL
-j, --join concatenate the source CoffeeScript before compiling
-m, --map generate source map and save as .js.map files
-M, --inline-map generate source map and include it directly in output
-n, --nodes print out the parse tree that the parser produces
--nodejs pass options directly to the "node" binary
--no-header suppress the "Generated by" header
-o, --output set the output directory for compiled JavaScript
-p, --print print out the compiled JavaScript
-r, --require require the given module before eval or REPL
-s, --stdio listen for and compile scripts over stdio
-l, --literate treat stdio as literate style coffee-script
-t, --tokens print out the tokens that the lexer/rewriter produce
-v, --version display the version number
-w, --watch watch scripts for changes and rerun commands
LSCPU(1)                          User Commands                         LSCPU(1)
lscpu - display information about the CPU architecture
lscpu [options]
lscpu gathers CPU architecture information from sysfs, /proc/cpuinfo and any applicable architecture-specific libraries (e.g. librtas on Powerpc). The command output can be optimized for parsing or for easy readability by humans. The information includes, for example, the number of CPUs, threads, cores, sockets, and Non-Uniform Memory Access (NUMA) nodes. There is also information about the CPU caches and cache sharing, family, model, bogoMIPS, byte order, and stepping.
The default output formatting on terminal is subject to change and maybe optimized for better readability. The output for non-terminals (e.g., pipes) is never affected by this optimization and it is always in "Field: data\n" format. Use for example "lscpu | less" to see the default output without optimizations.
In virtualized environments, the CPU architecture information displayed reflects the configuration of the guest operating system which is typically different from the physical (host) system. On architectures that support retrieving physical topology information, lscpu also displays the number of physical sockets, chips, cores in the host system.
Options that result in an output table have a list argument. Use this argument to customize the command output. Specify a comma-separated list of column labels to limit the output table to only the specified columns, arranged in the specified order. See COLUMNS for a list of valid column labels. The column labels are not case sensitive.
Not all columns are supported on all architectures. If an unsupported column is specified, lscpu prints the column but does not provide any data for it.
The cache sizes are reported as summary from all CPUs. The versions before v2.34 reported per-core sizes, but this output was confusing due to complicated CPUs topology and the way how caches are shared between CPUs. For more details about caches see --cache. Since version v2.37 lscpu follows cache IDs as provided by Linux kernel and it does not always start from zero.
-a, --all Include lines for online and offline CPUs in the output (default for -e). This option may only be specified together with option -e or -p.
-B, --bytes Print the sizes in bytes rather than in a human-readable format.
-b, --online Limit the output to online CPUs (default for -p). This option may only be specified together with option -e or -p.
-C, --caches[=list] Display details about CPU caches. For details about available information see --help output.
If the list argument is omitted, all columns for which data is available are included in the command output.
When specifying the list argument, the string of option, equal sign (=), and list must not contain any blanks or other whitespace. Examples: '-C=NAME,ONE-SIZE' or '--caches=NAME,ONE-SIZE'.
The default list of columns may be extended if list is specified in the format +list (e.g., lscpu -C=+ALLOC-POLICY).
-c, --offline Limit the output to offline CPUs. This option may only be specified together with option -e or -p.
-e, --extended[=list] Display the CPU information in human-readable format.
If the list argument is omitted, the default columns are included in the command output. The default output is subject to change.
When specifying the list argument, the string of option, equal sign (=), and list must not contain any blanks or other whitespace. Examples: '-e=cpu,node' or '--extended=cpu,node'.
The default list of columns may be extended if list is specified in the format +list (e.g., lscpu -e=+MHZ).
-J, --json Use JSON output format for the default summary or extended output (see --extended).
-p, --parse[=list] Optimize the command output for easy parsing.
If the list argument is omitted, the command output is compatible with earlier versions of lscpu. In this compatible format, two commas are used to separate CPU cache columns. If no CPU caches are identified the cache column is omitted. If the list argument is used, cache columns are separated with a colon (:).
When specifying the list argument, the string of option, equal sign (=), and list must not contain any blanks or other whitespace. Examples: '-p=cpu,node' or '--parse=cpu,node'.
The default list of columns may be extended if list is specified in the format +list (e.g., lscpu -p=+MHZ).
-s, --sysroot directory Gather CPU data for a Linux instance other than the instance from which the lscpu command is issued. The specified directory is the system root of the Linux instance to be inspected.
-x, --hex Use hexadecimal masks for CPU sets (for example "ff"). The default is to print the sets in list format (for example 0,1). Note that before version 2.30 the mask has been printed with 0x prefix.
-y, --physical Display physical IDs for all columns with topology elements (core, socket, etc.). Other than logical IDs, which are assigned by lscpu, physical IDs are platform-specific values that are provided by the kernel. Physical IDs are not necessarily unique and they might not be arranged sequentially. If the kernel could not retrieve a physical ID for an element lscpu prints the dash (-) character.
The CPU logical numbers are not affected by this option.
--output-all Output all available columns. This option must be combined with either --extended, --parse or --caches.
The basic overview of CPU family, model, etc. is always based on the first CPU only.
Sometimes in Xen Dom0 the kernel reports wrong data.
On virtual hardware the number of cores per socket, etc. can be wrong.
Cai Qian <qcai@redhat.com>, Karel Zak <kzak@redhat.com>, Heiko Carstens <heiko.carstens@de.ibm.com>
chcpu(8)
The lscpu 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/>.
TWM(1)                       General Commands Manual                      TWM(1)
twm - Tab Window Manager for the X Window System
twm [ -display dpy ] [ -s ] [ -f initfile ] [ -v ]
Twm is a window manager for the X Window System.  It provides titlebars, shaped windows, several forms of icon management, user-defined macro functions, click-to-type and pointer-driven keyboard focus, and user- specified key and pointer button bindings.
This program is usually started by the user's session manager or startup script.  When used from xdm(1) or xinit(1) without a session manager, twm is frequently executed in the foreground as the last client.  When run this way, exiting twm causes the session to be terminated (i.e., logged out).
By default, application windows are surrounded by a ``frame'' with a titlebar at the top and a special border around the window.  The titlebar contains the window's name, a rectangle that is lit when the window is receiving keyboard input, and function boxes known as ``titlebuttons'' at the left and right edges of the titlebar.
Pressing pointer Button1 (usually the left-most button unless it has been changed with xmodmap) on a titlebutton will invoke the function associated with the button.  In the default interface, windows are iconified by clicking (pressing and then immediately releasing) the left titlebutton (which looks like a Dot).  Conversely, windows are deiconified by clicking in the associated icon or entry in the icon manager (see description of the variable ShowIconManager and of the function f.showiconmgr).
Windows are resized by pressing the right titlebutton (which resembles a group of nested squares), dragging the pointer over edge that is to be moved, and releasing the pointer when the outline of the window is the desired size.  Similarly, windows are moved by pressing in the title or highlight region, dragging a window outline to the new location, and then releasing when the outline is in the desired position.  Just clicking in the title or highlight region raises the window without moving it.