compat_osf1 - setup for running OSF/1 binaries under emulation
OpenBSD supports running OSF/1 (a.k.a Digital UNIX, a.k.a.
on alpha systems. Most programs should work, including
that use the shared object libraries. Programs that make
system calls will not work. The OSF/1 compatibility feature
for kernels compiled with the COMPAT_OSF1 option and
To run dynamically linked programs, the OSF/1 shared libraries, runtime
linker, and certain configuration files found in /etc are
These are installed in a "shadow root" directory called
file operations done by OSF/1 programs run under OpenBSD
will look in
this directory first, and fall back to the file system proper. So, if an
OSF/1 program opens /etc/svc.conf, OpenBSD will first try to
/emul/osf1/etc/svc.conf, and if that file does not exist it
will then try
/etc/svc.conf. Shared libraries and configuration specific
should be installed in the shadow tree.
Setting up /emul/osf1
Access to an OSF/1 machine is needed and, if the licensing
the following files will have to be copied:
(The latter is required to run Netscape Navigator or Communicator.)
Or, simply NFS mount the appropriate directories under
The OpenBSD system's hostname(1) must contain a dot or resolv.conf(5)
must contain a search line. Without one of those, the OSF/1
will die and no hostname resolution will be possible.
Certain values in /emul/osf1/etc/svc.conf can cause programs
to fail with
``Bad system call''.
Pathnames pointed to by symbolic links are not looked up in
root when running an OSF/1 executable. This is not consistent.
Most Tru64 UNIX (OSF/1 release 5) programs depend on an undocumented system
call which is not currently supported.
OpenBSD 3.6 November 4, 1999
[ Back ]