ACPIDUMP(8) - System Manager’s Manual # ACPIDUMP(8) - System Manager’s Manual
NAME # acpidump - dump ACPI tables
SYNOPSIS # acpidump -o prefix
DESCRIPTION # The acpidump command stores ACPI tables from physical memory into files specified by prefix. If prefix specifies a directory, the generated files will be of the form <prefix>/<sig>.<id>. Otherwise, they will be named <prefix>.<sig>.<id>. “sig” is the signature of the ACPI Table; “id” is unique for each table.
...
IKECTL(8) - System Manager’s Manual # IKECTL(8) - System Manager’s Manual
NAME # ikectl - control the IKEv2 daemon
SYNOPSIS # ikectl [-q] [-s socket] command [arg …]
DESCRIPTION # The ikectl program controls the iked(8) daemon and provides commands to maintain a simple X.509 certificate authority (CA) for IKEv2 peers.
The options are as follows:
-q
Don’t ask for confirmation of any default options.
-s socket
Use socket instead of the default /var/run/iked.
...
Depends,
Ports,
Ld,
Pkg_add,
Packages,
Specs,
Ld.so,
Helper,
Bsd.port.mk,
Ldconfig,
Library-Specs LIBRARY-SPECS(7) - Miscellaneous Information Manual # LIBRARY-SPECS(7) - Miscellaneous Information Manual
NAME # library-specs - shared library name specifications
DESCRIPTION # Each WANTLIB item in the ports tree conforms to
[path/]libname[=major[.minor]] or
[path/]libname[>=major[.minor]] All libraries that a package needs must be mentioned in that list. Except for system and X11 libraries, they all must be reachable through LIB_DEPENDS and RUN_DEPENDS, directly, or indirectly through recursive dependencies.
Conversely, the ports tree uses WANTLIB to check whether a given LIB_DEPENDS will be required at runtime for shared libraries, and thus turn it into a @depend line (see pkg_create(1)) .
...
PACKAGE(5) - File Formats Manual # PACKAGE(5) - File Formats Manual
NAME # package, packing-list, plist - format for OpenBSD binary packages and packing-lists
DESCRIPTION # Binary packages for OpenBSD can be created using pkg_create(1) and are usually manipulated using pkg_add(1), pkg_mklocatedb(1), or pkg_info(1).
The basic underlying format is an archive following the ustar specification that can be handled with tar(1) and compressed using gzip(1).
Package names always end in “.
...
PACKAGES-SPECS(7) - Miscellaneous Information Manual # PACKAGES-SPECS(7) - Miscellaneous Information Manual
NAME # packages-specs - binary package names specifications
DESCRIPTION # Each package has a name consisting of at most three parts:
stem-version[-flavors] The stem part identifies the package. It may contain some dashes, but its form is mostly conventional. For instance, japanese packages usually start with a ‘ja’ prefix, e.g., “ja-kterm-6.2.0”.
The version part starts at the first digit that follows a ‘-’, and goes on up to the following ‘-’, or to the end of the package name, whichever comes first.
...
PKGPATH(7) - Miscellaneous Information Manual # PKGPATH(7) - Miscellaneous Information Manual
NAME # pkgpath - ports tree location for a package build
DESCRIPTION # Each location in the ports tree is uniquely identified through a pkgpath, which encodes the directory, flavor and subpackage information that allows the build of a package. This is not to be confused with PKG_PATH, the list of URLs from which pkg_add(1) retrieves binary packages.
...
PORTS(7) - Miscellaneous Information Manual # PORTS(7) - Miscellaneous Information Manual
NAME # ports - contributed applications
DESCRIPTION # The OpenBSD Ports Collection is the infrastructure used to create binary packages for third party applications.
For normal usage refer to packages(7), as most ports produce binary packages which are available from the official HTTP mirrors.
Each port contains any patches necessary to make the original application source code compile and run on OpenBSD.
...