neulab/tldr huggingface dataset:
"intel-mnemonic" "att-mnemonic" Select between intel mnemonic mode and AT&T mnemonic mode.  Note: "intel-mnemonic" implies "intel" and "att-mnemonic" implies "att".
"addr64" "addr32" "addr16" "data32" "data16" Specify the default address size and operand size.  These five options will be overridden if "x86-64", "i386" or "i8086" appear later in the option string.
"suffix" When in AT&T mode and also for a limited set of instructions when in Intel mode, instructs the disassembler to print a mnemonic suffix even when the suffix could be inferred by the operands or, for certain instructions, the execution mode's defaults.
For PowerPC, the -M argument raw selects disasssembly of hardware insns rather than aliases.  For example, you will see "rlwinm" rather than "clrlwi", and "addi" rather than "li".  All of the -m arguments for gas that select a CPU are supported.  These are: 403, 405, 440, 464, 476, 601, 603, 604, 620, 7400, 7410, 7450, 7455, 750cl, 821, 850, 860, a2, booke, booke32, cell, com, e200z4, e300, e500, e500mc, e500mc64, e500x2, e5500, e6500, efs, power4, power5, power6, power7, power8, power9, power10, ppc, ppc32, ppc64, ppc64bridge, ppcps, pwr, pwr2, pwr4, pwr5, pwr5x, pwr6, pwr7, pwr8, pwr9, pwr10, pwrx, titan, and vle.  32 and 64 modify the default or a prior CPU selection, disabling and enabling 64-bit insns respectively.  In addition, altivec, any, htm, vsx, and spe add capabilities to a previous or later CPU selection.  any will disassemble any opcode known to binutils, but in cases where an opcode has two different meanings or different arguments, you may not see the disassembly you expect.  If you disassemble without giving a CPU selection, a default will be chosen from information gleaned by BFD from the object files headers, but the result again may not be as you expect.
For MIPS, this option controls the printing of instruction mnemonic names and register names in disassembled instructions.  Multiple selections from the following may be specified as a comma separated string, and invalid options are ignored:
"no-aliases" Print the 'raw' instruction mnemonic instead of some pseudo instruction mnemonic.  I.e., print 'daddu' or 'or' instead of 'move', 'sll' instead of 'nop', etc.
"msa" Disassemble MSA instructions.
"virt" Disassemble the virtualization ASE instructions.
"xpa" Disassemble the eXtended Physical Address (XPA) ASE instructions.
"gpr-names=ABI" Print GPR (general-purpose register) names as appropriate for the specified ABI.  By default, GPR names are selected according to the ABI of the binary being disassembled.
"fpr-names=ABI" Print FPR (floating-point register) names as appropriate for the specified ABI.  By default, FPR numbers are printed rather than names.
"cp0-names=ARCH" Print CP0 (system control coprocessor; coprocessor 0) register names as appropriate for the CPU or architecture specified by ARCH.  By default, CP0 register names are selected according to the architecture and CPU of the binary being disassembled.
"hwr-names=ARCH" Print HWR (hardware register, used by the "rdhwr" instruction) names as appropriate for the CPU or architecture specified by ARCH.  By default, HWR names are selected according to the architecture and CPU of the binary being disassembled.
"reg-names=ABI" Print GPR and FPR names as appropriate for the selected ABI.
"reg-names=ARCH" Print CPU-specific register names (CP0 register and HWR names) as appropriate for the selected CPU or architecture.
For any of the options listed above, ABI or ARCH may be specified as numeric to have numbers printed rather than names, for the selected types of registers.  You can list the available values of ABI and ARCH using the --help option.
For VAX, you can specify function entry addresses with -M entry:0xf00ba.  You can use this multiple times to properly disassemble VAX binary files that don't contain symbol tables (like ROM dumps).  In these cases, the function entry mask would otherwise be decoded as VAX instructions, which would probably lead the rest of the function being wrongly disassembled.
-p --private-headers Print information that is specific to the object file format.  The exact information printed depends upon the object file format.  For some object file formats, no additional information is printed.
-P options --private=options Print information that is specific to the object file format.  The argument options is a comma separated list that depends on the format (the lists of options is displayed with the help).
For XCOFF, the available options are:
"header" "aout" "sections" "syms" "relocs" "lineno," "loader" "except" "typchk" "traceback" "toc" "ldinfo"
Not all object formats support this option.  In particular the ELF format does not use it.
-r --reloc Print the relocation entries of the file.  If used with -d or -D, the relocations are printed interspersed with the disassembly.
-R --dynamic-reloc Print the dynamic relocation entries of the file.  This is only meaningful for dynamic objects, such as certain types of shared libraries.  As for -r, if used with -d or -D, the relocations are printed interspersed with the disassembly.
-s --full-contents Display the full contents of any sections requested.  By default all non-empty sections are displayed.
-S --source Display source code intermixed with disassembly, if possible. Implies -d.
--source-comment[=txt] Like the -S option, but all source code lines are displayed with a prefix of txt.  Typically txt will be a comment string which can be used to distinguish the assembler code from the source code.  If txt is not provided then a default string of "# " (hash followed by a space), will be used.
--prefix=prefix Specify prefix to add to the absolute paths when used with -S.
--prefix-strip=level Indicate how many initial directory names to strip off the hardwired absolute paths. It has no effect without --prefix=prefix.
--show-raw-insn When disassembling instructions, print the instruction in hex as well as in symbolic form.  This is the default except when --prefix-addresses is used.
--no-show-raw-insn When disassembling instructions, do not print the instruction bytes. This is the default when --prefix-addresses is used.
--insn-width=width Display width bytes on a single line when disassembling instructions.
--visualize-jumps[=color|=extended-color|=off] Visualize jumps that stay inside a function by drawing ASCII art between the start and target addresses.  The optional =color argument adds color to the output using simple terminal colors.  Alternatively the =extended-color argument will add color using 8bit colors, but these might not work on all terminals.
If it is necessary to disable the visualize-jumps option after it has previously been enabled then use visualize-jumps=off.
-W[lLiaprmfFsoORtUuTgAckK] --dwarf[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=str-offsets,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links] Displays the contents of the DWARF debug sections in the file, if any are present.  Compressed debug sections are automatically decompressed (temporarily) before they are displayed.  If one or more of the optional letters or words follows the switch then only those type(s) of data will be dumped.  The letters and words refer to the following information:
"a" "=abbrev" Displays the contents of the .debug_abbrev section.
"A" "=addr" Displays the contents of the .debug_addr section.
"c" "=cu_index" Displays the contents of the .debug_cu_index and/or .debug_tu_index sections.
"f" "=frames" Display the raw contents of a .debug_frame section.
"F" "=frame-interp" Display the interpreted contents of a .debug_frame section.
"g" "=gdb_index" Displays the contents of the .gdb_index and/or .debug_names sections.
"i" "=info" Displays the contents of the .debug_info section.  Note: the output from this option can also be restricted by the use of the --dwarf-depth and --dwarf-start options.
"k" "=links" Displays the contents of the .gnu_debuglink and/or .gnu_debugaltlink sections.  Also displays any links to separate dwarf object files (dwo), if they are specified by the DW_AT_GNU_dwo_name or DW_AT_dwo_name attributes in the .debug_info section.
"K" "=follow-links" Display the contents of any selected debug sections that are found in linked, separate debug info file(s).  This can result in multiple versions of the same debug section being displayed if it exists in more than one file.
In addition, when displaying DWARF attributes, if a form is found that references the separate debug info file, then the referenced contents will also be displayed.
"l" "=rawline" Displays the contents of the .debug_line section in a raw format.
"L" "=decodedline" Displays the interpreted contents of the .debug_line section.
"m" "=macro" Displays the contents of the .debug_macro and/or .debug_macinfo sections.
"o" "=loc" Displays the contents of the .debug_loc and/or .debug_loclists sections.
"O" "=str-offsets" Displays the contents of the .debug_str_offsets section.
"p" "=pubnames" Displays the contents of the .debug_pubnames and/or .debug_gnu_pubnames sections.
"r" "=aranges" Displays the contents of the .debug_aranges section.
"R" "=Ranges" Displays the contents of the .debug_ranges and/or .debug_rnglists sections.
"s" "=str" Displays the contents of the .debug_str, .debug_line_str and/or .debug_str_offsets sections.
"t" "=pubtype" Displays the contents of the .debug_pubtypes and/or .debug_gnu_pubtypes sections.
"T" "=trace_aranges" Displays the contents of the .trace_aranges section.
"u" "=trace_abbrev" Displays the contents of the .trace_abbrev section.
"U" "=trace_info" Displays the contents of the .trace_info section.
Note: displaying the contents of .debug_static_funcs, .debug_static_vars and debug_weaknames sections is not currently supported.
--dwarf-depth=n Limit the dump of the ".debug_info" section to n children.  This is only useful with --debug-dump=info.  The default is to print all DIEs; the special value 0 for n will also have this effect.
With a non-zero value for n, DIEs at or deeper than n levels will not be printed.  The range for n is zero-based.
--dwarf-start=n Print only DIEs beginning with the DIE numbered n.  This is only useful with --debug-dump=info.
If specified, this option will suppress printing of any header information and all DIEs before the DIE numbered n.  Only siblings and children of the specified DIE will be printed.
This can be used in conjunction with --dwarf-depth.
--dwarf-check Enable additional checks for consistency of Dwarf information.
--ctf=section Display the contents of the specified CTF section.  CTF sections themselves contain many subsections, all of which are displayed in order.
--ctf-parent=section Specify the name of another section from which the CTF dictionary can inherit types.  (If none is specified, we assume the CTF dictionary inherits types from the default-named member of the archive contained within this section.)
-G --stabs Display the full contents of any sections requested.  Display the contents of the .stab and .stab.index and .stab.excl sections from an ELF file.  This is only useful on systems (such as Solaris 2.0) in which ".stab" debugging symbol-table entries are carried in an ELF section.  In most other file formats, debugging symbol-table entries are interleaved with linkage symbols, and are visible in the --syms output.
--start-address=address Start displaying data at the specified address.  This affects the output of the -d, -r and -s options.
--stop-address=address Stop displaying data at the specified address.  This affects the output of the -d, -r and -s options.
-t --syms Print the symbol table entries of the file.  This is similar to the information provided by the nm program, although the display format is different.  The format of the output depends upon the format of the file being dumped, but there are two main types.  One looks like this:
[  4](sec  3)(fl 0x00)(ty   0)(scl   3) (nx 1) 0x00000000 .bss [  6](sec  1)(fl 0x00)(ty   0)(scl   2) (nx 0) 0x00000000 fred
where the number inside the square brackets is the number of the entry in the symbol table, the sec number is the section number, the fl value are the symbol's flag bits, the ty number is the symbol's type, the scl number is the symbol's storage class and the nx value is the number of auxiliary entries associated with the symbol.  The last two fields are the symbol's value and its name.
The other common output format, usually seen with ELF based files, looks like this:
00000000 l    d  .bss   00000000 .bss 00000000 g       .text  00000000 fred
Here the first number is the symbol's value (sometimes referred to as its address).  The next field is actually a set of characters and spaces indicating the flag bits that are set on the symbol.  These characters are described below.  Next is the section with which the symbol is associated or *ABS* if the section is absolute (ie not connected with any section), or *UND* if the section is referenced in the file being dumped, but not defined there.
After the section name comes another field, a number, which for common symbols is the alignment and for other symbol is the size. Finally the symbol's name is displayed.
The flag characters are divided into 7 groups as follows:
"l" "g" "u" "!" The symbol is a local (l), global (g), unique global (u), neither global nor local (a space) or both global and local (!).  A symbol can be neither local or global for a variety of reasons, e.g., because it is used for debugging, but it is probably an indication of a bug if it is ever both local and global.  Unique global symbols are a GNU extension to the standard set of ELF symbol bindings.  For such a symbol the dynamic linker will make sure that in the entire process there is just one symbol with this name and type in use.
"w" The symbol is weak (w) or strong (a space).
"C" The symbol denotes a constructor (C) or an ordinary symbol (a space).
"W" The symbol is a warning (W) or a normal symbol (a space).  A warning symbol's name is a message to be displayed if the symbol following the warning symbol is ever referenced.
"I" "i" The symbol is an indirect reference to another symbol (I), a function to be evaluated during reloc processing (i) or a normal symbol (a space).
"d" "D" The symbol is a debugging symbol (d) or a dynamic symbol (D) or a normal symbol (a space).
"F" "f" "O" The symbol is the name of a function (F) or a file (f) or an object (O) or just a normal symbol (a space).
-T --dynamic-syms Print the dynamic symbol table entries of the file.  This is only meaningful for dynamic objects, such as certain types of shared libraries.  This is similar to the information provided by the nm program when given the -D (--dynamic) option.
The output format is similar to that produced by the --syms option, except that an extra field is inserted before the symbol's name, giving the version information associated with the symbol.  If the version is the default version to be used when resolving unversioned references to the symbol then it's displayed as is, otherwise it's put into parentheses.
--special-syms When displaying symbols include those which the target considers to be special in some way and which would not normally be of interest to the user.
-V --version Print the version number of objdump and exit.
-x --all-headers Display all available header information, including the symbol table and relocation entries.  Using -x is equivalent to specifying all of -a -f -h -p -r -t.
-w --wide Format some lines for output devices that have more than 80 columns. Also do not truncate symbol names when they are displayed.
-z --disassemble-zeroes Normally the disassembly output will skip blocks of zeroes.  This option directs the disassembler to disassemble those blocks, just like any other data.
nm(1), readelf(1), and the Info entries for binutils.
Copyright (c) 1991-2021 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts.  A copy of the license is included in the section entitled "GNU Free Documentation License".
YARN(1)                      General Commands Manual                     YARN(1)
yarn - scenario testing of Unix command line tools
yarn [--allow-missing-steps] [--no-allow-missing-steps] [--cd-datadir] [--no-cd-datadir] [--config=FILE] [--dump-config] [--dump-setting-names] [--generate-manpage=TEMPLATE] [-h] [--help] [--help-all] [--list-config-files] [--version] [--no-default-configs] [--dump-memory-profile=METHOD] [--env=NAME=VALUE] [--log=FILE] [--log-keep=N] [--log-level=LEVEL] [--log-max=SIZE] [--log-mode=MODE] [--memory-dump-interval=SECONDS] [--output=FILE] [-q] [--quiet] [--no-quiet] [--require-assumptions] [--no-require-assumptions] [-rSCENARIO] [--run=SCENARIO] [--shell=SHELL] [--shell-arg=ARG] [-sSHELL-LIBRARY] [--shell-library=SHELL-LIBRARY] [--snapshot] [--no-snapshot] [--stop-on-first-fail] [--no-stop-on-first-fail] [--tempdir=DIR] [--timings] [--no-timings] [-v] [--verbose] [--no-verbose] [-n] [--no-act] [--dry-run] [--pretend] [--no-no-act] [--no-dry-run] [--no-pretend] [FILE]...
yarn is a scenario testing tool: you write a scenario describing how a user uses your software and what should happen, and express, using very lightweight syntax, the scenario in such a way that it can be tested automatically.  The scenario has a simple, but strict structure:
GIVEN some setup for the test WHEN thing that is to be tested happens THEN the post-conditions must be true
As an example, consider a very short test scenario for verifying that a backup program works, at least for one simple case.
SCENARIO backups can be restored GIVEN some live data in a directory AND an empty backup repository WHEN a backup is made THEN the data case be restored FINALLY cleanup
Note the addition of AND: you can have multiple GIVEN, WHEN, and THEN statements. The AND keyword makes the text be more readable.  SCENARIO is also necessary, and gives the title.
FINALLY is for cleanups.  The FINALLY steps will be run regardless of whether the scenario succeeds or not.
Scenarios are meant to be written in somewhat human readable language. However, they are not free form text.  In addition to the GIVEN/WHEN/THEN structure, the text for each of the steps needs a computer-executable implementation.  This is done by using IMPLEMENTS.  The backup scenario from above might be implemented as follows:
IMPLEMENTS GIVEN some live data in a directory rm -rf "$DATADIR/data" mkdir "$DATADIR/data" echo foo > "$DATADIR/data/foo"
IMPLEMENTS GIVEN an empty backup repository rm -rf "$DATADIR/repo" mkdir "$DATADIR/repo"
IMPLEMENTS WHEN a backup is made backup-program -r "$DATADIR/repo" "$DATADIR/data"
IMPLEMENTS THEN the data can be restored mkdir "$DATADIR/restored" restore-program -r "$DATADIR/repo" "$DATADIR/restored" diff -rq "$DATADIR/data" "$DATADIR/restored"
IMPLEMENTS FINALLY cleanup echo nothing to do, actually
Each "IMPLEMENTS GIVEN" (or WHEN, THEN, FINALLY) is followed by a regular expression on the same line, and then a shell script that gets executed to implement any step that matches the regular expression.  The implementation can extract data from the match as well: for example, the regular expression might allow a file size to be specified.
The above example is a bit silly, of course: why go to the effort to obfuscate the various steps?  The answer is that the various steps, implemented using IMPLEMENTS, can be combined in many ways, to test different aspects of the program being tested.
Moreover, by making the step descriptions be human language text, matched by regular expressions, most of the test can hopefully be written, and understood, by non-programmers.  Someone who understands what a program should do, could write tests to verify its behaviour.  The implementations of the various steps need to be implemented by a programmer, but given a well-designed set of steps, with enough flexibility in their implementation, that quite a good test suite can be written.
The shell commands in an IMPLEMENTS section are run in the directory in which the user ran yarn.  The environment variable SRCDIR is set to the fully qualified path to that directory.
--allow-missing-steps allow scenarios to reference steps that do not exist, by warning about them, but otherwise ignoring the scenarios
--no-allow-missing-steps opposite of --allow-missing-steps
--cd-datadir change to DATADIR when running commands
--no-cd-datadir opposite of --cd-datadir
--env=NAME=VALUE add NAME=VALUE to the environment when tests are run
--generate-manpage=TEMPLATE fill in manual page TEMPLATE
--output=FILE write output to FILE, instead of standard output
-q, --quiet be quiet, avoid progress reporting, only show errors
--no-quiet opposite of --quiet
--require-assumptions require ASSUMING to always pass
--no-require-assumptions opposite of --require-assumptions
-r, --run=SCENARIO run only SCENARIO (this option can be repeated)
--shell=SHELL run IMPLEMENTS using SHELL
--shell-arg=ARG use ARG when running shell
-s, --shell-library=SHELL-LIBRARY include a shell library for the IMPLEMENTS sections to use
--snapshot make snapshots of test working directory after each scenario step; you probably want to use this with --tempdir
--no-snapshot opposite of --snapshot
--stop-on-first-fail stop if any scenario step fails, don't run more scenarios
--no-stop-on-first-fail opposite of --stop-on-first-fail
--tempdir=DIR use DIR as the temporary directory for tests; it should be empty or not exist
--timings report wall clock time for each scenario and step
--no-timings opposite of --timings
-v, --verbose make progress reporting be more verbose ("wall of text"), instead of a one-line status info; this is turned automatically if there is not terminal
--no-verbose opposite of --verbose
-n, --no-act, --dry-run, --pretend do not actually run any tests, merely print what would be run
--no-no-act, --no-dry-run, --no-pretend opposite of --no-act
Configuration files and settings --config=FILE add FILE to config files
--dump-config write out the entire current configuration
--dump-setting-names write out all names of settings and quit
--help-all show all options
--list-config-files list all possible config files
--no-default-configs clear list of configuration files to read
Logging --log=FILE write log entries to FILE (default is to not write log files at all); use "syslog" to log to system log, "stderr" to log to the standard error output, or "none" to disable logging
--log-keep=N keep last N logs (10)
--log-level=LEVEL log at LEVEL, one of debug, info, warning, error, critical, fatal (default: debug)
--log-max=SIZE rotate logs larger than SIZE, zero for never (default: 0)
--log-mode=MODE set permissions of new log files to MODE (octal; default 0600)
Peformance --dump-memory-profile=METHOD make memory profiling dumps using METHOD, which is one of: none, or simple (no meliae support anymore)(default: simple)
--memory-dump-interval=SECONDS make memory profiling dumps at least SECONDS apart
DATADIR Fully qualified pathname to a temporary directory, in which the tests can use files.  The temporary directory is removed at the end of the test execution, unless the user specifies otherwise with --snapshot.
SRCDIR Fully qualitifed pathname to the directory in which the user ran yarn.  This is useful when the tests want to change the directory.
To run yarn on all the scenarios in your current directory:
yarn *.scenario
All the files will be treated together as if they had been one file.
To add a shell library to be included when running any IMPLEMENTS section:
yarn --shell-library mylib.sh *.scenario
You can repeat --shell-library as many times as necessary.
cmdtest(1), cliapp(5).
The README.yarn file has more details on the scenario testing language.
GIT-EFFORT(1)                      Git Extras                      GIT-EFFORT(1)
git-effort - Show effort statistics on file(s)
git-effort [--above <value>] [<path>...] [-- [<log options>...]]
Shows effort statistics about files in the repository.
Display includes: - Commits: number of commits per file - highlighting files with most activity. - Active days: total number of days which contributed modifications to this file.
--above <value>
Ignore files with commits <= a value.
<path>...
Only count commits that touches the given paths.
Note: git-effort does not accept revision ranges, but the underlying git log does (See the examples).
<log options>...
Options for git log. Note that you must use -- to separate options to git log from options to git effort. This makes it possible to only count commits you are interested in. Not all options are relevant in the context of git-effort, but those that are is listed under the "Commit Limiting" section on the git-log manpages.
Note: Output will first appear unsorted, then the screen is cleared and the sorted list is output. The initial unsorted list is not shown in the examples for brevity.
Displays "effort" statistics:
$ git effort --above 5
file                                          commits    active days
git-extras                                    26         18 git-release                                   13         13 git-effort                                    13         2 git-ignore                                    11         7 git-changelog                                 11         8 git-graft                                     9          6 git-summary                                   8          6 git-delete-branch                             8          6 git-repl                                      7          5
$ git effort --above 5 bin/* -- --after="one year ago" --author="Leila Muhtasib"
git-extras                                    15         12 git-release                                   6          4 git-effort                                    6          2 git-ignore                                    4          4 git-changelog                                 3          2 git-graft                                     2          2
Showing statistics on directories is also possible:
$ git effort bin man -- --after="one year ago"
bin.......................................... 406        232 man.......................................... 118        80
Only count commits in the specified revision range:
$ git effort -- master..feature
bin/git-effort............................... 3          2 man/git-effort.md............................ 1          1
Written by Leila Muhtasib <muhtasib@gmail.com>
CPIO(1)                             GNU CPIO                             CPIO(1)
cpio - copy files to and from archives
cpio {-o|--create} [-0acvABLV] [-C BYTES] [-H FORMAT] [-M MESSAGE] [-O [[USER@]HOST:]ARCHIVE] [-F [[USER@]HOST:]ARCHIVE] [--file=[[USER@]HOST:]ARCHIVE] [--format=FORMAT] [--message=MESSAGE] [--null] [--reset-access-time] [--verbose] [--dot] [--append] [--block-size=blocks] [--dereference] [--io-size=BYTES] [--quiet] [--force-local] [--rsh-command=COMMAND] < name-list [> archive]
cpio {-i|--extract} [-bcdfmnrtsuvBSV] [-C BYTES] [-E FILE] [-H FORMAT] [-M MESSAGE] [-R [USER][:.][GROUP]] [-I [[USER@]HOST:]ARCHIVE] [-F [[USER@]HOST:]ARCHIVE] [--file=[[USER@]HOST:]ARCHIVE] [--make-directories] [--nonmatching] [--preserve-modification-time] [--numeric-uid-gid] [--rename] [--list] [--swap-bytes] [--swap] [--dot] [--unconditional] [--verbose] [--block-size=BLOCKS] [--swap-halfwords] [--io-size=BYTES] [--pattern-file=FILE] [--format=FORMAT] [--owner=[USER][:.][GROUP]] [--no-preserve-owner] [--message=MESSAGE] [--force-local] [--no-absolute-filenames] [--sparse] [--only-verify-crc] [--to-stdout] [--quiet] [--rsh-command=COMMAND] [pattern...] [< archive]
cpio {-p|--pass-through} [-0adlmuvLV] [-R [USER][:.][GROUP]] [--null] [--reset-access-time] [--make-directories] [--link] [--quiet] [--preserve-modification-time] [--unconditional] [--verbose] [--dot] [--dereference] [--owner=[USER][:.][GROUP]] [--no-preserve-owner] [--sparse] destination-directory < name-list
cpio {-?|--help|--usage|--version}
This manpage is a short description of GNU cpio.  For a detailed discussion, including examples and usage recommendations, refer to the GNU Cpio Manual available in texinfo format.  If the info reader and the cpio documentation are properly installed on your system, the command
info cpio
http://www.gnu.org/software/cpio/manual
If any discrepancies occur between this manpage and the GNU Cpio Manual, the later shall be considered the authoritative source.
GNU cpio copies files between archives and directories.  It supports the following archive formats: old binary cpio, old portable cpio, SVR4 cpio with and without checksum, HP cpio, and various tar formats.
The operation mode is requested by one of the following options:
-o, --create Copy-out.  Read a list of file names from the standard input and create on the standard output (unless overridden by the --file option) an archive containing these files.
-i, --extract Copy-in.  Read the archive from standard input (or from the file supplied with the --file option) and extract files from it, or (if the -t option is given) list its contents to the standard output. If one or more patterns are supplied, read or list only files matching these patterns.  The -t option alone implies -i.
-p, --pass-through Pass-through.  Read a list of file names from the standard input and copy them to the specified directory.
-?, --help Give a short help summary and exit.
--usage Print a short usage message and exit.
--version Print program version and exit.
Operation modifiers valid in any mode --block-size=BLOCK-SIZE Set the I/O block size to BLOCK-SIZE * 512 bytes.
-B     Set the I/O block size to 5120 bytes.
-c     Use the old portable (ASCII) archive format.  This is the same as -H odc.
-C, --io-size=NUMBER Set the I/O block size to the given NUMBER of bytes.
-D, --directory=DIR Change to directory DIR.
--force-local Archive file is local, even if its name contains colons.
-H, --format=FORMAT Use given archive FORMAT.  Valid formats are (the number in parentheses gives maximum size for individual archive member):
bin    The obsolete binary format.  (2147483647 bytes)
odc    The old (POSIX.1) portable format. (8589934591 bytes)
newc   The new (SVR4) portable format, which supports file systems having more than 65536 i-nodes. (4294967295 bytes)
crc    The new (SVR4) portable format with a checksum added.
tar    The old tar format. (8589934591 bytes)
ustar  The POSIX.1 tar format.  Also recognizes GNU tar archives, which are similar but not identical. (8589934591 bytes)
hpbin  The obsolete binary format used by HPUX's cpio (which stores device files differently).
hpodc  The portable format used by HPUX's cpio (which stores device files differently).
-R, --owner=[USER][:.][GROUP] In copy-in and copy-pass mode, set the ownership of all files created to the specified USER and/or GROUP.  In copy-out mode, store the supplied owner information in the archive.
USER and GROUP are first looked up in the system user and group databases.  If not found, cpio checks if they consist of decimal digits only and, if so, treats them as numeric UID and GID, correspondingly.
To avoid the lookup and ensure that arguments are treated as numeric values, prefix them with a plus sign, e.g.: -R +0:+0.
--quiet Do not print the number of blocks copied at the end of the run.
--rsh-command=COMMAND Use remote COMMAND instead of rsh.
-v, --verbose Verbosely list the files processed.
-V, --dot Print a "." for each file processed.
-W, --warning=FLAG Controlsи warning display.  The FLAG is one of none, to disable all warnings, all to enable them, truncate, to enable warnings about field truncation, and no-truncate, to disable them.
Multiple -W options accumulate.
Operation modifiers valid in copy-in and copy-out modes -F, --file=[[USER@]HOST:]ARCHIVE-FILE Use this ARCHIVE-FILE instead of standard input (in copy-in mode) or standard output (in copy-out mode).  Optional USER and HOST specify the user and host names in case of a remote archive.
-M, --message=STRING Print STRING when the end of a volume of the backup media is reached.
Operation modifiers valid only in copy-in mode -b, --swap Swap both halfwords of words and bytes of halfwords in the data. Equivalent to -sS.
-f, --nonmatching Only copy files that do not match any of the given patterns.
-n, --numeric-uid-gid In the verbose table of contents listing, show numeric UID and GID.
-r, --rename Interactively rename files.
-s, --swap-bytes Swap the bytes of each halfword in the files.
-S, --swap-halfwords Swap the halfwords of each word (4 bytes) in the files.
--to-stdout Extract files to standard output.
-E, --pattern-file=FILE Read additional patterns specifying filenames to extract or list from FILE.
--only-verify-crc When reading a CRC format archive, only verify the CRC's of each file in the archive, without actually extracting the files.
Operation modifiers valid only in copy-out mode -A, --append Append to an existing archive.
--device-independent, --reproducible Create reproducible archives.  This is equivalent to --ignore-devno --renumber-inodes.
--ignore-devno Store 0 in the device number field of each archive member, instead of the actual device number.
-O [[USER@]HOST:]ARCHIVE-NAME Use ARCHIVE-NAME instead of standard output. Optional USER and HOST specify the user and host names in case of a remote archive.
The output archive name can be specified wither using this option, or using -F (--file), but not both.
--renumber-inodes Renumber inodes when storing them in the archive.
Operation modifiers valid only in copy-pass mode -l, --link Link files instead of copying them, when possible.
Operation modifiers valid in copy-in and copy-out modes --absolute-filenames Do not strip file system prefix components from the file names. This is the default.
--no-absolute-filenames Create all files relative to the current directory.
Operation modifiers valid in copy-out and copy-pass modes -0, --null Filenames in the list are delimited by null characters instead of newlines.
-a, --reset-access-time Reset the access times of files after reading them.
-I [[USER@]HOST:]ARCHIVE-NAME Use ARCHIVE-NAME instead of standard input. Optional USER and HOST specify the user and host names in case of a remote archive.
The input archive name can be specified wither using this option, or using -F (--file), but not both.
-L, --dereference Dereference symbolic links (copy the files that they point to instead of copying the links).
Operation modifiers valid in copy-in and copy-pass modes -d, --make-directories Create leading directories where needed.
-m, --preserve-modification-time Retain previous file modification times when creating files.
--no-preserve-owner Do not change the ownership of the files.
--sparse Write files with large blocks of zeros as sparse files.
-u, --unconditional Replace all files unconditionally.
GNU cpio exits with code 0 if it was able to successfully complete the requested operation.  On errors, it exits with code 2.
tar(1), rmt(8), mt(1).
Report bugs to <bug-cpio@gnu.org>.
Copyright © 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it.  There is NO WARRANTY, to the extent permitted by law.
EMACS(1)                     General Commands Manual                    EMACS(1)
emacs - GNU project Emacs editor
emacs [ command-line switches ] [ files ... ]
GNU Emacs is a version of Emacs, written by the author of the original (PDP-10) Emacs, Richard Stallman.  The user functionality of GNU Emacs encompasses everything other editors do, and it is easily extensible since its editing commands are written in Lisp.
The primary documentation of GNU Emacs is in the GNU Emacs Manual, which you can read using Info, either from Emacs or as a standalone program. Please look there for complete and up-to-date documentation.  This man page is updated only when someone volunteers to do so.
Emacs has an extensive interactive help facility, but the facility assumes that you know how to manipulate Emacs windows and buffers.  CTRL- h or F1 enters the Help facility.  Help Tutorial (CTRL-h t) starts an interactive tutorial to quickly teach beginners the fundamentals of Emacs.  Help Apropos (CTRL-h a) helps you find a command with a name matching a given pattern, Help Key (CTRL-h k) describes a given key sequence, and Help Function (CTRL-h f) describes a given Lisp function.
GNU Emacs's many special packages handle mail reading (RMail) and sending (Mail), outline editing (Outline), compiling (Compile), running subshells within Emacs windows (Shell), running a Lisp read-eval-print loop (Lisp- Interaction-Mode), automated psychotherapy (Doctor), and much more.
Emacs Options The following options are of general interest:
file    Edit file.
--file=file, --find-file=file, --visit=file The same as specifying file directly as an argument.
+number Go to the line specified by number (do not insert a space between the "+" sign and the number).  This applies only to the next file specified.
+line:column Go to the specified line and column.
--chdir=directory Change to directory.
-q, --no-init-file Do not load an init file.
-nl, --no-shared-memory Do not use shared memory.
--no-site-file Do not load the site-wide startup file.
-nsl, --no-site-lisp Do not add site-lisp directories to load-path.
--no-desktop Do not load a saved desktop.
-Q, --quick Similar to "-q --no-site-file --no-splash".  Also, avoid processing X resources.
--no-splash Do not display a splash screen during start-up.
--debug-init Enable Emacs Lisp debugger during the processing of the user init file ~/.emacs.  This is useful for debugging problems in the init file.
-u user, --user=user Load user's init file.
-t file, --terminal=file Use specified file as the terminal instead of using stdin/stdout.  This must be the first argument specified in the command line.
--daemon[=name], --bg-daemon[=name] Start Emacs as a daemon, enabling the Emacs server and disconnecting from the terminal.  You can then use the emacsclient (see emacsclient(1)) command to connect to the server (with optional name).
--fg-daemon[=name] Like "--bg-daemon", but don't disconnect from the terminal.
--version Display Emacs version information and exit.
--help  Display this help and exit.
The following options are Lisp-oriented (these options are processed in the order encountered):
-f function, --funcall=function Execute the lisp function function.
-l file, --load=file Load the lisp code in the file file.
--eval=expr, --execute=expr Evaluate the Lisp expression expr.
The following options are useful when running Emacs as a batch editor:
--batch Edit in batch mode.  The editor will send messages to stderr.  You must use -l and -f options to specify files to execute and functions to call.
--script file Run file as an Emacs Lisp script.
--insert=file Insert contents of file into the current buffer.
--kill  Exit Emacs while in batch mode.
-L dir, --directory=dir Add dir to the list of directories Emacs searches for Lisp files.
Using Emacs with X Emacs has been tailored to work well with the X window system.  If you run Emacs from under X windows, it will create its own X window to display in.  You will probably want to start the editor as a background process so that you can continue using your original window.
Emacs can be started with the following X switches:
--name=name Specify the name which should be assigned to the initial Emacs window.  This controls looking up X resources as well as the window title.
-T name, --title=name Specify the title for the initial X window.
-r, -rv, --reverse-video Display the Emacs window in reverse video.
-fn font, --font=font Set the Emacs window's font to that specified by font. You will find the various X fonts in the /usr/lib/X11/fonts directory.  Note that Emacs will only accept fixed width fonts.  Under the X11 Release 4 font- naming conventions, any font with the value "m" or "c" in the eleventh field of the font name is a fixed width font. Furthermore, fonts whose name are of the form widthxheight are generally fixed width, as is the font fixed.  See xlsfonts(1) for more information.
When you specify a font, be sure to put a space between the switch and the font name.
--xrm=resources Set additional X resources.
--color, --color=mode Override color mode for character terminals; mode defaults to "auto", and can also be "never", "auto", "always", or a mode name like "ansi8".
-bw pixels, --border-width=pixels Set the Emacs window's border width to the number of pixels specified by pixels.  Defaults to one pixel on each side of the window.
-ib pixels, --internal-border=pixels Set the window's internal border width to the number of pixels specified by pixels.  Defaults to one pixel of padding on each side of the window.
-g geometry, --geometry=geometry Set the Emacs window's width, height, and position as specified.  The geometry specification is in the standard X format; see X(7) for more information.  The width and height are specified in characters; the default for GUI frames is a width of 80 and a height between 35 and 40, depending on the OS and the window manager.  See the Emacs manual, section "Options for Window Size and Position", for information on how window sizes interact with selecting or deselecting the tool bar, tab bar and menu bar.
-lsp pixels, --line-spacing=pixels Additional space to put between lines.
-vb, --vertical-scroll-bars Enable vertical scrollbars.
-fh, --fullheight Make the first frame as high as the screen.
-fs, --fullscreen Make the first frame fullscreen.
-fw, --fullwidth Make the first frame as wide as the screen.
-mm, --maximized Maximize the first frame, like "-fw -fh".
-fg color, --foreground-color=color On color displays, set the color of the text.
Use the command M-x list-colors-display for a list of valid color names.
-bg color, --background-color=color On color displays, set the color of the window's background.
-bd color, --border-color=color On color displays, set the color of the window's border.
-cr color, --cursor-color=color On color displays, set the color of the window's text cursor.
-ms color, --mouse-color=color On color displays, set the color of the window's mouse cursor.
-d displayname, --display=displayname Create the Emacs window on the display specified by displayname.  Must be the first option specified in the command line.
-nbi, --no-bitmap-icon Do not use picture of gnu for Emacs icon.
--iconic Start Emacs in iconified state.
-nbc, --no-blinking-cursor Disable blinking cursor.
--parent-id=xid Set parent window.
-nw, --no-window-system Tell Emacs not to create a graphical frame.  If you use this switch when invoking Emacs from an xterm(1) window, display is done in that window.
-D, --basic-display This option disables many display features; use it for debugging Emacs.
You can set X default values for your Emacs windows in your .Xresources file (see xrdb(1)).  Use the following format:
emacs.keyword:value
where value specifies the default value of keyword.  Emacs lets you set default values for the following keywords:
background (class Background) For color displays, sets the window's background color.
bitmapIcon (class BitmapIcon) If bitmapIcon's value is set to on, the window will iconify into the "kitchen sink."
borderColor (class BorderColor) For color displays, sets the color of the window's border.
borderWidth (class BorderWidth) Sets the window's border width in pixels.
cursorColor (class Foreground) For color displays, sets the color of the window's text cursor.
cursorBlink (class CursorBlink) Specifies whether to make the cursor blink.  The default is on.  Use off or false to turn cursor blinking off.
font (class Font) Sets the window's text font.
foreground (class Foreground) For color displays, sets the window's text color.
fullscreen (class Fullscreen) The desired fullscreen size.  The value can be one of fullboth, maximized, fullwidth, or fullheight, which correspond to the command-line options "-fs", "-mm", "-fw", and "-fh", respectively.  Note that this applies to the initial frame only.
geometry (class Geometry) Sets the geometry of the Emacs window (as described above).
iconName (class Title) Sets the icon name for the Emacs window icon.
internalBorder (class BorderWidth) Sets the window's internal border width in pixels.
lineSpacing (class LineSpacing) Additional space ("leading") between lines, in pixels.
menuBar (class MenuBar) Gives frames menu bars if on; don't have menu bars if off. See the Emacs manual, sections "Lucid Resources" and "Motif Resources", for how to control the appearance of the menu bar if you have one.
minibuffer (class Minibuffer) If none, don't make a minibuffer in this frame.  It will use a separate minibuffer frame instead.
paneFont (class Font) Font name for menu pane titles, in non-toolkit versions of Emacs.
pointerColor (class Foreground) For color displays, sets the color of the window's mouse cursor.
privateColormap (class PrivateColormap) If on, use a private color map, in the case where the "default visual" of class PseudoColor and Emacs is using it.
reverseVideo (class ReverseVideo) If reverseVideo's value is set to on, the window will be displayed in reverse video.
screenGamma (class ScreenGamma) Gamma correction for colors, equivalent to the frame parameter "screen-gamma".
scrollBarWidth (class ScrollBarWidth) The scroll bar width in pixels, equivalent to the frame parameter "scroll-bar-width".
selectionFont (class SelectionFont) Font name for pop-up menu items, in non-toolkit versions of Emacs.  (For toolkit versions, see the Emacs manual, sections "Lucid Resources" and "Motif Resources".)
selectionTimeout (class SelectionTimeout) Number of milliseconds to wait for a selection reply.  A value of 0 means wait as long as necessary.
synchronous (class Synchronous) Run Emacs in synchronous mode if on.  Synchronous mode is useful for debugging X problems.
title (class Title) Sets the title of the Emacs window.
toolBar (class ToolBar) Number of lines to reserve for the tool bar.
tabBar (class TabBar) Number of lines to reserve for the tab bar.
useXIM (class UseXIM) Turns off use of X input methods (XIM) if false or off.
verticalScrollBars (class ScrollBars) Gives frames scroll bars if on; suppresses scroll bars if off.
visualClass (class VisualClass) Specify the "visual" that X should use.  This tells X how to handle colors.  The value should start with one of TrueColor, PseudoColor, DirectColor, StaticColor, GrayScale, and StaticGray, followed by -depth, where depth is the number of color planes.
You can order printed copies of the GNU Emacs Manual from the Free Software Foundation, which develops GNU software.  See the online store at <https://shop.fsf.org/>. Your local administrator might also have copies available.  As with all software and publications from FSF, everyone is permitted to make and distribute copies of the Emacs manual.  The Texinfo source to the manual is also included in the Emacs source distribution.
/usr/local/share/info — files for the Info documentation browser.  The complete text of the Emacs reference manual is included in a convenient tree structured form.  Also includes the Emacs Lisp Reference Manual, useful to anyone wishing to write programs in the Emacs Lisp extension language, and the Introduction to Programming in Emacs Lisp.
/usr/local/share/emacs/$VERSION/lisp — Lisp source files and compiled files that define most editing commands.  Some are preloaded; others are autoloaded from this directory when used.
/usr/local/libexec/emacs/$VERSION/$ARCH — various programs that are used with GNU Emacs.
/usr/local/share/emacs/$VERSION/etc — various files of information.
/usr/local/share/emacs/$VERSION/etc/DOC.* — contains the documentation strings for the Lisp primitives and preloaded Lisp functions of GNU Emacs.  They are stored here to reduce the size of Emacs proper.
There is a mailing list, bug-gnu-emacs@gnu.org, for reporting Emacs bugs and fixes.  But before reporting something as a bug, please try to be sure that it really is a bug, not a misunderstanding or a deliberate feature.  We ask you to read the section "Reporting Bugs" in the Emacs manual for hints on how and when to report bugs.  Also, include the version number of the Emacs you are running in every bug report that you send in.  Bugs tend actually to be fixed if they can be isolated, so it is in your interest to report them in such a way that they can be easily reproduced.