neulab/tldr huggingface dataset:
-G, --supp-group=group Specify a supplementary group. This option is available to the root user only. The first specified supplementary group is also used as a primary group if the option --group is not specified.
-, -l, --login Start the shell as a login shell with an environment similar to a real login:
•   clears all the environment variables except for TERM and variables specified by --whitelist-environment
•   initializes the environment variables HOME, SHELL, USER, LOGNAME, and PATH
•   changes to the target user’s home directory
•   sets argv[0] of the shell to '-' in order to make the shell a login shell
-P, --pty Create a pseudo-terminal for the session. The independent terminal provides better security as the user does not share a terminal with the original session. This can be used to avoid TIOCSTI ioctl terminal injection and other security attacks against terminal file descriptors. The entire session can also be moved to the background (e.g., runuser --pty -u username — command &). If the pseudo-terminal is enabled, then runuser works as a proxy between the sessions (copy stdin and stdout).
This feature is mostly designed for interactive sessions. If the standard input is not a terminal, but for example a pipe (e.g., echo "date" | runuser --pty -u user), then the ECHO flag for the pseudo-terminal is disabled to avoid messy output.
-m, -p, --preserve-environment Preserve the entire environment, i.e., do not set HOME, SHELL, USER or LOGNAME. The option is ignored if the option --login is specified.
-s, --shell=shell Run the specified shell instead of the default. The shell to run is selected according to the following rules, in order:
•   the shell specified with --shell
•   the shell specified in the environment variable SHELL if the --preserve-environment option is used
•   the shell listed in the passwd entry of the target user
•   /bin/sh
If the target user has a restricted shell (i.e., not listed in /etc/shells), then the --shell option and the SHELL environment variables are ignored unless the calling user is root.
--session-command=command Same as -c, but do not create a new session. (Discouraged.)
-w, --whitelist-environment=list Don’t reset the environment variables specified in the comma-separated list when clearing the environment for --login. The whitelist is ignored for the environment variables HOME, SHELL, USER, LOGNAME, and PATH.
runuser reads the /etc/default/runuser and /etc/login.defs configuration files. The following configuration items are relevant for runuser:
ENV_PATH (string) Defines the PATH environment variable for a regular user. The default value is /usr/local/bin:/bin:/usr/bin.
ENV_ROOTPATH (string), ENV_SUPATH (string) Defines the PATH environment variable for root. ENV_SUPATH takes precedence. The default value is /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin.
ALWAYS_SET_PATH (boolean) If set to yes and --login and --preserve-environment were not specified runuser initializes PATH.
The environment variable PATH may be different on systems where /bin and /sbin are merged into /usr; this variable is also affected by the --login command-line option and the PAM system setting (e.g., pam_env(8)).
runuser normally returns the exit status of the command it executed. If the command was killed by a signal, runuser returns the number of the signal plus 128.
Exit status generated by runuser itself:
1 Generic error before executing the requested command
126 The requested command could not be executed
127 The requested command was not found
/etc/pam.d/runuser default PAM configuration file
/etc/pam.d/runuser-l PAM configuration file if --login is specified
/etc/default/runuser runuser specific logindef config file
/etc/login.defs global logindef config file
This runuser command was derived from coreutils' su, which was based on an implementation by David MacKenzie, and the Fedora runuser command by Dan Walsh.
setpriv(1), su(1), login.defs(5), shells(5), pam(8)
The runuser 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/>.
VIRTUALENVWRAPPER(1)            virtualenvwrapper           VIRTUALENVWRAPPER(1)
virtualenvwrapper - a set of wrappers to assist with manage your python virtualenvs
All of the commands below are to be used on the Terminal command line.
mkvirtualenv Create a new environment, in the WORKON_HOME.
mkvirtualenv [-a project_path] [-i package] [-r requirements_file] [virtualenv options] ENVNAME
All command line options except -a, -i, -r, and -h are passed directly to virtualenv.  The new environment is automatically activated after being initialized.
$ workon $ mkvirtualenv mynewenv New python executable in mynewenv/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. (mynewenv)$ workon mynewenv (mynewenv)$
The -a option can be used to associate an existing project directory with the new environment.
The -i option can be used to install one or more packages (by repeating the option) after the environment is created.
The -r option can be used to specify a text file listing packages to be installed. The argument value is passed to pip -r to be installed.
• scripts-premkvirtualenv
• scripts-postmkvirtualenv
• requirements file format
mktmpenv Create a new virtualenv in the WORKON_HOME directory.
mktmpenv [(-c|--cd)|(-n|--no-cd)] [VIRTUALENV_OPTIONS]
A unique virtualenv name is generated.
If -c or --cd is specified the working directory is changed to the virtualenv directory during the post-activate phase, regardless of the value of VIRTUALENVWRAPPER_WORKON_CD.
If -n or --no-cd is specified the working directory is not changed to the virtualenv directory during the post-activate phase, regardless of the value of VIRTUALENVWRAPPER_WORKON_CD.
$ mktmpenv Using real prefix '/Library/Frameworks/Python.framework/Versions/2.7' New python executable in 1e513ac6-616e-4d56-9aa5-9d0a3b305e20/bin/python Overwriting 1e513ac6-616e-4d56-9aa5-9d0a3b305e20/lib/python2.7/distutils/__init__.py with new content Installing setuptools............................................... .................................................................... .................................................................done. This is a temporary environment. It will be deleted when deactivated. (1e513ac6-616e-4d56-9aa5-9d0a3b305e20) $
lsvirtualenv List all of the environments.
lsvirtualenv [-b] [-l] [-h]
-b     Brief mode, disables verbose output.
-l     Long mode, enables verbose output.  Default.
-h     Print the help for lsvirtualenv.
• scripts-get_env_details
showvirtualenv Show the details for a single virtualenv.
showvirtualenv [env]
rmvirtualenv Remove an environment, in the WORKON_HOME.
rmvirtualenv ENVNAME
You must use deactivate before removing the current environment.
(mynewenv)$ deactivate $ rmvirtualenv mynewenv $ workon $
• scripts-prermvirtualenv
• scripts-postrmvirtualenv
cpvirtualenv Duplicate an existing virtualenv environment. The source can be an environment managed by virtualenvwrapper or an external environment created elsewhere.
WARNING: Copying virtual environments is not well supported. Each virtualenv has path information hard-coded into it, and there may be cases where the copy code does not know it needs to update a particular file. Use with caution.
cpvirtualenv ENVNAME [TARGETENVNAME]
NOTE: Target environment name is required for WORKON_HOME duplications. However, target environment name can be ommited for importing external environments. If omitted, the new environment is given the same name as the original.
$ workon $ mkvirtualenv source New python executable in source/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. (source)$ cpvirtualenv source dest Making script /Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/easy_install relative Making script /Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/easy_install-2.6 relative Making script /Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/pip relative Script /Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/postactivate cannot be made relative (it's not a normal script that starts with #!/Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/python) Script /Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/postdeactivate cannot be made relative (it's not a normal script that starts with #!/Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/python) Script /Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/preactivate cannot be made relative (it's not a normal script that starts with #!/Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/python) Script /Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/predeactivate cannot be made relative (it's not a normal script that starts with #!/Users/dhellmann/Devel/virtualenvwrapper/tmp/dest/bin/python) (dest)$ workon dest source (dest)$
• scripts-precpvirtualenv
• scripts-postcpvirtualenv
allvirtualenv Run a command in all virtualenvs under WORKON_HOME.
allvirtualenv command with arguments
Each virtualenv is activated, bypassing activation hooks, the current working directory is changed to the current virtualenv, and then the command is run. Commands cannot modify the current shell state, but can modify the virtualenv.
$ allvirtualenv pip install -U pip
workon List or change working virtual environments
workon [(-c|--cd)|(-n|--no-cd)] [environment_name|"."]
If no environment_name is given the list of available environments is printed to stdout.
If -c or --cd is specified the working directory is changed to the project directory during the post-activate phase, regardless of the value of VIRTUALENVWRAPPER_WORKON_CD.
If -n or --no-cd is specified the working directory is not changed to the project directory during the post-activate phase, regardless of the value of VIRTUALENVWRAPPER_WORKON_CD.
If "." is passed as the environment name, the name is derived from the base name of the current working directory (contributed by Matias Saguir).
$ workon $ mkvirtualenv env1 New python executable in env1/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. (env1)$ mkvirtualenv env2 New python executable in env2/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. (env2)$ workon env1 env2 (env2)$ workon env1 (env1)$ echo $VIRTUAL_ENV /Users/dhellmann/Devel/virtualenvwrapper/tmp/env1 (env1)$ workon env2 (env2)$ echo $VIRTUAL_ENV /Users/dhellmann/Devel/virtualenvwrapper/tmp/env2 (env2)$
• scripts-predeactivate
• scripts-postdeactivate
• scripts-preactivate
• scripts-postactivate
• variable-VIRTUALENVWRAPPER_WORKON_CD
deactivate Switch from a virtual environment to the system-installed version of Python.
NOTE: This command is actually part of virtualenv, but is wrapped to provide before and after hooks, just as workon does for activate.
$ workon $ echo $VIRTUAL_ENV
$ mkvirtualenv env1 New python executable in env1/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. (env1)$ echo $VIRTUAL_ENV /Users/dhellmann/Devel/virtualenvwrapper/tmp/env1 (env1)$ deactivate $ echo $VIRTUAL_ENV
There are two functions to provide shortcuts to navigate into the currently-active virtualenv.
cdvirtualenv Change the current working directory to $VIRTUAL_ENV.
cdvirtualenv [subdir]
Calling cdvirtualenv changes the current working directory to the top of the virtualenv ($VIRTUAL_ENV).  An optional argument is appended to the path, allowing navigation directly into a subdirectory.
$ mkvirtualenv env1 New python executable in env1/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. (env1)$ echo $VIRTUAL_ENV /Users/dhellmann/Devel/virtualenvwrapper/tmp/env1 (env1)$ cdvirtualenv (env1)$ pwd /Users/dhellmann/Devel/virtualenvwrapper/tmp/env1 (env1)$ cdvirtualenv bin (env1)$ pwd /Users/dhellmann/Devel/virtualenvwrapper/tmp/env1/bin
cdsitepackages Change the current working directory to the site-packages for $VIRTUAL_ENV.
cdsitepackages [subdir]
Because the exact path to the site-packages directory in the virtualenv depends on the version of Python, cdsitepackages is provided as a shortcut for cdvirtualenv lib/python${pyvers}/site-packages. An optional argument is also allowed, to specify a directory hierarchy within the site-packages directory to change into.
$ mkvirtualenv env1 New python executable in env1/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. (env1)$ echo $VIRTUAL_ENV /Users/dhellmann/Devel/virtualenvwrapper/tmp/env1 (env1)$ cdsitepackages PyMOTW/bisect/ (env1)$ pwd /Users/dhellmann/Devel/virtualenvwrapper/tmp/env1/lib/python2.6/site-packages/PyMOTW/bisect
lssitepackages Calling lssitepackages shows the content of the site-packages directory of the currently-active virtualenv.
lssitepackages
$ mkvirtualenv env1 New python executable in env1/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. (env1)$ $ workon env1 (env1)$ lssitepackages setuptools-0.6.10-py2.6.egg     pip-0.6.3-py2.6.egg easy-install.pth                setuptools.pth
add2virtualenv Adds the specified directories to the Python path for the currently-active virtualenv.
add2virtualenv directory1 directory2 ...
Sometimes it is desirable to share installed packages that are not in the system site-packages directory and which should not be installed in each virtualenv.  One possible solution is to symlink the source into the environment site-packages directory, but it is also easy to add extra directories to the PYTHONPATH by including them in a .pth file inside site-packages using add2virtualenv.
1. Check out the source for a big project, such as Django.
2. Run: add2virtualenv path_to_source.
3. Run: add2virtualenv.
4. A usage message and list of current "extra" paths is printed.
5. Use option -d to remove the added path.
The directory names are added to a path file named _virtualenv_path_extensions.pth inside the site-packages directory for the environment.
Based on a contribution from James Bennett and Jannis Leidel.
toggleglobalsitepackages Controls whether the active virtualenv will access the packages in the global Python site-packages directory.
toggleglobalsitepackages [-q]
Outputs the new state of the virtualenv. Use the -q switch to turn off all output.
$ mkvirtualenv env1 New python executable in env1/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. (env1)$ toggleglobalsitepackages Disabled global site-packages (env1)$ toggleglobalsitepackages Enabled global site-packages (env1)$ toggleglobalsitepackages -q (env1)$
SEE ALSO: project-management
mkproject Create a new virtualenv in the WORKON_HOME and project directory in PROJECT_HOME.
mkproject [-f|--force] [-t template] [virtualenv_options] ENVNAME
-f, --force Create the virtualenv even if the project directory already exists
The template option may be repeated to have several templates used to create a new project.  The templates are applied in the order named on the command line.  All other options are passed to mkvirtualenv to create a virtual environment with the same name as the project.
$ mkproject myproj New python executable in myproj/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. Creating /Users/dhellmann/Devel/myproj (myproj)$ pwd /Users/dhellmann/Devel/myproj (myproj)$ echo $VIRTUAL_ENV /Users/dhellmann/Envs/myproj (myproj)$
• scripts-premkproject
• scripts-postmkproject
setvirtualenvproject Bind an existing virtualenv to an existing project.
setvirtualenvproject [virtualenv_path project_path]
The arguments to setvirtualenvproject are the full paths to the virtualenv and project directory.  An association is made so that when workon activates the virtualenv the project is also activated.
$ mkproject myproj New python executable in myproj/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. Creating /Users/dhellmann/Devel/myproj (myproj)$ mkvirtualenv myproj_new_libs New python executable in myproj/bin/python Installing setuptools............................................. .................................................................. .................................................................. done. Creating /Users/dhellmann/Devel/myproj (myproj_new_libs)$ setvirtualenvproject $VIRTUAL_ENV $(pwd)
When no arguments are given, the current virtualenv and current directory are assumed.
Any number of virtualenvs can refer to the same project directory, making it easy to switch between versions of Python or other dependencies for testing.
cdproject Change the current working directory to the one specified as the project directory for the active virtualenv.
cdproject
wipeenv Remove all of the installed third-party packages in the current virtualenv.
wipeenv
virtualenvwrapper Print a list of commands and their descriptions as basic help output.
2009-2019, Doug Hellmann
GIT-CLEAN(1)                       Git Manual                       GIT-CLEAN(1)
git-clean - Remove untracked files from the working tree
git clean [-d] [-f] [-i] [-n] [-q] [-e <pattern>] [-x | -X] [--] <path>...
Normally, only files unknown to Git are removed, but if the -x option is specified, ignored files are also removed. This can, for example, be useful to remove all build products.
If any optional <path>... arguments are given, only those paths are affected.
-d Normally, when no <path> is specified, git clean will not recurse into untracked directories to avoid removing too much. Specify -d to have it recurse into such directories as well. If any paths are specified, -d is irrelevant; all untracked files matching the specified paths (with exceptions for nested git directories mentioned under --force) will be removed.
-f, --force If the Git configuration variable clean.requireForce is not set to false, git clean will refuse to delete files or directories unless given -f or -i. Git will refuse to modify untracked nested git repositories (directories with a .git subdirectory) unless a second -f is given.
-i, --interactive Show what would be done and clean files interactively. See “Interactive mode” for details.
-n, --dry-run Don’t actually remove anything, just show what would be done.
-q, --quiet Be quiet, only report errors, but not the files that are successfully removed.
-e <pattern>, --exclude=<pattern> Use the given exclude pattern in addition to the standard ignore rules (see gitignore(5)).
-x Don’t use the standard ignore rules (see gitignore(5)), but still use the ignore rules given with -e options from the command line. This allows removing all untracked files, including build products. This can be used (possibly in conjunction with git restore or git reset) to create a pristine working directory to test a clean build.
-X Remove only files ignored by Git. This may be useful to rebuild everything from scratch, but keep manually created files.
When the command enters the interactive mode, it shows the files and directories to be cleaned, and goes into its interactive command loop.
*** Commands *** 1: clean                2: filter by pattern    3: select by numbers 4: ask each             5: quit                 6: help What now> 1
You also could say c or clean above as long as the choice is unique.
The main command loop has 6 subcommands.
clean Start cleaning files and directories, and then quit.
filter by pattern This shows the files and directories to be deleted and issues an "Input ignore patterns>>" prompt. You can input space-separated patterns to exclude files and directories from deletion. E.g. "*.c *.h" will excludes files end with ".c" and ".h" from deletion. When you are satisfied with the filtered result, press ENTER (empty) back to the main menu.
select by numbers This shows the files and directories to be deleted and issues an "Select items to delete>>" prompt. When the prompt ends with double >> like this, you can make more than one selection, concatenated with whitespace or comma. Also you can say ranges. E.g. "2-5 7,9" to choose 2,3,4,5,7,9 from the list. If the second number in a range is omitted, all remaining items are selected. E.g. "7-" to choose 7,8,9 from the list. You can say * to choose everything. Also when you are satisfied with the filtered result, press ENTER (empty) back to the main menu.
ask each This will start to clean, and you must confirm one by one in order to delete items. Please note that this action is not as efficient as the above two actions.
quit This lets you quit without do cleaning.
help Show brief usage of interactive git-clean.
ANSIBLE-PULL(1)          System administration commands          ANSIBLE-PULL(1)
ansible-pull - pulls playbooks from a VCS repo and executes them for the local host
usage: ansible-pull [-h] [--version] [-v] [--private-key PRIVATE_KEY_FILE] [-u REMOTE_USER] [-c CONNECTION] [-T TIMEOUT] [--ssh-common-args SSH_COMMON_ARGS] [--sftp-extra-args SFTP_EXTRA_ARGS] [--scp-extra-args SCP_EXTRA_ARGS] [--ssh-extra-args SSH_EXTRA_ARGS] [-k | --connection-password-file CONNECTION_PASSWORD_FILE] [--vault-id VAULT_IDS] [--ask-vault-password | --vault-password-file VAULT_PASSWORD_FILES] [-e EXTRA_VARS] [-t TAGS] [--skip-tags SKIP_TAGS] [-i INVENTORY] [--list-hosts] [-l SUBSET] [-M MODULE_PATH] [-K | --become-password-file BECOME_PASSWORD_FILE] [--purge] [-o] [-s SLEEP] [-f] [-d DEST] [-U URL] [--full] [-C CHECKOUT] [--accept-host-key] [-m MODULE_NAME] [--verify-commit] [--clean] [--track-subs] [--check] [--diff] [playbook.yml [playbook.yml ...]]
Used to pull a remote copy of ansible on each managed node, each set to run via cron and update playbook source via a source repository.  This inverts the default push architecture of ansible into a pull architecture, which has near-limitless scaling potential.
The setup playbook can be tuned to change the cron frequency, logging locations, and parameters to ansible-pull.  This is useful both for extreme scale-out as well as periodic remediation.  Usage of the 'fetch' module to retrieve logs from ansible-pull runs would be an excellent way to gather and analyze remote logs from ansible-pull.
--accept-host-key adds the hostkey for the repo url if not already added
--check don't make any changes; instead, try to predict some of the changes that may occur
--clean modified files in the working repository will be discarded
--diff when changing (small) files and templates, show the differences in those files; works great with --check
--full Do a full clone, instead of a shallow one.
--purge purge checkout after playbook run
--track-subs submodules will track the latest changes. This is equivalent to specifying the --remote flag to git submodule update
--verify-commit verify GPG signature of checked out commit, if it fails abort running the playbook. This needs the corresponding VCS module to support such an operation
-C 'CHECKOUT', --checkout 'CHECKOUT' branch/tag/commit to checkout. Defaults to behavior of repository module.
-U 'URL', --url 'URL' URL of the playbook repository
-d 'DEST', --directory 'DEST' absolute path of repository checkout directory (relative paths are not supported)
-f, --force run the playbook even if the repository could not be updated
-m 'MODULE_NAME', --module-name 'MODULE_NAME' Repository module name, which ansible will use to check out the repo. Choices are ('git', 'subversion', 'hg', 'bzr'). Default is git.
-o, --only-if-changed only run the playbook if the repository has been updated
-s 'SLEEP', --sleep 'SLEEP' sleep for random interval (between 0 and n number of seconds) before starting. This is a useful way to disperse git requests
ansible (1), ansible-config (1), ansible-console (1), ansible-doc (1), ansible-galaxy (1), ansible-inventory (1), ansible-playbook (1), ansible-vault (1)
EYED3(1)                                                                EYED3(1)
eyeD3 - displays and manipulates id3-tags on mp3 files
eyeD3 [options] file [file...] eyeD3 [options] dir [dir...]
eyeD3 Manipulates ID3 tags in mp3 files and is able to read/write and convert between ID3 v1.0, v1.1, v2.3 and v2.4 tags.  High-level access is provided to most frames, including APIC (i.e., images) frames.
-h, --help Shows a brief help string and exit.
--no-color Disable color output.
-v, --verbose Show all available tag information.
--debug Trace program execution; for debugging.
-1, --v1 Only read/write ID3 v1 tags. By default, v1 tags are only read if there is not a v2 tag.
-2, --v2 Only read/write ID3 v2.x tags.
--to-v1.1 Convert the file's tag to ID3 v1.1. (Or 1.0 if there is no track number)
--to-v2.3 Convert the file's tag to ID3 v2.3.
--to-v2.4 Convert the file's tag to ID3 v2.4
Options for manipulating tag data have the side-effect of removing a frame when the data specified is the empty string.  For example, --artist="" (or -a "") would cause the artist frame to be removed.  This is especially useful for removing comment frames.
-a STRING, --artist=STRING Set artist the to STRING.
-A STRING, --album=STRING Set album to STRING.
-t STRING, --title=STRING Set track title to STRING.
-n NUM, --track=NUM Set track number to NUM.
-N NUM, --track-total=NUM Set total number of tracks to NUM.
-G STRING, --genre=STRING Sets genre to STRING. (See --list-genres)
-Y YEAR, --year=YEAR Set the four digit year.
-p STRING, --publisher=STRING Set the publisher/label text.
--comment=[LANGUAGE]:DESCRIPTION:COMMENT Add (or remove when COMMENT is "") a comment.  Note that the argument value MUST always contain exactly two ':' characters to delimit the fields even when the default language is being used. The DESCRIPTION string is the comment title.  The optional LANGUAGE string MUST be a three-character ISO 639 language code. The default is "eng" for English.
A tag may not have more than one comment frame with the same DESCRIPTION and LANGUAGE values.
--remove-comments Remove all comment frames from the tag.
--lyrics=[LANGUAGE]:DESCRIPTION:LYRICS Add (or remove when LYRICS is "") a comment.  Note that the argument value MUST always contain exactly two ':' characters to delimit the fields even when the default language is being used. The DESCRIPTION string is the lyrics title.  The optional LANGUAGE string MUST be a three-character ISO 639 language code.  The default is "eng" for English.
A tag may not have more than one lyrics frame with the same DESCRIPTION and LANGUAGE values.
--remove-lyrics Remove all lyrics frames from the tag.
--add-image=IMG_PATH:TYPE[:DESCRIPTION] Add an image to the tag (APIC frame).  The IMG_PATH is the image file to add to the tag. If the path value is empty the image frame with a value of TYPE is removed from the tag.  The TYPE is one of the types listed when 'eyeD3 --list-image-types' is run.  The DESCRIPTION is optional and will default to "".
A tag may not have more than one image frame with the same TYPE values.
--remove-images Remove all image (APIC) frames from the tag.
--add-object=OBJ_PATH[:DESCRIPTION[:MIME-TYPE[:FILENAME]]] Add an encapsulated object to the tag (GEOB frame).  The description and filename are optional, but when used, the ':' delimiters must be present.  If the OBJ_PATH value is empty the GEOB frame with DESCRIPTION is removed.
A tag may not have more than one object (GEOB) frame with the same DESCRIPTION values.
-i DIR, --write-images=DIR Causes all attached images (APIC frames) to be written to the specified directory.  They are named by their "image type".  For example, if the image is a png and the type is OTHER, a file named OTHER.png is written to the desired directory.  If the file name already exist, a unique numeric value is appended to the type string.
-o DIR, --write-objects=DIR Causes all attached objects (GEOB frames) to be written to the specified directory.  The files are written with the name "<filename>.<mime-subtype>" in the specified directory.
--set-text-frame=FID:TEXT Set the value of a specific (i.e., FID) text frame.  To remove the frame, specify an empty value.  e.g., --set-text-frame="TDRC:"
--set-user-text-frame=DESC:TEXT Set the value of a TXXX text frame with a unique description.  To remove the frame, specify an empty value.  e.g., --set-user-text- frame="Description:"
--set-url-frame=FID:URL Set the value of a specific (i.e., FID) URL frame.  To remove the frame, specify an empty URL.  e.g., --set-url-frame="WCOM:"
--set-user-url-frame=DESC:URL Set the value of a WXXX frame with unique description string.  To remove the frame, specify an empty URL.  e.g., --set-user-url- frame="Description:"
--play-count=[+]N Set the play count (PCNT). If the argument value begins with '+' the value is incremented by N, otherwise it is set to exactly N.
--bpm=N Set the beats per minute value.  The value MUST be greater than 0.
--unique-file-id=OWNER_ID:ID Add a UFID frame.  If the ID arg is empty the UFID frame with OWNER_ID is removed.  An OWNER_ID MUST be specified.
--set-encoding=latin1|utf8|utf16-LE|utf16-BE Set the encoding that is used for _all_ text frames in the tag. The encoding is applied only when the tag is updated, therefore a frame must be set or --force-update is present.  Note that, unfortunately, utf8 is not supported by ID3 v2.3 tags.
--remove-v1 Remove ID3 v1.x tag.
--remove-v2 Remove ID3 v2.x tag.
--remove-all Remove all tags.
MISC. OPTIONS --rename=PATTERN Rename the file based on PATTERN which may contain the following substitution variables: %A (artist), %a (album), %t (title), %n (track number), and %N (the total track count).  The PATTERN string MUST not contain the file name extenstion.
--fs-encoding=ENCODING Use the specified character encoding for filenames when renaming files.  The default value is iso-8859-1.
-l, --list-genres Display the table of "valid" ID3 genres and exit.
--list-image-types List all possible image types for APIC frames.
--strict Fail for tags that violate the ID3 specification.
--jep-118 Output the tag per the format described in JEP-0118.  See http://www.xmpp.org/extensions/xep-0118.html
--nfo  Output NFO information for each album directory.
--lametag Prints the LAME Tag.
--force-update Update the tag regardless of whether any frames were set on the command line.
--no-zero-padding Don't pad track or disc numbers with 0's.
--no-tagging-time-frame When saving tags do not add a TDTG (tagging time) frame.
-F DELIM Specify a new delimiter for option values that contain multiple fields (default delimiter is ':')
http://eyed3.nicfit.net/
eyeD3 was written by Travis Shirk <travis@pobox.com>. This manpage was written by Alexander Wirt <formorer@debian.org> for the Debian Distribution and Travis Shirk.
DO-RELEASE-UPGRADE(8)                                      DO-RELEASE-UPGRADE(8)
do-release-upgrade - upgrade operating system to latest release
do-release-upgrade [options]
Upgrade the operating system to the latest release from the command-line. This is the preferred command if the machine has no graphic environment or if the machine is to be upgraded over a remote connection.
-d, --devel-release If using the latest supported release, upgrade to the development release
-p, --proposed Try upgrading to the latest release using the upgrader from Ubuntu-proposed
-m MODE, --mode=MODE Run in a special upgrade mode. Currently "desktop" for regular upgrades of a desktop system and "server" for server systems are supported.
-f FRONTEND, --frontend=FRONTEND Run the specified frontend
update-manager(8), apt-get(8)
drill(1)                     General Commands Manual                    drill(1)
drill - get (debug) information out of DNS(SEC)
drill [ OPTIONS ] name [ @server ] [ type ] [ class ]
drill is a tool to designed to get all sorts of information out of the DNS. It is specifically designed to be used with DNSSEC.
The name drill is a pun on dig. With drill you should be able get even more information than with dig.
If no arguments are given class defaults to 'IN' and type to 'A'. The server(s) specified in /etc/resolv.conf are used to query against.
name Ask for this name.
@server Send to query to this server. If not specified use the nameservers from /etc/resolv.conf.
type Ask for this RR type. If type is not given on the command line it defaults to 'A'. Except when doing a reverse lookup when it defaults to 'PTR'.
class Use this class when querying.
drill mx miek.nl Show the MX records of the domain miek.nl
drill -S jelte.nlnetlabs.nl Chase any signatures in the jelte.nlnetlab.nl domain. This option is only available when ldns has been compiled with openssl- support.
drill -TD www.example.com Do a DNSSEC (-D) trace (-T) from the rootservers down to www.example.com.  This option only works when ldns has been compiled with openssl support.
drill -s dnskey jelte.nlnetlabs.nl Show the DNSKEY record(s) for jelte.nlnetlabs.nl. For each found DNSKEY record also print the DS record.
-D     Enable DNSSEC in the query. When querying for DNSSEC types (DNSKEY, RRSIG, DS and NSEC) this is not automatically enabled.
-T     Trace name from the root down. When using this option the @server arguments is not used.
-S     Chase the signature(s) of 'name' to a known key or as high up in the tree as possible.
-I  IPv4 or IPv6 address Source address to query from.  The source address has to be present on an interface of the host running drill.
-V level Be more verbose. Set level to 5 to see the actual query that is sent.
-Q     Quiet mode, this overrules -V.
-f file Read the query from a file. The query must be dumped with -w.
-i file read the answer from the file instead from the network. This aids in debugging and can be used to check if a query on disk is valid. If the file contains binary data it is assumed to be a query in network order.
-w file Write an answer packet to file.
-q file Write the query packet to file.
-v     Show drill's version.
-h     Show a short help message.
QUERY OPTIONS -4     Stay on ip4. Only send queries to ip4 enabled nameservers.
-6     Stay on ip6. Only send queries to ip6 enabled nameservers.
-a     Use the resolver structure's fallback mechanism if the answer is truncated (TC=1). If a truncated packet is received and this option is set, drill will first send a new query with EDNS0 buffer size 4096.
If the EDNS0 buffer size was already set to 512+ bytes, or the above retry also results in a truncated answer, the resolver structure will fall back to TCP.
-b size Use size as the buffer size in the EDNS0 pseudo RR.
-c file Use file instead of /etc/resolv.conf for nameserver configuration.
-d domain When tracing (-T), start from this domain instead of the root.
-t     Use TCP/IP when querying a server
-k keyfile Use this file to read a (trusted) key from. When this options is given drill tries to validate the current answer with this key. No chasing is done. When drill is doing a secure trace, this key will be used as trust anchor. Can contain a DNSKEY or a DS record.
Alternatively, when DNSSEC enabled tracing (-TD) or signature chasing (-S), if -k is not specified, and a default trust anchor (/etc/trusted-key.key) exists and contains a valid DNSKEY or DS record, it will be used as the trust anchor.
-o mnemonic Use this option to set or unset specific header bits. A bit is set by using the bit mnemonic in CAPITAL letters. A bit is unset when the mnemonic is given in lowercase. The following mnemonics are understood by drill:
QR, qr: set, unset QueRy (default: on) AA, aa: set, unset Authoritative Answer (default: off) TC, tc: set, unset TrunCated (default: off) RD, rd: set, unset Recursion Desired (default: on) CD, cd: set, unset Checking Disabled  (default: off) RA, ra: set, unset Recursion Available  (default: off) AD, ad: set, unset Authenticated Data (default: off)
Thus: -o CD, will enable Checking Disabled, which instructs the cache to not validate the answers it gives out.
-p port Use this port instead of the default of 53.
-r file When tracing (-T), use file as a root servers hint file.
-s     When encountering a DNSKEY print the equivalent DS also.
-u     Use UDP when querying a server. This is the default.
-w file write the answer to a file. The file will contain a hexadecimal dump of the query. This can be used in conjunction with -f.
-x     Do a reverse lookup. The type argument is not used, it is preset to PTR.
-y <name:key[:algo]> specify named base64 tsig key, and optional an algorithm (defaults to hmac-md5.sig-alg.reg.int)
-z     don't randomize the nameserver list before sending queries.
The exit status is 0 if the looked up answer is secure and trusted, or insecure.  The exit status is not 0 if the looked up answer is untrusted or bogus, or an error occurred while performing the lookup.
/etc/trusted-key.key The file from which trusted keys are loaded when no -k option is given.
unbound-anchor(8)
dig(1), RFC403{3,4,5}.
Jelte Jansen and Miek Gieben. Both of NLnet Labs.
Report bugs to <ldns-team@nlnetlabs.nl>.
Copyright (c) 2004-2008 NLnet Labs.  Licensed under the revised BSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
jp2a(1)                           USER COMMANDS                          jp2a(1)
jp2a - convert JPEG and PNG images to ASCII
jp2a [ options ] [ filename(s) | URL(s) ]
jp2a will convert JPEG and PNG images to ASCII characters.  You can specify a mixture of files and URLs.
-      Read JPEG or PNG image from standard input
--background=light --background=dark If you don't want to mess with --invert all the time, just use these instead.  If you are using white characters on a black display, then use --background=dark, and vice versa.
-b --border Frame output image in a border
--chars=... Use the given characters when producing the output ASCII image. Default is "   ...',;:clodxkO0KXNWM".
--colors Use truecolor (or ANSI color if truecolor is not supported) for text output and CSS color for HTML output.
--color-depth=... Use a specific color-depth for terminal output. Valid values are: 4 (for ANSI), 8 (for 256 color palette) and 24 (for truecolor or 24-bit color).
-d --debug Print debugging information when using libcurl to download images from the net.
-f --term-fit Use the largest dimension that makes the image fit in your terminal display.
--term-height Use terminal display height and calculate width based on image aspect ratio.
--term-width Use terminal display width and calculate height based on image aspect ratio.
-z --term-zoom Use terminal display width and height.
--fill When used with --html and --color, then color each output character's background color.  For instance, if you want to use fill-output on a light background, do
jp2a --color --html --html-fill --background=light somefile.jpg --output=dark.html
To do the same on a light background:
jp2a --color --html --html-fill --background=dark somefile.jpg --output=light.html
The default is to have fill disabled.
-x --flipx Flip output image horizontally
-y --flipy Flip output image vertically
--height=N Set output height.  If only --height is specified, then output width will be calculated according to the source images aspect ratio.
-h --help Display a short help text
--grayscale Converts image to grayscale when using --html or --colors.
--html Make ASCII output in strict XHTML 1.0. (Will output in HTML for version 2.0.0 and above.)
--htmlls Make ASCII output in HTML (Living Standard), suitable for viewing with web browsers.  This is useful with big output dimensions, and if you want to check the result with a browser with small font.
--xhtml Make ASCII output in strict XHTML 1.0.
--html-fill Same as --fill.  You should use that option instead.
--html-no-bold Do not use bold text for HTML output.
--html-raw Output only the image in HTML codes, leaving out the rest of the webpage, so you can construct your own. (Will use <br> for version 2.0.0 and above instead of <br/>.)
--html-fontsize=N Set fontsize when using --html output.  Default is 4.
--html-title=... Set HTML output title.
--output=... Write ASCII output to given filename.  To explicitly specify standard output, use --output=-.
-i --invert Invert output image.  If you view a picture with white background, but you are using a display with light characters on a dark background, you should invert the image.
--red=...
--green=...
--blue=... When converting from RGB to grayscale, use the given weights to calculate luminance.  The default is red=0.2989, green=0.5866 and blue=0.1145.
--size=WIDTHxHEIGHT Set output dimension.
-v --verbose Print some verbose information to standard error when reading each JPEG image.
--width=N Set output width.  If you only specify the width, the height will be calculated automatically.
-V --version Print program version.
--zoom Sets output dimensions to your entire terminal window, disregarding source image aspect ratio.
jp2a returns 1 when errors are encountered, zero for no errors.
Convert and print imagefile.jpg using ASCII characters in 40 columns and 20 rows:
jp2a --size=40x20 imagefile.jpg
Download an image off the net, convert and print:
jp2a http://www.google.com/intl/en/logos/easter_logo.jpg
Output picture.jpg and picture2.jpg, each 80x25 characters, using the characters " ...ooxx@@" for output:
jp2a --size=80x25 --chars=" ...ooxx@@" picture.jpg picture2.jpg
Output image.jpg using 76 columns, height is automatically calculated from aspect ratio of image.jpg
cat image.jpg | jp2a --width=76 -
If you use jp2a together with ImageMagick's convert(1) then you can make good use of pipes, and have ImageMagick do all sorts of image conversions and effects on the source image.  For example:
convert somefile.gif jpg:- | jp2a - --width=80
Check out convert(1) options to see what you can do.  Convert can handle almost any image format, so with this combination you can convert images in e.g. PDF or AVI files to ASCII.
Although the default build of jp2a includes automatic downloading of files specified by URLs, you can explicitly download them by using curl(1) or wget(1), for example:
curl -s http://foo.bar/image.jpg | convert - jpg:- | jp2a -
If you have compiled jp2a with libcurl(3), you can download images by specifying URLs:
jp2a https://user:pass@foo.com/bar.jpg
The protocols recognized are ftp, ftps, file, http, https and tftp.
If you need more control of the downloading, you should use curl(1) or wget(1) and jp2a read the image from standard input.
jp2a uses pipe and fork to download images using libcurl (i.e., no exec or system calls) and therefore does not worry about malevolently formatted URLs.
You can extract the red channel by doing this:
jp2a somefile.jpg --red=1.0 --green=0.0 --blue=0.0
This will calculate luminance based on Y = R*1.0 + G*0.0 + B*0.0.  The default values is to use Y = R*0.2989 + G*0.5866 + B*0.1145.
The latest version of jp2a and news is always available from https://github.com/Talinx/jp2a.
cjpeg(1), djpeg(1), jpegtran(1), convert(1)
jp2a does not interpolate when resizing.  If you want better quality, try using convert(1) and convert the source image to the exact output dimensions before using jp2a.
Another issue is that jp2a skips some X-pixels along each scanline.  This gives a less precise output image, and will probably be corrected in future versions.
Christian Stigen Larsen and Christoph Raitzig
jp2a uses jpeglib to read JPEG files.  jpeglib is made by The Independent JPEG Group (IJG), who have a page at http://www.ijg.org
jp2a uses libpng to read PNG files.  libpng's homepage: http://libpng.org/pub/png/libpng.html
jp2a is distributed under the GNU General Public License v2.
ENCFS(1)                      Encrypted Filesystem                      ENCFS(1)
encfs - mounts or creates an encrypted virtual filesystem
encfs [--version] [-v|--verbose] [-c|--config] [-t|--syslogtag] [-s] [-f] [--annotate] [--standard] [--paranoia] [--insecure] [--reverse] [--reversewrite] [--extpass=program] [-S|--stdinpass] [--anykey] [--forcedecode] [-require-macs] [-i MINUTES|--idle=MINUTES] [-m|--ondemand] [--delaymount] [-u|--unmount] [--public] [--nocache] [--noattrcache] [--nodatacache] [--no-default-flags] [-o FUSE_OPTION] [-d|--fuse-debug] [-H|--fuse-help] rootdir mountPoint [-- [Fuse Mount Options]]
EncFS creates a virtual encrypted filesystem which stores encrypted data in the rootdir directory and makes the unencrypted data visible at the mountPoint directory.  The user must supply a password which is used to (indirectly) encrypt both filenames and file contents.
If EncFS is unable to find a supported filesystem at the specified rootdir, then the user will be asked if they wish to create a new encrypted filesystem at the specified location.  Options will be presented to the user allowing some control over the algorithms to use. As EncFS matures, there may be an increasing number of choices.
--version Shows EncFS version.  Using --verbose before --version may display additional information.
-c, --config Causes EncFS to use the supplied file as the configuration file.
-v, --verbose Causes EncFS to enable logging of various debug channels within EncFS.  Normally these logging messages are disabled and have no effect.  It is recommended that you run in foreground (-f) mode when running with verbose enabled.
-t, --syslogtag This option allows to set the syslog tag which will be used when messages are logged via syslog. By default the syslog tag is set to encfs.
-s  The -s (single threaded) option causes EncFS to run in single threaded mode.  By default, EncFS runs in multi-threaded mode.  This option is used during EncFS development in order to simplify debugging and allow it to run under memory checking tools.
-f  The -f (foreground) option causes EncFS to run in the foreground. Normally EncFS spawns off as a daemon and runs in the background, returning control to the spawning shell.  With the -f option, it will run in the foreground and any warning/debug log messages will be displayed on standard error.  In the default (background) mode, all log messages are logged via syslog.
--annotate Print annotation lines to stderr during configuration.
--standard If creating a new filesystem, this automatically selects standard configuration options, to help with automatic filesystem creation. This is the set of options that should be used unless you know what you're doing and have read the documentation.
When not creating a filesystem, this flag does nothing.
--paranoia Same as --standard, but for paranoia mode.
--insecure Allows you to disable data encoding, thus to pass plain data as is. Fully discouraged of course!
--reverse Normally EncFS provides a plaintext view of data on demand: it stores enciphered data and displays plaintext data.  With --reverse it takes as source plaintext data and produces enciphered data on-demand. This can be useful for creating remote encrypted backups, where you do not wish to keep the local files unencrypted.
For example, the following would create an encrypted view in /tmp/crypt-view.
encfs --reverse /home/me /tmp/crypt-view
You could then copy the /tmp/crypt-view directory in order to have a copy of the encrypted data.  You must also keep a copy of the file /home/me/.encfs6.xml which contains the filesystem information. Together, the two can be used to reproduce the unencrypted data:
ENCFS6_CONFIG=/home/me/.encfs6.xml encfs /tmp/crypt-view /tmp/plain-view
Now /tmp/plain-view contains the same data as /home/me
Note that --reverse mode only works with limited configuration options, so many settings may be disabled when used.  Incompatible options as for now : Filename Initialization Vector Chaining and External IV Chaining.