Shell & core reference
Look up command behavior, shell syntax, system calls, and kernel interfaces.
Keep the installed manual close: online documentation may describe a newer release than the one on your host. Distinguish shell builtins, external commands, library functions, and system calls when looking up a name.
Use Bash for shell expansion and quoting, Coreutils for common file and text tools, Git for repository operations, and Make for build rules. Use Linux man-pages and kernel documentation for interfaces beneath the command line.
No matching references. Try a broader term or clear the filters.
Look up command behavior, shell syntax, system calls, and kernel interfaces.
-
Bash reference manual
Resolve quoting, expansion, redirection, and shell-control questions before relying on a command in a script.
Current GNU Bash · Project documentation · Selection reviewed -
GNU Coreutils manual
Check the precise behavior of common file, text, and checksum utilities, including options that differ across operating systems.
GNU utilities · not BSD command variants · Project documentation · Selection reviewed -
Git command documentation
Consult command semantics, revisions, and configuration when repository behavior needs a precise explanation.
Version-selectable Git manuals · Project documentation · Selection reviewed -
GNU Make manual
Understand dependency evaluation, variable expansion, recipes, and parallel execution when a build behaves unexpectedly.
GNU Make · not all make implementations · Project documentation · Selection reviewed -
Linux man-pages collection
Find the correct manual section for an interface and distinguish kernel behavior from a similarly named command.
System calls, libraries and selected tools · Project documentation · Selection reviewed -
Linux kernel administrator guide
Look up kernel parameters, reporting procedures, and subsystem administration; verify compatibility with the running kernel.
Current upstream kernel documentation · Project documentation · Selection reviewed
How this library is selected
References are selected for a concrete operational task, with preference for project and distribution documentation. Annotations describe when to use a source; version labels make its scope explicit.
Selection reviewed means the destination, subject, and version scope were checked. It is not a claim that every upstream command has been tested. Original guides identify their own test environment. Platform filters also include references that apply across distributions.