|
|
compat_linux(8) -- setup for running Linux binaries under emulation
|
|
OpenBSD supports running Linux binaries. This only applies to i386 systems for now. Both the a.out and ELF binary formats are supported. Most programs should work, including the ones that use the Linu... |
|
compat_osf1(8) -- setup for running OSF/1 binaries under emulation
|
|
OpenBSD supports running OSF/1 (a.k.a Digital UNIX, a.k.a. Tru64) binaries on alpha systems. Most programs should work, including the ones that use the shared object libraries. Programs that make dire... |
|
compat_sunos(8) -- setup for running SunOS binaries under emulation
|
|
OpenBSD/sparc and some of the OpenBSD/m68k architectures can run SunOS executables. Most executables will work. The SunOS compatibility feature is active for kernels compiled with the COMPAT_SUNOS opt... |
|
compat_svr4(8) -- setup for running SVR4/iBCS2 binaries under emulation
|
|
OpenBSD supports running SVR4/iBCS2 binaries. This code has been tested on i386 and sparc systems. Most programs should work, but not ones that use or depend on: kernel internal data structures the /p... |
|
compat_ultrix(8) -- setup for running Ultrix binaries under emulation
|
|
OpenBSD/mips and OpenBSD/vax architectures can run RISC ULTRIX and Vax ULTRIX executables, respectively. However, the user is responsible for the legal issues of ensuring that they have a right to use... |
|
comsat(8) -- biff server
|
|
comsat is the server process which receives reports of incoming mail and notifies users if they have requested this service. comsat receives messages on a datagram port associated with the ``biff'' ... |
|
config(8) -- build kernel compilation directories or modify a kernel
|
|
In the first synopsis form, the config program creates a kernel build directory from the kernel configuration file specified by config-file. In the second synopsis form, config allows editing of the k... |
|
crash(8) -- system failure and diagnosis
|
|
This section explains what happens when the system crashes and (very briefly) how to analyze crash dumps. When the system crashes voluntarily it prints a message of the form panic: why i gave up the g... |
|
cron(8) -- clock daemon
|
|
The cron daemon schedules commands to be run at specified dates and times. Commands that are to be run periodically are specified within crontab(5) files. Commands that are only to be run once are sch... |
|
cryptoadm(8) -- manage the ActivCard, CRYPTOCard and
|
|
The tokenadm utility displays and edits user entries in the various token databases. It may also be invoked as one the following: activadm, cryptoadm, or snkadm. The options are as follows: -1 Display... |
|
cryptoinit(8) -- modify or add user in ActivCard, CRYPTOCard,
|
|
The tokeninit utility may also be invoked by one of the following names: activinit, cryptoinit, or snkinit. Depending on the name it was invoked as, it will initialize the system information to allow ... |
|
cvsbug(8) -- send problem report (PR) about CVS to a central support site
|
|
cvsbug is a tool used to submit problem reports (PRs) to a central support site. In most cases the correct site will be the default. This argument indicates the support site which is responsible for t... |
|
daily(8) -- periodic system maintenance
|
|
The three files /etc/daily, /etc/weekly, and /etc/monthly are shell scripts run on a periodic basis by the clock daemon, cron(8). They take care of some basic administrative tasks. The results are mai... |
