neulab/tldr huggingface dataset:
~/.task/pending.data The file that contains the tasks that are not yet done.
~/.task/completed.data The file that contains the completed ("done") tasks.
~/.task/undo.data The file that contains information needed by the "undo" command.
CREDITS & COPYRIGHTS Copyright (C) 2006 - 2021 T. Babej, P. Beckingham, F. Hernandez.
Taskwarrior is distributed under the MIT license. See https://www.opensource.org/licenses/mit-license.php for more information.
taskrc(5), task-color(5), task-sync(5)
For more information regarding Taskwarrior, see the following:
The official site at <https://taskwarrior.org>
The official code repository at <https://github.com/GothenburgBitFactory/taskwarrior>
You can contact the project by emailing <support@GothenburgBitFactory.org>
Bugs in Taskwarrior may be reported to the issue-tracker at <https://github.com/GothenburgBitFactory/taskwarrior/issues>
CPPCHECK(1)                   cppcheck User Manual                   CPPCHECK(1)
cppcheck - Tool for static C/C++ code analysis
cppcheck [--check-config] [--check-library] [-D<id>] [-U<id>] [--enable=<id>] [--error-exitcode=<n>] [--errorlist] [--exitcode-suppressions=<file>] [--file-list=<file>] [--force] [--help] [-I<dir>] [--includes-file=<file>] [--config-exclude=<dir>] [--config-excludes-file=<file>] [--include=<file>] [-i<dir>] [--inconclusive] [--inline-suppr] [-j<jobs>] [-l<load>] [--language=<language>] [--library=<cfg>] [--max-configs=<limit>] [--max-ctu-depth=<limit>] [--platform=<type>] [--quiet] [--relative-paths=<paths>] [--report-progress] [--rule=<rule>] [--rule-file=<file>] [--std=<id>] [--suppress=<spec>] [--suppressions-list=<file>] [--suppress-xml=<.xml file>] [--template='<text>'] [--verbose] [--version] [--xml] [--xml-version=<version>]] [file or path] ...
Cppcheck is a command-line tool that tries to detect bugs that your C/C++ compiler doesn't see. It is versatile, and can check non-standard code including various compiler extensions, inline assembly code, etc. Its internal preprocessor can handle includes, macros, and several preprocessor commands. While Cppcheck is highly configurable, you can start using it just by giving it a path to the source code.
Analyze given C/C++ files for common errors.
--check-config Check Cppcheck configuration. The normal code analysis is disabled by this flag.
--check-library Show information messages when library files have incomplete info.
-D<id> By default Cppcheck checks all configurations. Use -D to limit the checking. When -D is used the checking is limited to the given configuration. Example: -DDEBUG=1 -D__cplusplus
-U<id> By default Cppcheck checks all configurations. Use '-U' to explicitly hide certain #ifdef <id> code paths from checking. Example: '-UDEBUG'
--enable=<id> Enable additional checks. The available ids are:
all Enable all checks. It is recommended to only use --enable=all when the whole program is scanned, because this enables unusedFunction.
warning Enable warning messages
style Enable all coding style checks. All messages with the severities 'style', 'performance' and 'portability' are enabled.
performance Enable performance messages
portability Enable portability messages
information Enable information messages
unusedFunction Check for unused functions. It is recommend to only enable this when the whole program is scanned
missingInclude Warn if there are missing includes. For detailed information use --check-config
By default none of the additional checks are enabled. Several ids can be given if you separate them with commas, e.g. --enable=style,unusedFunction. See also --std
--error-exitcode=<n> If errors are found, integer <n> is returned instead of default 0. EXIT_FAILURE is returned if arguments are not valid or if no input files are provided. Note that your operating system can modify this value, e.g. 256 can become 0.
--errorlist Print a list of all possible error messages in XML format.
--exitcode-suppressions=<file> Used when certain messages should be displayed but should not cause a non-zero exitcode.
--file-list=<file> Specify the files to check in a text file. One filename per line. When file is -, the file list will be read from standard input.
-f, --force Force checking of files that have a lot of configurations. Error is printed if such a file is found so there is no reason to use this by default. If used together with --max-configs=, the last option is the one that is effective.
-h, --help Print help text.
-I <dir> Give path to search for include files. Give several -I parameters to give several paths. First given path is searched for contained header files first. If paths are relative to source files, this is not needed.
--includes-file=<file> Specify directory paths to search for included header files in a text file. Add one include path per line. First given path is searched for contained header files first. If paths are relative to source files, this is not needed.
--config-exclude=<dir> Path (prefix) to be excluded from configuration checking. Preprocessor configurations defined in headers (but not sources) matching the prefix will not be considered for evaluation of configuration alternatives.
--config-exclude-file=<file> A file that contains a list of config-excludes.
--include=<file> Force inclusion of a file before the checked file. Can be used for example when checking the Linux kernel, where autoconf.h needs to be included for every file compiled. Works the same way as the GCC -include option.
-i <dir> Give path to ignore. Give several -i parameters to ignore several paths. Give directory name or filename with path as parameter. Directory name is matched to all parts of the path.
--inconclusive Allow that Cppcheck reports even though the analysis is inconclusive. There are false positives with this option. Each result must be carefully investigated before you know if it is good or bad.
--inline-suppr Enable inline suppressions. Use them by placing comments in the form: // cppcheck-suppress memleak before the line to suppress.
-j <jobs> Start <jobs> threads to do the checking work.
-l <load> Specifies that no new threads should be started if there are other threads running and the load average is at least <load> (ignored on non UNIX-like systems)
--language=<language> Forces cppcheck to check all files as the given language. Valid values are: c, c++
--library=<cfg> Use library configuration.
--max-configs=<limit> Maximum number of configurations to check in a file before skipping it. Default is 12. If used together with --force, the last option is the one that is effective.
--max-ctu-depths=<limit> Maximum depth in whole program analysis. Default is 2.
--platform=<type> Specifies platform specific types and sizes.The available platforms are:
unix32 32 bit unix variant
unix64 64 bit unix variant
win32A 32 bit Windows ASCII character encoding
win32W 32 bit Windows UNICODE character encoding
win64 64 bit Windows
By default the platform which was used to compile Cppcheck is used.
-q, --quiet Only print something when there is an error.
-rp, -rp=<paths>, --relative-paths;, --relative-paths=<paths> Use relative paths in output. When given, <paths> are used as base. You can separate multiple paths by ';'. Otherwise path where source files are searched is used. E.g. if given value is test, when checking test/test.cpp, the path in output will be test.cpp instead of test/test.cpp. The feature uses string comparison to create relative paths, so using e.g. ~ for home folder does not work. It is currently only possible to apply the base paths to files that are on a lower level in the directory tree.
--report-progress Report progress when checking a file.
--rule=<rule> Match regular expression to create your own checks. E.g. rule "/ 0" can be used to check division by zero. This command is only available if cppcheck was compiled with HAVE_RULES=yes.
--rule-file=<file> Use given rule XML file. See https://sourceforge.net/projects/cppcheck/files/Articles/ for more info about the syntax. This command is only available if cppcheck was compiled with HAVE_RULES=yes.
--std=<id> Set standard. The available options are:
posix POSIX compatible code
c89 C code is C89 compatible
c99 C code is C99 compatible
c11 C code is C11 compatible (default)
c++03 C++ code is C++03 compatible
c++11 C++ code is C++11 compatible (default)
Example to set more than one standards: 'cppcheck --std=c99 --std=posix file.cpp'
--suppress=<spec> Suppress a specific warning. The format of <spec> is: [error id]:[filename]:[line]. The [filename] and [line] are optional. [error id] may be * to suppress all warnings (for a specified file or files). [filename] may contain the wildcard characters * or ?.
--suppressions-list=<file> Suppress warnings listed in the file. Each suppression is in the format of <spec> above.
--suppress-xml=<.xml file> Use suppressions defined in xml as described in the manual
--template='<text>' Format the error messages. E.g. '{file}:{line},{severity},{id},{message}' or '{file}({line}):({severity}) {message}'. Pre-defined templates: gcc, vs
-v, --verbose More detailed error reports
--xml Write results in XML to error stream
--xml-version=<version> Select the XML file version. Currently versions 1 and 2 are available. The default version is 1.
The program was written by Daniel Marjamäki and Cppcheck team. See AUTHORS file for list of team members.
Reijo Tomperi <aggro80@users.sourceforge.net> Wrote this manpage for the Debian system.
Full list of features: https://sourceforge.net/p/cppcheck/wiki/Home/
Copyright © 2009 - 2016 Reijo Tomperi
This manual page was written for the Debian system (but may be used by others).
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or (at your option) any later version published by the Free Software Foundation.
APROPOS(1)                 BSD General Commands Manual                APROPOS(1)
apropos, whatis — search manual page databases
apropos [-afk] [-C file] [-M path] [-m path] [-O outkey] [-S arch] [-s section] expression ...
The apropos and whatis utilities query manual page databases generated by makewhatis(8), evaluating expression for each file in each database.  By default, they display the names, section numbers, and description lines of all matching manuals.
By default, apropos searches for makewhatis(8) databases in the default paths stipulated by man(1) and uses case-insensitive extended regular expression matching over manual names and descriptions (the Nm and Nd macro keys).  Multiple terms imply pairwise -o.
whatis is a synonym for apropos -f.
-a      Instead of showing only the title lines, show the complete manual pages, just like man(1) -a would.  If the standard output is a terminal device and -c is not specified, use less(1) to paginate them.  In -a mode, the options -IKOTW described in the mandoc(1) manual are also available.
-C file Specify an alternative configuration file in man.conf(5) format.
-f      Search for all words in expression in manual page names only.  The search is case-insensitive and matches whole words only.  In this mode, macro keys, comparison operators, and logical operators are not available.
-k      Support the full expression syntax.  It is the default for apropos.
-M path Use the colon-separated path instead of the default list of paths searched for makewhatis(8) databases.  Invalid paths, or paths without manual databases, are ignored.
-m path Prepend the colon-separated paths to the list of paths searched for makewhatis(8) databases.  Invalid paths, or paths without manual databases, are ignored.
-O outkey Show the values associated with the key outkey instead of the manual descriptions.
-S arch Restrict the search to pages for the specified machine(1) architecture.  arch is case-insensitive.  By default, pages for all architectures are shown.
-s section Restrict the search to the specified section of the manual.  By default, pages from all sections are shown.  See man(1) for a listing of sections.
The options -chlw are also supported and are documented in man(1).  The options -fkl are mutually exclusive and override each other.
An expression consists of search terms joined by logical operators -a (and) and -o (or).  The -a operator has precedence over -o and both are evaluated left-to-right.
( expr ) True if the subexpression expr is true.
expr1 -a expr2 True if both expr1 and expr2 are true (logical ‘and’).
expr1 [-o] expr2 True if expr1 and/or expr2 evaluate to true (logical ‘or’).
term    True if term is satisfied.  This has syntax [[key[,key...]](=|~)]val, where key is an mdoc(7) macro to query and val is its value.  See Macro Keys for a list of available keys. Operator = evaluates a substring, while ~ evaluates a case- sensitive extended regular expression.
-i term If term is a regular expression, it is evaluated case- insensitively.  Has no effect on substring terms.
Results are sorted first according to the section number in ascending numerical order, then by the page name in ascending ascii(7) alphabetical order, case-insensitive.
Each output line is formatted as
name[, name...](sec) - description
Where “name” is the manual's name, “sec” is the manual section, and “description” is the manual's short description.  If an architecture is specified for the manual, it is displayed as
name(sec/arch) - description
Resulting manuals may be accessed as
$ man -s sec name
If an architecture is specified in the output, use
$ man -s sec -S arch name
Macro Keys Queries evaluate over a subset of mdoc(7) macros indexed by makewhatis(8). In addition to the macro keys listed below, the special key any may be used to match any available macro key.
Names and description: Nm      manual name Nd      one-line manual description arch    machine architecture (case-insensitive) sec     manual section number
Sections and cross references: Sh      section header (excluding standard sections) Ss      subsection header Xr      cross reference to another manual page Rs      bibliographic reference
Semantic markup for command line utilities: Fl      command line options (flags) Cm      command modifier Ar      command argument Ic      internal or interactive command Ev      environmental variable Pa      file system path
Semantic markup for function libraries: Lb      function library name In      include file Ft      function return type Fn      function name Fa      function argument type and name Vt      variable type Va      variable name Dv      defined variable or preprocessor constant Er      error constant Ev      environmental variable
Various semantic markup: An      author name Lk      hyperlink Mt      “mailto” hyperlink Cd      kernel configuration declaration Ms      mathematical symbol Tn      tradename
Physical markup: Em      italic font or underline Sy      boldface font Li      typewriter font
Text production: St      reference to a standards document At      AT&T UNIX version reference Bx      BSD version reference Bsx     BSD/OS version reference Nx      NetBSD version reference Fx      FreeBSD version reference Ox      OpenBSD version reference Dx      DragonFly version reference
In general, macro keys are supposed to yield complete results without expecting the user to consider actual macro usage.  For example, results include:
Fa   function arguments appearing on Fn lines Fn   function names marked up with Fo macros In   include file names marked up with Fd macros Vt   types appearing as function return types and types appearing in function arguments in the SYNOPSIS
MANPAGER  Any non-empty value of the environment variable MANPAGER is used instead of the standard pagination program, less(1); see man(1) for details.  Only used if -a or -l is specified.
MANPATH   A colon-separated list of directories to search for manual pages; see man(1) for details.  Overridden by -M, ignored if -l is specified.
PAGER     Specifies the pagination program to use when MANPAGER is not defined.  If neither PAGER nor MANPAGER is defined, less(1) is used.  Only used if -a or -l is specified.
mandoc.db      name of the makewhatis(8) keyword database /etc/man.conf  default man(1) configuration file
The apropos utility exits 0 on success, and >0 if an error occurs.
Search for ".cf" as a substring of manual names and descriptions:
$ apropos =.cf
Include matches for ".cnf" and ".conf" as well:
$ apropos =.cf =.cnf =.conf
Search in names and descriptions using a case-sensitive regular expression:
$ apropos '~set.?[ug]id'
Search for all manual pages in a given section:
$ apropos -s 9 .
Search for manuals in the library section mentioning both the "optind" and the "optarg" variables:
$ apropos -s 3 Va=optind -a Va=optarg
Do exactly the same as calling whatis with the argument "ssh":
$ apropos -- -i 'Nm~[[:<:]]ssh[[:>:]]'
The following two invocations are equivalent:
$ apropos -S arch -s section expression
$ apropos \( expression \) -a arch~^(arch|any)$ -a sec~^section$
man(1), re_format(7), makewhatis(8)
The apropos utility is compliant with the IEEE Std 1003.1-2008 (“POSIX.1”) specification of man(1) -k.
All options, the whatis command, support for logical operators, macro keys, substring matching, sorting of results, the environment variables MANPAGER and MANPATH, the database format, and the configuration file are extensions to that specification.
Part of the functionality of whatis was already provided by the former manwhere utility in 1BSD.  The apropos and whatis utilities first appeared in 2BSD.  They were rewritten from scratch for OpenBSD 5.6.
The -M option and the MANPATH variable first appeared in 4.3BSD; -m in 4.3BSD-Reno; -C in 4.4BSD Lite1; and -S and -s in OpenBSD 4.5 for apropos and in OpenBSD 5.6 for whatis.  The options -acfhIKklOTWw appeared in OpenBSD 5.7.
Bill Joy wrote manwhere in 1977 and the original BSD apropos and whatis in February 1979.  The current version was written by Kristaps Dzonsons <kristaps@bsd.lv> and Ingo Schwarze <schwarze@openbsd.org>.
svn(1)                       General Commands Manual                      svn(1)
svn - Subversion command line client tool
svn command [options] [args]
Subversion is a version control system, which allows you to keep old versions of files and directories (usually source code), keep a log of who, when, and why changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a single copy of the master sources.  This copy is called the source ``repository''; it contains all the information to permit extracting previous versions of those files at any time.
For more information about the Subversion project, visit http://subversion.apache.org.
Documentation for Subversion and its tools, including detailed usage explanations of the svn, svnadmin, svnserve and svnlook programs, historical background, philosophical approaches and reasonings, etc., can be found at http://svnbook.red-bean.com/.
Run `svn help' to access the built-in tool documentation.
GIT-SHOW(1)                        Git Manual                        GIT-SHOW(1)
git-show - Show various types of objects
git show [<options>] [<object>...]
Shows one or more objects (blobs, trees, tags and commits).
For commits it shows the log message and textual diff. It also presents the merge commit in a special format as produced by git diff-tree --cc.
For tags, it shows the tag message and the referenced objects.
For trees, it shows the names (equivalent to git ls-tree with --name-only).
For plain blobs, it shows the plain contents.
The command takes options applicable to the git diff-tree command to control how the changes the commit introduces are shown.
This manual page describes only the most frequently used options.
<object>... The names of objects to show (defaults to HEAD). For a more complete list of ways to spell object names, see "SPECIFYING REVISIONS" section in gitrevisions(7).
The options below can be used to change the way git show generates diff output.
--diff-merges=(off|none|on|first-parent|1|separate|m|combined|c|dense-combined|cc), --no-diff-merges Specify diff format to be used for merge commits. Default is dense-combined unless --first-parent is in use, in which case first-parent is the default.
git show v1.0.0 Shows the tag v1.0.0, along with the object the tags points at.
git show v1.0.0^{tree} Shows the tree pointed to by the tag v1.0.0.
git show -s --format=%s v1.0.0^{commit} Shows the subject of the commit pointed to by the tag v1.0.0.
git show next~10:Documentation/README Shows the contents of the file Documentation/README as they were current in the 10th last commit of the branch next.
git show master:Makefile master:t/Makefile Concatenates the contents of said Makefiles in the head of the branch master.
GETFACL(1)                    Access Control Lists                    GETFACL(1)
getfacl - get file access control lists
getfacl [-aceEsRLPtpndvh] file ...
getfacl [-aceEsRLPtpndvh] -
For each file, getfacl displays the file name, owner, the group, and the Access Control List (ACL). If a directory has a default ACL, getfacl also displays the default ACL. Non-directories cannot have default ACLs.
If getfacl is used on a file system that does not support ACLs, getfacl displays the access permissions defined by the traditional file mode permission bits.
The output format of getfacl is as follows: 1:  # file: somedir/ 2:  # owner: lisa 3:  # group: staff 4:  # flags: -s- 5:  user::rwx 6:  user:joe:rwx               #effective:r-x 7:  group::rwx                 #effective:r-x 8:  group:cool:r-x 9:  mask::r-x 10:  other::r-x 11:  default:user::rwx 12:  default:user:joe:rwx       #effective:r-x 13:  default:group::r-x 14:  default:mask::r-x 15:  default:other::---
Lines 1--3 indicate the file name, owner, and owning group.
Line 4 indicates the setuid (s), setgid (s), and sticky (t) bits: either the letter representing the bit, or else a dash (-). This line is included if any of those bits is set and left out otherwise, so it will not be shown for most files. (See CONFORMANCE TO POSIX 1003.1e DRAFT STANDARD 17 below.)
Lines 5, 7 and 10 correspond to the user, group and other fields of the file mode permission bits. These three are called the base ACL entries. Lines 6 and 8 are named user and named group entries. Line 9 is the effective rights mask. This entry limits the effective rights granted to all groups and to named users. (The file owner and others permissions are not affected by the effective rights mask; all other entries are.)  Lines 11--15 display the default ACL associated with this directory. Directories may have a default ACL. Regular files never have a default ACL.
The default behavior for getfacl is to display both the ACL and the default ACL, and to include an effective rights comment for lines where the rights of the entry differ from the effective rights.
If output is to a terminal, the effective rights comment is aligned to column 40. Otherwise, a single tab character separates the ACL entry and the effective rights comment.
The ACL listings of multiple files are separated by blank lines.  The output of getfacl can also be used as input to setfacl.
PERMISSIONS Process with search access to a file (i.e., processes with read access to the containing directory of a file) are also granted read access to the file's ACLs.  This is analogous to the permissions required for accessing the file mode.
-a, --access Display the file access control list.
-d, --default Display the default access control list.
-c, --omit-header Do not display the comment header (the first three lines of each file's output).
-e, --all-effective Print all effective rights comments, even if identical to the rights defined by the ACL entry.
-E, --no-effective Do not print effective rights comments.
-s, --skip-base Skip files that only have the base ACL entries (owner, group, others).
-R, --recursive List the ACLs of all files and directories recursively.
-L, --logical Logical walk, follow symbolic links to directories. The default behavior is to follow symbolic link arguments, and skip symbolic links encountered in subdirectories.  Only effective in combination with -R.
-P, --physical Physical walk, do not follow symbolic links to directories. This also skips symbolic link arguments.  Only effective in combination with -R.
-t, --tabular Use an alternative tabular output format. The ACL and the default ACL are displayed side by side. Permissions that are ineffective due to the ACL mask entry are displayed capitalized. The entry tag names for the ACL_USER_OBJ and ACL_GROUP_OBJ entries are also displayed in capital letters, which helps in spotting those entries.
-p, --absolute-names Do not strip leading slash characters (`/'). The default behavior is to strip leading slash characters.
-n, --numeric List numeric user and group IDs
-v, --version Print the version of getfacl and exit.
--  End of command line options. All remaining parameters are interpreted as file names, even if they start with a dash character.
-   If the file name parameter is a single dash character, getfacl reads a list of files from standard input.
CONFORMANCE TO POSIX 1003.1e DRAFT STANDARD 17 If the environment variable POSIXLY_CORRECT is defined, the default behavior of getfacl changes in the following ways: Unless otherwise specified, only the ACL is printed. The default ACL is only printed if the -d option is given. If no command line parameter is given, getfacl behaves as if it was invoked as ``getfacl -''.  No flags comments indicating the setuid, setgid, and sticky bits are generated.
Please send your bug reports and comments to the above address.
setfacl(1), acl(5)
ngrok(8)                   BSD System Manager's Manual                  ngrok(8)
nrgok â€” secure introspectable tunnels to localhost
nrgok [options] port
nrgok creates a tunnel from the public internet to a port on your local machine. You can give this URL to anyone to allow them to try out a web site you're developing without doing any deployment.
It captures all traffic through the tunnel. It displays information about the HTTP traffic for your inspection. Raw request/response bytes, parsed headers and form data, JSON/XML syntax checking and more are included. It can also replay requests.
By default, nrgok will establish tunnel with ngrok.com servers. They are free to use for basic functionalities. You can also setup your own server by using ngrokd.
port is either the local port to be forwarded or an IP address.
To get available options, use ngrok -h.
ngrokd(8)
The nrgok program was written by Alan Shreve.
semanage(8)                                                          semanage(8)
semanage - SELinux Policy Management tool
semanage {import,export,login,user,port,interface,module,node,fcontext,boolean,permissive,dontaudit,ibpkey,ibendport} ...  positional arguments:
import Import local customizations
export Output local customizations
login Manage login mappings between linux users and SELinux confined users
user Manage SELinux confined users (Roles and levels for an SELinux user)
port Manage network port type definitions
interface Manage network interface type definitions
module Manage SELinux policy modules
node Manage network node type definitions
fcontext Manage file context mapping definitions
boolean Manage booleans to selectively enable functionality
permissive Manage process type enforcement mode
dontaudit Disable/Enable dontaudit rules in policy
ibpkey Manage infiniband pkey type definitions
ibendport Manage infiniband end port type definitions
semanage is used to configure certain elements of SELinux policy without requiring modification to or recompilation from policy sources.  This includes the mapping from Linux usernames to SELinux user identities (which controls the initial security context assigned to Linux users when they login and bounds their authorized role set) as well as security context mappings for various kinds of objects, such as network ports, interfaces, infiniband pkeys and endports, and nodes (hosts) as well as the file context mapping. See the EXAMPLES section below for some examples of common usage.  Note that the semanage login command deals with the mapping from Linux usernames (logins) to SELinux user identities, while the semanage user command deals with the mapping from SELinux user identities to authorized role sets.  In most cases, only the former mapping needs to be adjusted by the administrator; the latter is principally defined by the base policy and usually does not require modification.
-h, --help List help information
selinux(8), semanage-boolean(8), semanage-dontaudit(8), semanage- export(8), semanage-fcontext(8), semanage-import(8), semanage- interface(8), semanage-login(8), semanage-module(8), semanage-node(8), semanage-permissive(8), semanage-port(8), semanage-user(8) semanage- ibkey(8), semanage-ibendport(8),
This man page was written by Daniel Walsh <dwalsh@redhat.com> and Russell Coker <rcoker@redhat.com>. Examples by Thomas Bleher <ThomasBleher@gmx.de>.  usage: semanage [-h]
BOOT(8)                 BSD/i386 System Manager's Manual                 BOOT(8)
boot — system bootstrapping procedures
Power fail and crash recovery.  Normally, the system will reboot itself at power-up or after crashes.  An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user operations.
Cold starts.  Most i386 PCs attempt to boot first from floppy disk drive 0 (sometimes known as drive A:) and, failing that, from hard disk drive 0 (sometimes known as drive C:, or as drive 0x80 to the BIOS).  Some BIOSes allow you to change this default sequence, and may also include a CD-ROM drive as a boot device.
Some newer PCs boot using UEFI firmware, not BIOS.  That process is described in uefi(8).
A three-stage bootstrap is employed.  Control is passed from the boot blocks (bootstrap stages one and two) to a third-stage bootstrap program, loader(8).  This third stage provides more sophisticated control over the booting process than it is possible to achieve in the boot blocks, which are constrained by occupying limited fixed space on a given disk or slice.
The remainder of this subsection deals only with the boot blocks.  The loader(8) program is documented separately.
After the boot blocks have been loaded, you should see a prompt similar to the following:
>> FreeBSD/x86 BOOT Default: 0:ad(0,a)/boot/loader boot:
The automatic boot will attempt to load /boot/loader from partition ‘a’ of either the floppy or the hard disk.  This boot may be aborted by typing any character on the keyboard at the ‘boot:’ prompt.  At this time, the following input will be accepted:
?       Give a short listing of the files in the root directory of the default boot device, as a hint about available boot files.  (A ? may also be specified as the last segment of a path, in which case the listing will be of the relevant subdirectory.)
bios_drive:interface(unit,[slice,]part)filename [-aCcDdghmnPprsv] [-Sspeed] Specify boot file and flags.
bios_drive The drive number as recognized by the BIOS.  0 for the first drive, 1 for the second drive, etc.
interface The type of controller to boot from.  Note that the controller is required to have BIOS support since the BIOS services are used to load the boot file image.
The supported interfaces are:
ad    ST506, IDE, ESDI, RLL disks on a WD100[2367] or lookalike controller fd    5 1/4" or 3 1/2" High density floppies da    SCSI disk on any supported SCSI controller
unit    The unit number of the drive on the interface being used. 0 for the first drive, 1 for the second drive, etc.
[slice,]part The partition letter inside the BSD portion of the disk. See bsdlabel(8).  By convention, only partition ‘a’ contains a bootable image.  If sliced disks are used (“fdisk partitions”), any slice (1 for the first slice, 2 for the second slice, etc.) can be booted from, with the default (if not specified) being the active slice or, otherwise, the first FreeBSD slice.  If slice is specified as 0, the first FreeBSD slice (also known as “compatibility” slice) is booted from.
filename The pathname of the file to boot (relative to the root directory on the specified partition).  Defaults to /boot/kernel/kernel.  Symbolic links are not supported (hard links are).
[-aCcDdghmnPpqrsv] [-Sspeed] Boot flags:
-a    during kernel initialization, ask for the device to mount as the root file system. -C    try to mount root file system from a CD-ROM. -c    this flag is currently a no-op. -D    boot with the dual console configuration.  In the single configuration, the console will be either the internal display or the serial port, depending on the state of the -h option below.  In the dual console configuration, both the internal display and the serial port will become the console at the same time, regardless of the state of the -h option. -d    enter the DDB kernel debugger (see ddb(4)) as early as possible in kernel initialization. -g    use the GDB remote debugging protocol. -h    force the serial console.  For instance, if you boot from the internal console, you can use the -h option to force the kernel to use the serial port as its console device. -m    mute the console to suppress all kernel console input and output during the boot. -n    ignore key press to interrupt boot before loader(8) is invoked. -P    probe the keyboard.  If no keyboard is found, the -D and -h options are automatically set. -p    pause after each attached device during the device probing phase. -q    be quiet, do not write anything to the console unless automatic boot fails or is disabled.  This option only affects second-stage bootstrap, to prevent next stages from writing to the console use in combination with the -m option. -r    use the statically configured default for the device containing the root file system (see config(8)). Normally, the root file system is on the device that the kernel was loaded from. -s    boot into single-user mode; if the console is marked as “insecure” (see ttys(5)), the root password must be entered. -Sspeed set the speed of the serial console to speed.  The default is 9600 unless it has been overridden by setting BOOT_COMCONSOLE_SPEED in make.conf(5) and recompiling and reinstalling the boot blocks. -v    be verbose during device probing (and later).
Use the /boot.config file to set the default configuration options for the boot block code.  See boot.config(5) for more information about the /boot.config file.
/boot.config  parameters for the boot blocks (optional) /boot/boot1   first stage bootstrap file /boot/boot2   second stage bootstrap file /boot/loader  third stage bootstrap /boot/kernel/kernel default kernel /boot/kernel.old/kernel typical non-default kernel (optional)
When disk-related errors occur, these are reported by the second-stage bootstrap using the same error codes returned by the BIOS, for example “Disk error 0x1 (lba=0x12345678)”.  Here is a partial list of these error codes:
0x1   Invalid argument 0x2   Address mark not found 0x4   Sector not found 0x8   DMA overrun 0x9   DMA attempt across 64K boundary 0xc   Invalid media 0x10  Uncorrectable CRC/ECC error 0x20  Controller failure 0x40  Seek failed 0x80  Timeout
NOTE: On older machines, or otherwise where EDD support (disk packet interface support) is not available, all boot-related files and structures (including the kernel) that need to be accessed during the boot phase must reside on the disk at or below cylinder 1023 (as the BIOS understands the geometry).  When a “Disk error 0x1” is reported by the second-stage bootstrap, it generally means that this requirement has not been adhered to.
ddb(4), boot.config(5), make.conf(5), mount.conf(5), ttys(5), boot0cfg(8), btxld(8), config(8), efibootmgr(8), efivar(8), gpart(8), gptboot(8), gptzfsboot(8), halt(8), loader(8), nextboot(8), reboot(8), shutdown(8), uefi(8), zfsbootcfg(8)
The bsdlabel format used by this version of BSD is quite different from that of other architectures.
Due to space constraints, the keyboard probe initiated by the -P option is simply a test that the BIOS has detected an “extended” keyboard.  If an “XT/AT” keyboard (with no F11 and F12 keys, etc.) is attached, the probe will fail.
DELUSER(8)                   System Manager's Manual                  DELUSER(8)
deluser, delgroup - remove a user or group from the system
deluser [options] [--force] [--remove-home] [--remove-all-files] [--backup] [--backup-to DIR] user
deluser --group [options] group delgroup [options] [--only-if-empty] group
deluser [options] user group
COMMON OPTIONS [--quiet] [--system] [--help] [--version] [--conf FILE]
deluser and delgroup remove users and groups from the system according to command line options and configuration information in /etc/deluser.conf and /etc/adduser.conf.  They are friendlier front ends to the userdel and groupdel programs, removing the home directory as option or even all files on the system owned by the user to be removed, running a custom script, and other features.  deluser and delgroup can be run in one of three modes:
Remove a normal user If called with one non-option argument and without the --group option, deluser will remove a normal user.
By default, deluser will remove the user without removing the home directory, the mail spool  or any other files on the system owned by the user. Removing the home directory and mail spool can be achieved using the --remove-home option.
The --remove-all-files option removes all files on the system owned by the user. Note that if you activate both options --remove-home will have no effect because all files including the home directory and mail spool are already covered by the --remove-all-files option.
If you want to backup all files before deleting them you can activate the --backup option which will create a file username.tar(.gz|.bz2) in the directory specified by the --backup-to option (defaulting to the current working directory). Both the remove and backup options can also be activated for default in the configuration file /etc/deluser.conf. See deluser.conf(5) for details.
If you want to remove the root account (uid 0), then use the --force parameter; this may prevent to remove the root user by accident.
If the file /usr/local/sbin/deluser.local exists, it will be executed after the user account has been removed in order to do any local cleanup. The arguments passed to deluser.local are: username uid gid home-directory
Remove a group If deluser is called with the --group option, or delgroup is called, a group will be removed.
Warning: The primary group of an existing user cannot be removed.
If the option --only-if-empty is given, the group won't be removed if it has any members left.
Remove a user from a specific group If called with two non-option arguments, deluser will remove a user from a specific group.
--conf FILE Use FILE instead of the default files /etc/deluser.conf and /etc/adduser.conf
--group Remove a group. This is the default action if the program is invoked as delgroup.
--quiet Suppress progress messages.
--system Only delete if user/group is a system user/group. This avoids accidentally deleting non-system users/groups. Additionally, if the user does not exist, no error value is returned. This option is mainly for use in Debian package maintainer scripts.
--only-if-empty Only remove if no members are left.
--backup Backup all files contained in the userhome and the mailspool-file to a file named /$user.tar.bz2 or /$user.tar.gz.
--backup-to Place the backup files not in / but in the directory specified by this parameter. This implicitly sets --backup also.
--remove-home Remove the home directory of the user and its mailspool. If --backup is specified, the files are deleted after having performed the backup.
--remove-all-files Remove all files from the system owned by this user. Note: --remove-home does not have an effect any more. If --backup is specified, the files are deleted after having performed the backup.
0      The action was successfully executed.
1      The user to delete was not a system account. No action was performed.
2      There is no such user. No action was performed.
3      There is no such group. No action was performed.
4      Internal error. No action was performed.
5      The group to delete is not empty. No action was performed.
6      The user does not belong to the specified group. No action was performed.
7      You cannot remove a user from its primary group. No action was performed.
8      The required perl-package 'perl modules' is not installed. This package is required to perform the requested actions. No action was performed.
9      For removing the root account the parameter "--force" is required. No action was performed.
/etc/deluser.conf Default configuration file for deluser and delgroup
/usr/local/sbin/deluser.local Optional custom add-ons.
adduser(8), deluser.conf(5), groupdel(8), userdel(8)
Copyright (C) 2000 Roland Bauerschmidt. Modifications (C) 2004 Marc Haber and Joerg Hoh.  This manpage and the deluser program are based on adduser which is: Copyright (C) 1997, 1998, 1999 Guy Maor. Copyright (C) 1995 Ted Hajek, with a great deal borrowed from the original Debian adduser Copyright (C) 1994 Ian Murdock.  deluser is free software; see the GNU General Public Licence version 2 or later for copying conditions.  There is no warranty.
pdffonts(1)                  General Commands Manual                 pdffonts(1)
pdffonts - Portable Document Format (PDF) font analyzer (version 3.03)
pdffonts [options] [PDF-file]
Pdffonts lists the fonts used in a Portable Document Format (PDF) file along with various information for each font.
The following information is listed for each font:
name   the font name, exactly as given in the PDF file (potentially including a subset prefix)
type   the font type – see below for details
encoding the font encoding
emb    "yes" if the font is embedded in the PDF file
sub    "yes" if the font is a subset
uni    "yes" if there is an explicit "ToUnicode" map in the PDF file (the absence of a ToUnicode map doesn't necessarily mean that the text can't be converted to Unicode)
object ID the font dictionary object ID (number and generation)
PDF files can contain the following types of fonts:
Type 1 Type 1C – aka Compact Font Format (CFF) Type 3 TrueType CID Type 0 – 16-bit font with no specified type CID Type 0C – 16-bit PostScript CFF font CID TrueType – 16-bit TrueType font
-f number Specifies the first page to analyze.
-l number Specifies the last page to analyze.
-subst List the substitute fonts that poppler will use for non embedded fonts.
The pdffonts software and documentation are copyright 1996–2011 Glyph & Cog, LLC.
pdfdetach(1), pdfimages(1), pdfinfo(1), pdftocairo(1), pdftohtml(1), pdftoppm(1), pdftops(1), pdftotext(1), pdfseparate(1), pdfsig(1), pdfunite(1)
TLMGR(1)               User Contributed Perl Documentation              TLMGR(1)
tlmgr - the native TeX Live Manager
tlmgr [option...] action [option...] [operand...]
tlmgr manages an existing TeX Live installation, both packages and configuration options.  For information on initially downloading and installing TeX Live, see <https://tug.org/texlive/acquire.html>.
The most up-to-date version of this documentation (updated nightly from the development sources) is available at <https://tug.org/texlive/tlmgr.html>, along with procedures for updating "tlmgr" itself and information about test versions.
WARNING: tlmgr in Debian runs always in user mode
TeX Live is organized into a few top-level schemes, each of which is specified as a different set of collections and packages, where a collection is a set of packages, and a package is what contains actual files.  Schemes typically contain a mix of collections and packages, but each package is included in exactly one collection, no more and no less. A TeX Live installation can be customized and managed at any level.
See <https://tug.org/texlive/doc> for all the TeX Live documentation available.
After successfully installing TeX Live, here are a few common operations with "tlmgr":
"tlmgr option repository ctan" "tlmgr option repository http://mirror.ctan.org/systems/texlive/tlnet" Tell "tlmgr" to use a nearby CTAN mirror for future updates; useful if you installed TeX Live from the DVD image and want to have continuing updates.  The two commands are equivalent; "ctan" is just an alias for the given url.  Caveat: "mirror.ctan.org" resolves to many different hosts, and they are not perfectly synchronized; we recommend updating only daily (at most), and not more often.
"tlmgr update --list" Report what would be updated without actually updating anything.
"tlmgr update --all" Make your local TeX installation correspond to what is in the package repository (typically useful when updating from CTAN).
"tlmgr info" what Display detailed information about a package what, such as the installation status and description, of searches for what in all packages.
For all the capabilities and details of "tlmgr", please read the following voluminous information.
The following options to "tlmgr" are global options, not specific to any action.  All options, whether global or action-specific, can be given anywhere on the command line, and in any order.  The first non-option argument will be the main action.  In all cases, "--"option and "-"option are equivalent, and an "=" is optional between an option name and its value.
--repository url|path Specify the package repository from which packages should be installed or updated, either a local directory or network location, as below. This overridesthe default package repository found in the installation's TeX Live Package Database (a.k.a. the TLPDB, which is given entirely in the file "tlpkg/texlive.tlpdb").
This "--repository" option changes the location only for the current run; to make a permanent change, use "option repository" (see the "option" action).
As an example, you can choose a particular CTAN mirror with something like this:
-repository http://ctan.example.org/its/ctan/dir/systems/texlive/tlnet
Of course a real hostname and its particular top-level CTAN directory have to be specified.  The list of CTAN mirrors is available at <https://ctan.org/mirrors>.
Here's an example of using a local directory:
-repository /local/TL/repository
For backward compatibility and convenience, "--location" and "--repo" are accepted as aliases for this option.
Locations can be specified as any of the following:
"/some/local/dir" "file:/some/local/dir" Equivalent ways of specifying a local directory.
"ctan" "http://mirror.ctan.org/systems/texlive/tlnet" Pick a CTAN mirror automatically, trying for one that is both nearby and up-to-date. The chosen mirror is used for the entire download. The bare "ctan" is merely an alias for the full url. (See <https://ctan.org> for more about CTAN and its mirrors.)
"http://server/path/to/tlnet" Standard HTTP. If the (default) LWP method is used, persistent connections are supported. TL can also use "curl" or "wget" to do the downloads, or an arbitrary user-specified program, as described in the "tlmgr" documentation (<https://tug.org/texlive/doc/tlmgr.html#ENVIRONMENT-VARIABLES>).
"https://server/path/to/tlnet" Again, if the (default) LWP method is used, this supports persistent connections. Unfortunately, some versions of "wget" and "curl" do not support https, and even when "wget" supports https, certificates may be rejected even when the certificate is fine, due to a lack of local certificate roots. The simplest workaround for this problem is to use http or ftp.
"ftp://server/path/to/tlnet" If the (default) LWP method is used, persistent connections are supported.
"user@machine:/path/to/tlnet" "scp://user@machine/path/to/tlnet" "ssh://user@machine/path/to/tlnet" These forms are equivalent; they all use "scp" to transfer files. Using "ssh-agent" is recommended. (Info: <https://en.wikipedia.org/wiki/OpenSSH>, <https://en.wikipedia.org/wiki/Ssh-agent>.)
If the repository is on the network, trailing "/" characters and/or trailing "/tlpkg" and/or "/archive" components are ignored.
--gui [action] "tlmgr" has a graphical interface as well as the command line interface.  You can give this option, "--gui", together with an action to be brought directly into the respective screen of the GUI. For example, running
tlmgr --gui update
starts you directly at the update screen.  If no action is given, the GUI will be started at the main screen.