neulab/tldr huggingface dataset:
-r0    Similar to -r, but when used with the commands 'a', 'u', 'f', 'm' will recurse subdirectories only for wildcard names.
-rr[N] Add data recovery record.
-rv[N] Create recovery volumes.  -s Create solid archive.
-s<N>  Create solid groups using file count. Similar to -s, but reset solid statistics after compressing <N> files.
-se    Create solid groups using extension. Similar to -s, but reset solid statistics if file extension is changed.
-sv    Create independent solid volumes. Similar to -s, but reset solid statistics as soon as possible when starting a new volume.
-sv-   Create dependent solid volumes. Similar to -s, but reset of solid statistics is disabled.
-s-    Disable solid archiving.
-sc<chr>[obj] Specify the character set.
-sfx[name] Create SFX archives.  The archive is merged with SFX-module "name" in the user's home directory.  The default module is taken from /usr/lib/default.sfx.  Please be aware that you have to accompany the result with /usr/share/doc/rar/acknow.txt on distribution, which holds 3rd party licenses that apply to default.sfx.
-si[name] Read data from standard input (stdin).
-sl<size> Process files with size less than specified.
-sm<size> Process files with size more than specified.
-t     Test files after archiving. This switch is especially useful in combination with the move command, so files will be deleted only if the archive has been successfully tested.
-ta<date> Process files modified after <date> in YYYYMMDDHHMMSS format.
-tb<date> Process files modified before <date> in YYYYMMDDHHMMSS format.
-tk    Keep original archive time. Prevents rar from modifying the archive date when changing an archive.
-tl    Set archive time to latest file. Forces rar to set the date of a changed archive to the date of the newest file in the archive.
-tn<time> Process files newer than <time>.
-to<time> Process files older than <time>.
-ts[m|c|a] Save or restore file time (modification, creation, access).
-v<size>[k|b] Create volumes with size=<size>*1000 [*1024, *1] bytes.
-ver[n] File version control.
-vn    Use the old style volume naming scheme.
-vp    Pause before each volume.
-w<path> Assign work directory.
-x<file> Exclude specified file. Wildcards may be used and you may specify the switch '-x' several times.
-z[file] Read archive comment from file.  If [file] is not present, comment is read from stdin.
The program is documented fully in rar.txt which you find in /usr/share/doc/rar.
This manual page was written by Petr Cech <cech@debian.org> according to "rar -?" for the Debian GNU/Linux system (but may be used by others).
HUGO(1)                            Hugo Manual                           HUGO(1)
hugo - hugo builds your site
hugo [flags]
hugo is the main command, used to build your Hugo site.
Hugo is a Fast and Flexible Static Site Generator built with love by spf13 and friends in Go.
Complete documentation is available at http://gohugo.io/.
-b, --baseURL=""      hostname (and path) to the root, e.g. http://spf13.com/
-D, --buildDrafts[=false]      include content marked as draft
-E, --buildExpired[=false]      include expired content
-F, --buildFuture[=false]      include content with publishdate in the future
--cacheDir=""      filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache/
--cleanDestinationDir[=false]      remove files from destination not found in static directories
--config=""      config file (default is path/config.yaml|json|toml)
--configDir="config"      config dir
-c, --contentDir=""      filesystem path to content directory
--debug[=false]      debug output
-d, --destination=""      filesystem path to write files to
--disableKinds=[]      disable different kind of pages (home, RSS etc.)
--enableGitInfo[=false]      add Git revision, date and author info to the pages
-e, --environment=""      build environment
--forceSyncStatic[=false]      copy all files when static is changed.
--gc[=false]      enable to run some cleanup tasks (remove unused cache files) after the build
-h, --help[=false]      help for hugo
--i18n-warnings[=false]      print missing translations
--ignoreCache[=false]      ignores the cache directory
--ignoreVendor[=false]      ignores any _vendor directory
--ignoreVendorPaths=""      ignores any _vendor for module paths matching the given Glob pattern
-l, --layoutDir=""      filesystem path to layout directory
--log[=false]      enable Logging
--logFile=""      log File path (if set, logging enabled automatically)
--minify[=false]      minify any supported output format (HTML, XML etc.)
--noChmod[=false]      don't sync permission mode of files
--noTimes[=false]      don't sync modification time of files
--path-warnings[=false]      print warnings on duplicate target paths etc.
--poll=""      set this to a poll interval, e.g --poll 700ms, to use a poll based approach to watch for file system changes
--print-mem[=false]      print memory usage to screen at intervals
--quiet[=false]      build in quiet mode
--renderToMemory[=false]      render to memory (only useful for benchmark testing)
-s, --source=""      filesystem path to read files relative from
--templateMetrics[=false]      display metrics about template executions
--templateMetricsHints[=false]      calculate some improvement hints when combined with --templateMetrics
-t, --theme=[]      themes to use (located in /themes/THEMENAME/)
--themesDir=""      filesystem path to themes directory
--trace=""      write trace to file (not useful in general)
-v, --verbose[=false]      verbose output
--verboseLog[=false]      verbose logging
-w, --watch[=false]      watch filesystem for changes and recreate as needed
hugo-completion(1), hugo-config(1), hugo-convert(1), hugo-deploy(1), hugo-env(1), hugo-gen(1), hugo-import(1), hugo-list(1), hugo-mod(1), hugo-new(1), hugo-server(1), hugo-version(1)
MODINFO(8)                           modinfo                          MODINFO(8)
modinfo - Show information about a Linux Kernel module
modinfo [-0] [-F field] [-k kernel] [modulename|filename...]
modinfo -V
modinfo -h
modinfo extracts information from the Linux Kernel modules given on the command line. If the module name is not a filename, then the /lib/modules/version directory is searched, as is also done by modprobe(8) when loading kernel modules.
modinfo by default lists each attribute of the module in form fieldname : value, for easy reading. The filename is listed the same way (although it's not really an attribute).
This version of modinfo can understand modules of any Linux Kernel architecture.
-V, --version Print the modinfo version.
-F, --field Only print this field value, one per line. This is most useful for scripts. Field names are case-insensitive. Common fields (which may not be in every module) include author, description, license, parm, depends, and alias. There are often multiple parm, alias and depends fields. The special field filename lists the filename of the module.
-b basedir, --basedir basedir Root directory for modules, / by default.
-k kernel Provide information about a kernel other than the running one. This is particularly useful for distributions needing to extract information from a newly installed (but not yet running) set of kernel modules. For example, you wish to find which firmware files are needed by various modules in a new kernel for which you must make an initrd/initramfs image prior to booting.
-0, --null Use the ASCII zero character to separate field values, instead of a new line. This is useful for scripts, since a new line can theoretically appear inside a field.
-a --author, -d --description, -l --license, -p --parameters, -n --filename These are shortcuts for the --field flag's author, description, license, parm and filename arguments, to ease the transition from the old modutils modinfo.
This manual page originally Copyright 2003, Rusty Russell, IBM Corporation. Maintained by Jon Masters and others.
modprobe(8)
NUMFMT(1)                         User Commands                        NUMFMT(1)
numfmt - Convert numbers from/to human-readable strings
numfmt [OPTION]... [NUMBER]...
Reformat NUMBER(s), or the numbers from standard input if none are specified.
--debug print warnings about invalid input
-d, --delimiter=X use X instead of whitespace for field delimiter
--field=FIELDS replace the numbers in these input fields (default=1); see FIELDS below
--format=FORMAT use printf style floating-point FORMAT; see FORMAT below for details
--from=UNIT auto-scale input numbers to UNITs; default is 'none'; see UNIT below
--from-unit=N specify the input unit size (instead of the default 1)
--grouping use locale-defined grouping of digits, e.g. 1,000,000 (which means it has no effect in the C/POSIX locale)
--header[=N] print (without converting) the first N header lines; N defaults to 1 if not specified
--invalid=MODE failure mode for invalid numbers: MODE can be: abort (default), fail, warn, ignore
--padding=N pad the output to N characters; positive N will right-align; negative N will left-align; padding is ignored if the output is wider than N; the default is to automatically pad if a whitespace is found
--round=METHOD use METHOD for rounding when scaling; METHOD can be: up, down, from-zero (default), towards-zero, nearest
--suffix=SUFFIX add SUFFIX to output numbers, and accept optional SUFFIX in input numbers
--to=UNIT auto-scale output numbers to UNITs; see UNIT below
--to-unit=N the output unit size (instead of the default 1)
-z, --zero-terminated line delimiter is NUL, not newline
UNIT options: none   no auto-scaling is done; suffixes will trigger an error
auto   accept optional single/two letter suffix:
1K = 1000, 1Ki = 1024, 1M = 1000000, 1Mi = 1048576,
si     accept optional single letter suffix:
1K = 1000, 1M = 1000000, ...
iec    accept optional single letter suffix:
1K = 1024, 1M = 1048576, ...
iec-i  accept optional two-letter suffix:
1Ki = 1024, 1Mi = 1048576, ...
FIELDS supports cut(1) style field ranges: N      N'th field, counted from 1
N-     from N'th field, to end of line
N-M    from N'th to M'th field (inclusive)
-M     from first to M'th field (inclusive)
-      all fields
Multiple fields/ranges can be separated with commas
FORMAT must be suitable for printing one floating-point argument '%f'. Optional quote (%'f) will enable --grouping (if supported by current locale).  Optional width value (%10f) will pad output. Optional zero (%010f) width will zero pad the number. Optional negative values (%-10f) will left align.  Optional precision (%.1f) will override the input determined precision.
Exit status is 0 if all input numbers were successfully converted.  By default, numfmt will stop at the first conversion error with exit status 2.  With --invalid='fail' a warning is printed for each conversion error and the exit status is 2.  With --invalid='warn' each conversion error is diagnosed, but the exit status is 0.  With --invalid='ignore' conversion errors are not diagnosed and the exit status is 0.
$ numfmt --to=si 1000
-> "1.0K"
$ numfmt --to=iec 2048
-> "2.0K"
$ numfmt --to=iec-i 4096
-> "4.0Ki"
$ echo 1K | numfmt --from=si
-> "1000"
$ echo 1K | numfmt --from=iec
-> "1024"
$ df -B1 | numfmt --header --field 2-4 --to=si $ ls -l  | numfmt --header --field 5 --to=iec $ ls -lh | numfmt --header --field 5 --from=iec --padding=10 $ ls -lh | numfmt --header --field 5 --from=iec --format %10f
Written by Assaf Gordon.
Full documentation <https://www.gnu.org/software/coreutils/numfmt> or available locally via: info '(coreutils) numfmt invocation'
loc(3f)                                                                  loc(3f)
Name loc - returns the address of an object
Syntax integer loc, addr, arg external loc addr = loc ( arg )
Description The returned value is the address of arg.
Files libU77.a
Bugs The memory address pointers addr should be integer*8 on 64 bit machines, such as DEC Alpha's and the SGI machines running IRIX64. On machines with a 32 bit memory the address pointers addr should be integer*4.
BISON(1)                          User Commands                         BISON(1)
bison - GNU Project parser generator (yacc replacement)
bison [OPTION]... FILE
Bison is a parser generator in the style of yacc(1).  It should be upwardly compatible with input files designed for yacc.
Input files should follow the yacc convention of ending in .y.  Unlike yacc, the generated files do not have fixed names, but instead use the prefix of the input file.  Moreover, if you need to put C++ code in the input file, you can end his name by a C++-like extension (.ypp or .y++), then bison will follow your extension to name the output file (.cpp or .c++).  For instance, a grammar description file named parse.yxx would produce the generated parser in a file named parse.tab.cxx, instead of yacc's y.tab.c or old Bison version's parse.tab.c.
This description of the options that can be given to bison is adapted from the node Invocation in the bison.texi manual, which should be taken as authoritative.
Bison supports both traditional single-letter options and mnemonic long option names.  Long option names are indicated with -- instead of -. Abbreviations for option names are allowed as long as they are unique. When a long option takes an argument, like --file-prefix, connect the option name and the argument with =.
Generate a deterministic LR or generalized LR (GLR) parser employing LALR(1), IELR(1), or canonical LR(1) parser tables.
Mandatory arguments to long options are mandatory for short options too. The same is true for optional arguments.
Operation Modes: -h, --help display this help and exit
--print-localedir output directory containing locale-dependent data and exit
--print-datadir output directory containing skeletons and XSLT and exit
-u, --update apply fixes to the source grammar file and exit
-f, --feature[=FEATURES] activate miscellaneous features
FEATURES is a list of comma separated words that can include: caret, diagnostics-show-caret show errors with carets
fixit, diagnostics-parseable-fixits show machine-readable fixes
syntax-only do not generate any file
all    all of the above
none   disable all of the above
Diagnostics: -W, --warnings[=CATEGORY] report the warnings falling in CATEGORY
--color[=WHEN] whether to colorize the diagnostics
--style=FILE specify the CSS FILE for colorizer diagnostics
Warning categories include: conflicts-sr S/R conflicts (enabled by default)
conflicts-rr R/R conflicts (enabled by default)
counterexamples, cex generate conflict counterexamples
dangling-alias string aliases not attached to a symbol
deprecated obsolete constructs
empty-rule empty rules without %empty
midrule-values unset or unused midrule values
precedence useless precedence and associativity
yacc   incompatibilities with POSIX Yacc
other  all other warnings (enabled by default)
all    all the warnings except 'counterexamples', 'dangling-alias' and 'yacc'
no-CATEGORY turn off warnings in CATEGORY
none   turn off all the warnings
error[=CATEGORY] treat warnings as errors
WHEN can be one of the following: always, yes colorize the output
never, no don't colorize the output
auto, tty colorize if the output device is a tty
Tuning the Parser: -L, --language=LANGUAGE specify the output programming language
-S, --skeleton=FILE specify the skeleton to use
-t, --debug instrument the parser for tracing same as '-Dparse.trace'
--locations enable location support
-D, --define=NAME[=VALUE] similar to '%define NAME VALUE'
-F, --force-define=NAME[=VALUE] override '%define NAME VALUE'
-p, --name-prefix=PREFIX prepend PREFIX to the external symbols deprecated by '-Dapi.prefix={PREFIX}'
-l, --no-lines don't generate '#line' directives
-k, --token-table include a table of token names
-y, --yacc emulate POSIX Yacc
Output Files: -H, --header=[FILE] also produce a header file
-d     likewise but cannot specify FILE (for POSIX Yacc)
-r, --report=THINGS also produce details on the automaton
--report-file=FILE write report to FILE
-v, --verbose same as '--report=state'
-b, --file-prefix=PREFIX specify a PREFIX for output files
-o, --output=FILE leave output to FILE
-g, --graph[=FILE] also output a graph of the automaton
--html[=FILE] also output an HTML report of the automaton
-x, --xml[=FILE] also output an XML report of the automaton
-M, --file-prefix-map=OLD=NEW replace prefix OLD with NEW when writing file paths in output files
THINGS is a list of comma separated words that can include: states describe the states
itemsets complete the core item sets with their closure
lookaheads explicitly associate lookahead tokens to items
solved describe shift/reduce conflicts solving
all    include all the above information
none   disable the report
Written by Robert Corbett and Richard Stallman.
Report bugs to <bug-bison@gnu.org>. GNU Bison home page: <https://www.gnu.org/software/bison/>. General help using GNU software: <https://www.gnu.org/gethelp/>. For complete documentation, run: info bison.
Copyright Â© 2021 Free Software Foundation, Inc. This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
lex(1), flex(1), yacc(1).
The full documentation for bison is maintained as a Texinfo manual.  If the info and bison programs are properly installed at your site, the command
info bison
restic backup(1)                                                restic backup(1)
restic - Backup and restore files
restic [flags]
restic is a backup program which allows saving multiple revisions of files and directories in an encrypted repository stored on different backends.
--cacert=[]      file to load root certificates from (default: use system certificates)
--cache-dir=""      set the cache directory. (default: use system default cache directory)
--cleanup-cache[=false]      auto remove old cache directories
-h, --help[=false]      help for restic
--json[=false]      set output mode to JSON for commands that support it
--key-hint=""      key ID of key to try decrypting first (default: $RESTIC_KEY_HINT)
--limit-download=0      limits downloads to a maximum rate in KiB/s. (default: unlimited)
--limit-upload=0      limits uploads to a maximum rate in KiB/s. (default: unlimited)
--no-cache[=false]      do not use a local cache
--no-lock[=false]      do not lock the repository, this allows some operations on read-only repositories
-o, --option=[]      set extended option (key=value, can be specified multiple times)
--password-command=""      shell command to obtain the repository password from (default: $RESTIC_PASSWORD_COMMAND)
-p, --password-file=""      file to read the repository password from (default: $RESTIC_PASSWORD_FILE)
-q, --quiet[=false]      do not output comprehensive progress report
-r, --repo=""      repository to backup to or restore from (default: $RESTIC_REPOSITORY)
--repository-file=""      file to read the repository location from (default: $RESTIC_REPOSITORY_FILE)
--tls-client-cert=""      path to a file containing PEM encoded TLS client certificate and private key
-v, --verbose[=0]      be verbose (specify multiple times or a level using --verbose=n, max level/times is 3)
restic-backup(1), restic-cache(1), restic-cat(1), restic-check(1), restic-copy(1), restic-diff(1), restic-dump(1), restic-find(1), restic-forget(1), restic-generate(1), restic-init(1), restic-key(1), restic-list(1), restic-ls(1), restic-migrate(1), restic-mount(1), restic-prune(1), restic-rebuild-index(1), restic-recover(1), restic-restore(1), restic-self-update(1), restic-snapshots(1), restic-stats(1), restic-tag(1), restic-unlock(1), restic-version(1)
RFKILL(8)                     System Administration                    RFKILL(8)
rfkill - tool for enabling and disabling wireless devices
rfkill [options] [command] [ID|type ...]
rfkill lists, enabling and disabling wireless devices.
The command "list" output format is deprecated and maintained for backward compatibility only. The new output format is the default when no command is specified or when the option --output is used.
The default output is subject to change. So whenever possible, you should avoid using default outputs in your scripts. Always explicitly define expected columns by using the --output option together with a columns list in environments where a stable output is required.
-o, --output Specify which output columns to print. Use --help to get a list of available columns.
--help Display help text and exit.
help Display help text and exit.
event Listen for rfkill events and display them on stdout.
list [id|type ...] List the current state of all available devices. The command output format is deprecated, see the section DESCRIPTION. It is a good idea to check with list command id or type scope is appropriate before setting block or unblock. Special all type string will match everything. Use of multiple ID or type arguments is supported.
block id|type [...] Disable the corresponding device.
unblock id|type [...] Enable the corresponding device. If the device is hard-blocked, for example via a hardware switch, it will remain unavailable though it is now soft-unblocked.
toggle id|type [...] Enable or disable the corresponding device.
rfkill --output ID,TYPE rfkill block all rfkill unblock wlan rfkill block bluetooth uwb wimax wwan gps fm nfc
rfkill was originally written by Johannes Berg <johannes@sipsolutions.net> and Marcel Holtmann <marcel@holtmann.org>. The code has been later modified by Sami Kerola <kerolasa@iki.fi> and Karel Zak <kzak@redhat.com> for the util-linux project.
This manual page was written by Darren Salt <linux@youmustbejoking.demon.co.uk> for the Debian project (and may be used by others).
powertop(8), systemd-rfkill(8), Linux kernel documentation <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/driver-api/rfkill.rst>
The rfkill 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/>.
MONGOEXPORT(1)               General Commands Manual              MONGOEXPORT(1)
mongoexport - export MongoDB data from a server in CSV or JSON format
mongoexport [options]
The mongoexport program allows exporting the contents of a running MongoDB instance to in CSV or JSON format.
See mongoexport --help for a list supported options and their descriptions.
mongoimport(1)
The full documentation of mongoexport can be found at https://docs.mongodb.com/manual/reference/program/mongoexport/.
mongoexport was written by MongoDB, Inc. and is licensed under the Apache License, Version 2.0.
This manpage was written by Apollon Oikonomopoulos <apoikos@debian.org> for the Debian project (but may be used by others).
VPNC(8)                  System Administration Utilities                 VPNC(8)
vpnc - client for Cisco VPN3000 Concentrator, IOS and PIX
vpnc [--version] [--print-config] [--help] [--long-help] [options] [config files]
This manual page documents briefly the vpnc and vpnc-disconnect commands.
vpnc is a VPN client for the Cisco 3000 VPN  Concentrator,  creating  a IPSec-like connection as a tunneling network device for the local system. It uses the TUN/TAP driver in  Linux  kernel  2.4  and  above  and device tun(4) on BSD. The created connection is presented as a tunneling network device to the local system.
OBLIGATORY WARNING: the most used configuration (XAUTH authentication with pre-shared keys and password authentication) is insecure by design, be aware of this fact when you use vpnc to exchange sensitive data like passwords!
The vpnc daemon by itself does not set any routes, but it calls vpnc-script to do this job. vpnc-script displays a connect banner. If the concentrator supplies a network list for split-tunneling these networks are added to the routing table.  Otherwise the default-route will be modified to point to the tunnel.  Further a host route to the concentrator is added in the later case.  If the client host needs DHCP, care must be taken to add another host route to the DHCP-Server around the tunnel.
The vpnc-disconnect command is used to terminate the connection previously created by vpnc and restore the previous routing configuration.
The daemon reads configuration data from the following places: •      command line options •      config file(s) specified on the command line •      /etc/vpnc/default.conf •      /etc/vpnc.conf •      prompting the user if not found above
vpnc can parse options and configuration files in any order. However the first place to set an option wins.  configuration filenames which do not contain a / will be searched at /etc/vpnc/<filename> and /etc/vpnc/<filename>.conf.  Otherwise <filename> and <filename>.conf will be used.  If no configuration file is specified on the command-line at all, both /etc/vpnc/default.conf and /etc/vpnc.conf will be loaded.
Additionally, if the configuration file "-" is specified on the command- line vpnc will read configuration from stdin.  The configuration is parsed and the connection proceeds when stdin is closed or the special character CEOT (CTRL-D) is read.
The program options can be either given as arguments (but not all of them for security reasons) or be stored in a configuration file.
--gateway <ip/hostname> IP/name of your IPSec gateway conf-variable: IPSec gateway <ip/hostname>
--id <ASCII string> your group name conf-variable: IPSec ID <ASCII string>
--secret <ASCII string> your group password (cleartext) conf-variable: IPSec secret <ASCII string>
(configfile only option) your group password (obfuscated) conf-variable: IPSec obfuscated secret <hex string>
--username <ASCII string> your username conf-variable: Xauth username <ASCII string>
--password <ASCII string> your password (cleartext) conf-variable: Xauth password <ASCII string>
(configfile only option) your password (obfuscated) conf-variable: Xauth obfuscated password <hex string>
--domain <ASCII string> (NT-) Domain name for authentication conf-variable: Domain <ASCII string>
--xauth-inter enable interactive extended authentication (for challenge response auth) conf-variable: Xauth interactive
--vendor <cisco/netscreen/fortigate> vendor of your IPSec gateway Default: cisco conf-variable: Vendor <cisco/netscreen/fortigate>
--natt-mode <natt/none/force-natt/cisco-udp> Which NAT-Traversal Method to use: •      natt -- NAT-T as defined in RFC3947 •      none -- disable use of any NAT-T method •      force-natt -- always use NAT-T encapsulation even without presence of a NAT device (useful if the OS captures all ESP traffic) •      cisco-udp -- Cisco proprietary UDP encapsulation, commonly over Port 10000 Note: cisco-tcp encapsulation is not yet supported Default: natt conf-variable: NAT Traversal Mode <natt/none/force-natt/cisco-udp>
--script <command> command is executed using system() to configure the interface, routing and so on. Device name, IP, etc. are passed using environment variables, see README. This script is executed right after ISAKMP is done, but before tunneling is enabled. It is called when vpnc terminates, too Default: /etc/vpnc/vpnc-script conf-variable: Script <command>
--dh <dh1/dh2/dh5> name of the IKE DH Group Default: dh2 conf-variable: IKE DH Group <dh1/dh2/dh5>
--pfs <nopfs/dh1/dh2/dh5/server> Diffie-Hellman group to use for PFS Default: server conf-variable: Perfect Forward Secrecy <nopfs/dh1/dh2/dh5/server>
--enable-1des enables weak single DES encryption conf-variable: Enable Single DES
--enable-no-encryption enables using no encryption for data traffic (key exchanged must be encrypted) conf-variable: Enable no encryption
--application-version <ASCII string> Application Version to report. Note: Default string is generated at runtime. Default: Cisco Systems VPN Client 0.5.3:Linux conf-variable: Application version <ASCII string>
--ifname <ASCII string> visible name of the TUN/TAP interface conf-variable: Interface name <ASCII string>
--ifmode <tun/tap> mode of TUN/TAP interface: •      tun: virtual point to point interface (default) •      tap: virtual ethernet interface Default: tun conf-variable: Interface mode <tun/tap>
--ifmtu <0-65535> Set MTU for TUN/TAP interface (default 0 == automatic detect) conf-variable: Interface MTU <0-65535>
--debug <0/1/2/3/99> Show verbose debug messages • 0: Do not print debug information. • 1: Print minimal debug information. • 2: Show statemachine and packet/payload type information. • 3: Dump everything excluding authentication data. •      99: Dump everything INCLUDING AUTHENTICATION data (e.g. PASSWORDS). conf-variable: Debug <0/1/2/3/99>
--no-detach Don't detach from the console after login conf-variable: No Detach
--pid-file <filename> store the pid of background process in <filename> Default: /run/vpnc.pid conf-variable: Pidfile <filename>
--local-addr <ip/hostname> local IP to use for ISAKMP / ESP / ... (0.0.0.0 == automatically assign) Default: 0.0.0.0 conf-variable: Local Addr <ip/hostname>
--local-port <0-65535> local ISAKMP port number to use (0 == use random port) Default: 500 conf-variable: Local Port <0-65535>
--udp-port <0-65535> Local UDP port number to use (0 == use random port).  This is only relevant if cisco-udp nat-traversal is used.  This is the _local_ port, the remote udp port is discovered automatically.  It is especially not the cisco-tcp port. Default: 10000 conf-variable: Cisco UDP Encapsulation Port <0-65535>
--dpd-idle <0,10-86400> Send DPD packet after not receiving anything for <idle> seconds. Use 0 to disable DPD completely (both ways). Default: 300 conf-variable: DPD idle timeout (our side) <0,10-86400>
--non-inter Don't ask anything, exit on missing options conf-variable: Noninteractive
--auth-mode <psk/cert/hybrid> Authentication mode: •      psk:    pre-shared key (default) •      cert:   server + client certificate (not implemented yet) •      hybrid: server certificate + xauth (if built with openssl support) Default: psk conf-variable: IKE Authmode <psk/cert/hybrid>
--ca-file <filename> filename and path to the CA-PEM-File conf-variable: CA-File <filename>
--ca-dir <directory> path of the trusted CA-Directory Default: /etc/ssl/certs conf-variable: CA-Dir <directory>
--target-network <target network/netmask> Target network in dotted decimal or CIDR notation Default: 0.0.0.0/0.0.0.0 conf-variable: IPSEC target network <target network/netmask>
--password-helper <executable> path to password program or helper name conf-variable: Password helper <executable>
--print-config Prints your configuration; output can be used as vpnc.conf
/etc/vpnc.conf /etc/vpnc/default.conf The default configuration file. You can specify the same config directives as with command line options and additionally IPSec secret and Xauth password both supplying a cleartext password. Scrambled passwords from the Cisco configuration profiles can be used with IPSec obfuscated secret and Xauth obfuscated password.
See EXAMPLES for further details.
/etc/vpnc/*.conf vpnc will read configuration files in this directory when the config filename (with or without .conf) is specified on the command line.
This is an example vpnc.conf with pre-shared keys:
IPSec gateway vpn.example.com IPSec ID ExampleVpnPSK IKE Authmode psk IPSec secret PskS3cret! Xauth username user@example.com Xauth password USecr3t
And another one with hybrid authentication (requires that vpnc was built with openssl support):
IPSec gateway vpn.example.com IPSec ID ExampleVpnHybrid IKE Authmode hybrid CA-Dir /etc/vpnc or CA-File /etc/vpnc/vpn-example-com.pem IPSec secret HybS3cret? Xauth username user@example.com Xauth password 123456
The lines begin with a keyword (no leading spaces!).  The values start exactly one space after the keywords, and run to the end of line. This lets you put any kind of weird character (except CR, LF and NUL) in your strings, but it does mean you can't add comments after a string, or spaces before them.
In case the the CA-Dir option is used, your certificate needs to be named something like 722d15bd.X, where X is a manually assigned number to make sure that files with colliding hashes have different names. The number can be derived from the certificate file itself:
openssl x509 -subject_hash -noout -in /etc/vpnc/vpn-example-com.pem
See also the --print-config option to generate a config file, and the example file in the package documentation directory where more advanced usage is demonstrated.
Advanced features like manual setting of multiple target routes and disabling /etc/resolv.conf rewriting is documented in the README of the vpnc package.
This man-page has been written by Eduard Bloch <blade(at)debian.org> and Christian Lackas <delta(at)lackas.net>, based on vpnc README by Maurice Massar <vpnc(at)unix-ag.uni-kl.de>.  Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 any later version published by the Free Software Foundation.
pcf2vpnc(1), cisco-decrypt(1), ip(8), ifconfig(8), route(1), http://www.unix-ag.uni-kl.de/~massar/vpnc/
GIT-SUBTREE(1)                   [FIXME: manual]                  GIT-SUBTREE(1)
git-subtree - Merge subtrees together and split repository into subtrees
git subtree [<options>] -P <prefix> add <local-commit> git subtree [<options>] -P <prefix> add <repository> <remote-ref> git subtree [<options>] -P <prefix> merge <local-commit> git subtree [<options>] -P <prefix> split [<local-commit>]
git subtree [<options>] -P <prefix> pull <repository> <remote-ref> git subtree [<options>] -P <prefix> push <repository> <refspec>
Subtrees allow subprojects to be included within a subdirectory of the main project, optionally including the subproject’s entire history.
For example, you could include the source code for a library as a subdirectory of your application.
Subtrees are not to be confused with submodules, which are meant for the same task. Unlike submodules, subtrees do not need any special constructions (like .gitmodules files or gitlinks) be present in your repository, and do not force end-users of your repository to do anything special or to understand how subtrees work. A subtree is just a subdirectory that can be committed to, branched, and merged along with your project in any way you want.
They are also not to be confused with using the subtree merge strategy. The main difference is that, besides merging the other project as a subdirectory, you can also extract the entire history of a subdirectory from your project and make it into a standalone project. Unlike the subtree merge strategy you can alternate back and forth between these two operations. If the standalone library gets updated, you can automatically merge the changes into your project; if you update the library inside your project, you can "split" the changes back out again and merge them back into the library project.
For example, if a library you made for one application ends up being useful elsewhere, you can extract its entire history and publish that as its own git repository, without accidentally intermingling the history of your application project.
Tip In order to keep your commit messages clean, we recommend that people split their commits between the subtrees and the main project as much as possible. That is, if you make a change that affects both the library and the main application, commit it in two pieces. That way, when you split the library commits out later, their descriptions will still make sense. But if this isn’t important to you, it’s not necessary. git subtree will simply leave out the non-library-related parts of the commit when it splits it out into the subproject later.
add <local-commit>, add <repository> <remote-ref> Create the <prefix> subtree by importing its contents from the given <local-commit> or <repository> and <remote-ref>. A new commit is created automatically, joining the imported project’s history with your own. With --squash, import only a single commit from the subproject, rather than its entire history.
merge <local-commit> Merge recent changes up to <local-commit> into the <prefix> subtree. As with normal git merge, this doesn’t remove your own local changes; it just merges those changes into the latest <local-commit>. With --squash, create only one commit that contains all the changes, rather than merging in the entire history.
If you use --squash, the merge direction doesn’t always have to be forward; you can use this command to go back in time from v2.5 to v2.4, for example. If your merge introduces a conflict, you can resolve it in the usual ways.
split [<local-commit>] Extract a new, synthetic project history from the history of the <prefix> subtree of <local-commit>, or of HEAD if no <local-commit> is given. The new history includes only the commits (including merges) that affected <prefix>, and each of those commits now has the contents of <prefix> at the root of the project instead of in a subdirectory. Thus, the newly created history is suitable for export as a separate git repository.
After splitting successfully, a single commit ID is printed to stdout. This corresponds to the HEAD of the newly created tree, which you can manipulate however you want.
Repeated splits of exactly the same history are guaranteed to be identical (i.e. to produce the same commit IDs) as long as the settings passed to split (such as --annotate) are the same. Because of this, if you add new commits and then re-split, the new commits will be attached as commits on top of the history you generated last time, so git merge and friends will work as expected.
pull <repository> <remote-ref> Exactly like merge, but parallels git pull in that it fetches the given ref from the specified remote repository.
push <repository> [+][<local-commit>:]<remote-ref> Does a split using the <prefix> subtree of <local-commit> and then does a git push to push the result to the <repository> and <remote-ref>. This can be used to push your subtree to different branches of the remote repository. Just as with split, if no <local-commit> is given, then HEAD is used. The optional leading + is ignored.
-q, --quiet Suppress unnecessary output messages on stderr.
-d, --debug Produce even more unnecessary output messages on stderr.
-P <prefix>, --prefix=<prefix> Specify the path in the repository to the subtree you want to manipulate. This option is mandatory for all commands.
OPTIONS FOR ADD AND MERGE (ALSO: PULL, SPLIT --REJOIN, AND PUSH --REJOIN) These options for add and merge may also be given to pull (which wraps merge), split --rejoin (which wraps either add or merge as appropriate), and push --rejoin (which wraps split --rejoin).
--squash Instead of merging the entire history from the subtree project, produce only a single commit that contains all the differences you want to merge, and then merge that new commit into your project.
Using this option helps to reduce log clutter. People rarely want to see every change that happened between v1.0 and v1.1 of the library they’re using, since none of the interim versions were ever included in their application.
Using --squash also helps avoid problems when the same subproject is included multiple times in the same project, or is removed and then re-added. In such a case, it doesn’t make sense to combine the histories anyway, since it’s unclear which part of the history belongs to which subtree.
Furthermore, with --squash, you can switch back and forth between different versions of a subtree, rather than strictly forward.  git subtree merge --squash always adjusts the subtree to match the exactly specified commit, even if getting to that commit would require undoing some changes that were added earlier.
Whether or not you use --squash, changes made in your local repository remain intact and can be later split and send upstream to the subproject.
-m <message>, --message=<message> Specify <message> as the commit message for the merge commit.
OPTIONS FOR SPLIT (ALSO: PUSH) These options for split may also be given to push (which wraps split).
--annotate=<annotation> When generating synthetic history, add <annotation> as a prefix to each commit message. Since we’re creating new commits with the same commit message, but possibly different content, from the original commits, this can help to differentiate them and avoid confusion.
Whenever you split, you need to use the same <annotation>, or else you don’t have a guarantee that the new re-created history will be identical to the old one. That will prevent merging from working correctly. git subtree tries to make it work anyway, particularly if you use --rejoin, but it may not always be effective.
-b <branch>, --branch=<branch> After generating the synthetic history, create a new branch called <branch> that contains the new history. This is suitable for immediate pushing upstream. <branch> must not already exist.
--ignore-joins If you use --rejoin, git subtree attempts to optimize its history reconstruction to generate only the new commits since the last --rejoin.  --ignore-joins disables this behavior, forcing it to regenerate the entire history. In a large project, this can take a long time.
--onto=<onto> If your subtree was originally imported using something other than git subtree, its history may not match what git subtree is expecting. In that case, you can specify the commit ID <onto> that corresponds to the first revision of the subproject’s history that was imported into your project, and git subtree will attempt to build its history from there.
If you used git subtree add, you should never need this option.
--rejoin After splitting, merge the newly created synthetic history back into your main project. That way, future splits can search only the part of history that has been added since the most recent --rejoin.
If your split commits end up merged into the upstream subproject, and then you want to get the latest upstream version, this will allow git’s merge algorithm to more intelligently avoid conflicts (since it knows these synthetic commits are already part of the upstream repository).
Unfortunately, using this option results in git log showing an extra copy of every new commit that was created (the original, and the synthetic one).
If you do all your merges with --squash, make sure you also use --squash when you split --rejoin.
EXAMPLE 1. ADD COMMAND Let’s assume that you have a local repository that you would like to add an external vendor library to. In this case we will add the git-subtree repository as a subdirectory of your already existing git-extensions repository in ~/git-extensions/:
$ git subtree add --prefix=git-subtree --squash \ git://github.com/apenwarr/git-subtree.git master
master needs to be a valid remote ref and can be a different branch name
You can omit the --squash flag, but doing so will increase the number of commits that are included in your local repository.
We now have a ~/git-extensions/git-subtree directory containing code from the master branch of git://github.com/apenwarr/git-subtree.git in our git-extensions repository.
EXAMPLE 2. EXTRACT A SUBTREE USING COMMIT, MERGE AND PULL Let’s use the repository for the git source code as an example. First, get your own copy of the git.git repository:
$ git clone git://git.kernel.org/pub/scm/git/git.git test-git $ cd test-git
gitweb (commit 1130ef3) was merged into git as of commit 0a8f4f0, after which it was no longer maintained separately. But imagine it had been maintained separately, and we wanted to extract git’s changes to gitweb since that time, to share with the upstream. You could do this:
$ git subtree split --prefix=gitweb --annotate='(split) ' \ 0a8f4f0^.. --onto=1130ef3 --rejoin \ --branch gitweb-latest $ gitk gitweb-latest $ git push git@github.com:whatever/gitweb.git gitweb-latest:master
(We use 0a8f4f0^.. because that means "all the changes from 0a8f4f0 to the current version, including 0a8f4f0 itself.")
If gitweb had originally been merged using git subtree add (or a previous split had already been done with --rejoin specified) then you can do all your splits without having to remember any weird commit IDs:
$ git subtree split --prefix=gitweb --annotate='(split) ' --rejoin \ --branch gitweb-latest2
And you can merge changes back in from the upstream project just as easily:
$ git subtree pull --prefix=gitweb \ git@github.com:whatever/gitweb.git master
Or, using --squash, you can actually rewind to an earlier version of gitweb:
$ git subtree merge --prefix=gitweb --squash gitweb-latest~10
Then make some changes:
$ date >gitweb/myfile $ git add gitweb/myfile $ git commit -m 'created myfile'
And fast forward again:
$ git subtree merge --prefix=gitweb --squash gitweb-latest
And notice that your change is still intact:
$ ls -l gitweb/myfile
And you can split it out and look at your changes versus the standard gitweb:
git log gitweb-latest..$(git subtree split --prefix=gitweb)
EXAMPLE 3. EXTRACT A SUBTREE USING A BRANCH Suppose you have a source directory with many files and subdirectories, and you want to extract the lib directory to its own git project. Here’s a short way to do it:
First, make the new repository wherever you want:
$ <go to the new location> $ git init --bare
Back in your original directory:
$ git subtree split --prefix=lib --annotate="(split)" -b split
Then push the new branch onto the new empty repository:
$ git push <new-repo> split:master
Written by Avery Pennarun <apenwarr@gmail.com[1]>
1. apenwarr@gmail.com mailto:apenwarr@gmail.com
2TO3-3.3(1)                       User Commands                      2TO3-3.3(1)
2to3-3.3 - Python2 to Python3 converter
2to3 [options] file|dir ...
-d, --doctests_only Fix up doctests only
-f FIX, --fix=FIX Each FIX specifies a transformation; default: all
-j PROCESSES, --processes=PROCESSES Run 2to3 concurrently
-x NOFIX, --nofix=NOFIX Prevent a transformation from being run
-l, --list-fixes List available transformations
-p, --print-function Modify the grammar so that print() is a function
-v, --verbose More verbose logging
--no-diffs Don't show diffs of the refactoring
-w, --write Write back modified files
-n, --nobackups Don't write backups for modified files
SHRED(1)                          User Commands                         SHRED(1)
shred - overwrite a file to hide its contents, and optionally delete it
shred [OPTION]... FILE...
Overwrite the specified FILE(s) repeatedly, in order to make it harder for even very expensive hardware probing to recover the data.
If FILE is -, shred standard output.
-f, --force change permissions to allow writing if necessary
-n, --iterations=N overwrite N times instead of the default (3)
--random-source=FILE get random bytes from FILE
-s, --size=N shred this many bytes (suffixes like K, M, G accepted)
-u     deallocate and remove file after overwriting
--remove[=HOW] like -u but give control on HOW to delete;  See below
-v, --verbose show progress
-x, --exact do not round file sizes up to the next full block;
this is the default for non-regular files
-z, --zero add a final overwrite with zeros to hide shredding
Delete FILE(s) if --remove (-u) is specified.  The default is not to remove the files because it is common to operate on device files like /dev/hda, and those files usually should not be removed.  The optional HOW parameter indicates how to remove a directory entry: 'unlink' => use a standard unlink call.  'wipe' => also first obfuscate bytes in the name.  'wipesync' => also sync each obfuscated byte to the device.  The default mode is 'wipesync', but note it can be expensive.
CAUTION: shred assumes the file system and hardware overwrite data in place.  Although this is common, many platforms operate otherwise.  Also, backups and mirrors may contain unremovable copies that will let a shredded file be recovered later.  See the GNU coreutils manual for details.
Written by Colin Plumb.
Full documentation <https://www.gnu.org/software/coreutils/shred> or available locally via: info '(coreutils) shred invocation'
E2UNDO(8)                    System Manager's Manual                   E2UNDO(8)
e2undo - Replay an undo log for an ext2/ext3/ext4 file system
e2undo [ -f ] [ -h ] [ -n ] [ -o offset ] [ -v ] [ -z undo_file ] undo_log device
e2undo will replay the undo log undo_log for an ext2/ext3/ext4 file system found on device.  This can be used to undo a failed operation by an e2fsprogs program.
-f     Normally, e2undo will check the file system superblock to make sure the undo log matches with the file system on the device.  If they do not match, e2undo will refuse to apply the undo log as a safety mechanism.  The -f option disables this safety mechanism.
-h     Display a usage message.
-n     Dry-run; do not actually write blocks back to the file system.
-o offset Specify the file system's offset (in bytes) from the beginning of the device or file.
-v     Report which block we're currently replaying.