.\" $OpenBSD: compat_osf1.8,v 1.7 2007/05/31 19:19:58 jmc Exp $
.\" $NetBSD: compat_osf1.8,v 1.8 2002/01/14 13:50:43 wiz Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" This code is derived from software contributed to The NetBSD Foundation
.\" by Roland C. Dowdeswell.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\"    must display the following acknowledgement:
.\"        This product includes software developed by the NetBSD
.\"        Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\"    contributors may be used to endorse or promote products derived
.\"    from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.Dd $Mdocdate: May 31 2007 $
.Dt COMPAT_OSF1 8
.Os
.Sh NAME
.Nm compat_osf1
.Nd setup for running OSF/1 binaries under emulation
.Sh DESCRIPTION
.Ox
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 direct MACH system calls will not work.
The OSF/1 compatibility feature is active for kernels compiled with the
.Nm COMPAT_OSF1
option and kern.emul.osf1
.Xr sysctl 8
enabled.
.Pp
To run dynamically linked programs, the OSF/1 shared libraries,
runtime linker, and certain configuration files found in
.Pa /etc
are also needed.
These are installed in a "shadow root" directory called
.Pa /emul/osf1 .
Any file operations done by OSF/1 programs run under
.Ox
will look in this directory first, and fall back to the file system proper.
So, if an OSF/1 program opens
.Pa /etc/svc.conf ,
.Ox
will first try to open
.Pa /emul/osf1/etc/svc.conf ,
and if that file does not exist it will then try
.Pa /etc/svc.conf .
Shared libraries and configuration specific to OSF/1 should be installed
in the shadow tree.
.Ss Setting up /emul/osf1
Access to an OSF/1 machine is needed and, if the licensing details permit,
the following files will have to be copied:
.Bd -unfilled -offset indent
/shlib
/usr/shlib
/etc/sia
/usr/lib/X11/locale
.Ed
.Pp
(The latter is required to run Netscape Navigator or Communicator.)
.Pp
Also copy
.Bd -unfilled -offset indent
/etc/svc.conf
/usr/ccs/lib/cmplrs/otabase/libots.so
/sbin/loader
.Ed
.Pp
Or, simply NFS mount the appropriate directories under
.Pa /emul/osf1 .
.Sh SEE ALSO
.Xr options 4 ,
.Xr config 8
.Sh BUGS
The
.Ox
system's
.Xr hostname 1
.Em must
contain a dot
.Em or
.Xr resolv.conf 5
must contain a
.Li search
line.
Without one of those, the OSF/1 resolver will die and no hostname resolution
will be possible.
.Pp
Certain values in
.Pa /emul/osf1/etc/svc.conf
can cause programs to fail with
.Dq Bad system call .
.Pp
Pathnames pointed to by symbolic links are not looked up in the
shadow root when running an OSF/1 executable.
This is not consistent.
.Pp
Most Tru64 UNIX (OSF/1 release 5) programs depend on an undocumented
system call which is not currently supported.