NAME    [Toc]    [Back]

     compat_osf1 - setup for running OSF/1 binaries under  emulation

DESCRIPTION    [Toc]    [Back]

     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
direct MACH
     system calls will not work.  The OSF/1 compatibility feature
is active
     for   kernels  compiled  with  the  COMPAT_OSF1  option  and
kern.emul.osf1
     sysctl(8) enabled.

     To run dynamically linked programs,  the  OSF/1  shared  libraries, runtime
     linker,  and  certain  configuration files found in /etc are
also needed.
     These are installed in  a  "shadow  root"  directory  called
/emul/osf1.  Any
     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
open
     /emul/osf1/etc/svc.conf, and if that file does not exist  it
will then try
     /etc/svc.conf.   Shared libraries and configuration specific
to OSF/1
     should be installed in the shadow tree.

   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:

           /shlib
           /usr/shlib
           /etc/sia
           /usr/lib/X11/locale

     (The  latter is required to run Netscape Navigator or Communicator.)

     Also copy

           /etc/svc.conf
           /usr/ccs/lib/cmplrs/otabase/libots.so
           /sbin/loader

     Or, simply  NFS  mount  the  appropriate  directories  under
/emul/osf1.

SEE ALSO    [Toc]    [Back]

     options(4), config(8)

BUGS    [Toc]    [Back]

     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
resolver
     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
the shadow
     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