compat_osf1(8) [netbsd man page]

COMPAT_OSF1(8)						    BSD System Manager's Manual 					    COMPAT_OSF1(8)

NAME

     compat_osf1 -- setup procedure for running OSF/1 binaries

DESCRIPTION

     NetBSD supports running OSF/1 (a.k.a Digital Unix, a.k.a. Tru64) binaries on NetBSD/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 enabled (see options(4)).

     To run dynamically linked programs, you will need the OSF/1 shared libraries, runtime linker, and certain configuration files found in /etc.
     These are installed in a ``shadow root'' directory called /emul/osf1.  Any file operations done by OSF/1 programs run under NetBSD will look
     in this directory first, and fall back to the file system proper.	So, if an OSF/1 program opens /etc/svc.conf, NetBSD 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
     The simple technique is to install pkgsrc/emulators/osf1_lib.  (You may also want to install pkgsrc/www/navigator and/or pkgsrc/www/communi-
     cator.)

     Alternatively, if you have access to an OSF/1 machine and if the licensing details permit, you can copy the contents of:
	   /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

     config(1), options(4)

BUGS

     Your hostname(1) must contain a dot or your 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.

BSD
								 November 4, 1999							       BSD

COMPAT_ULTRIX(8)					    BSD System Manager's Manual 					  COMPAT_ULTRIX(8)

NAME

     compat_ultrix -- setup procedure for ULTRIX compatibility on MIPS and VAX architectures

DESCRIPTION

     NetBSD/mips and NetBSD/vax architectures can run Risc ULTRIX and VAX ULTRIX executables, respectively.  However, you have to worry about the
     legal issues of ensuring that you have a right to use any ULTRIX binaries on your machine.

     Most executables will work.  The exceptions include programs that use proprietary, ULTRIX-specific features (LAT, CI support, DECnet support)
     and various system calls, ioctl()'s, or ULTRIX kernel semantics that are difficult to emulate (e.g. ULTRIX packetfilter) or buggy (e.g.
     ULTRIX NIS).

     All ULTRIX executables are static, so no shared libraries are required for ULTRIX compatibility.  However, ULTRIX is based on a 4.3BSD alpha
     release.  ULTRIX commands and libraries are often much older than their NetBSD or even SunOS 4.x equivalents, and may require incompatible
     configuration files.

SYSTEM CONFIGURATION FILES

     Set up resolv.conf and svc.conf as below:

	   # mkdir -p /emul/ultrix/etc
	   # cd /emul/ultrix/etc
	   # egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf
	   # cp -p /usr/share/examples/emul/ultrix/etc/*     ./

   /etc/resolv.conf
     The ULTRIX resolver library only understands domain and nameserver lines in resolv.conf(5).  You should create a copy of /etc/resolv.conf
     containing only those commands and put it in /emul/ultrix/etc/resolv.conf.  Note that the domain search order used by ULTRIX executables may
     not be the same as native binaries; there is no good way around this.

   /etc/svc.conf
     ULTRIX uses /etc/svc.conf to select an ordered search of NIS, Hesiod, or local flat-file mappings.  You should create an
     /emul/ultrix/etc/svc.conf specifying either local files or bind (DNS) lookups for all ULTRIX name services.

SEE ALSO

     resolv.conf(5)

BUGS

     RISC ULTRIX NIS (YP) is known to not work.  The ULTRIX NIS libraries have a consistent endian-ness bug.  ULTRIX NIS client will not inter-
     operate with the NetBSD ypbind(8) process.  The only workaround is to use /etc/svc.conf to disable NIS (YP).

     The ndbm hashed-password file used by ULTRIX are incompatible with the db hashed-password file used by NetBSD.  There is no good solution for
     this.  NIS would be a good one, if ULTRIX NIS worked.

     The API used by Xservers to talk to the kernel is currently compatible with ULTRIX 4.1.  An implementation of the ULTRIX 4.2 Xws interface
     (used by X11R6) is in progress.

     A complete list of things which fail to work in ULTRIX compatibility mode should be added here.

BSD
								 January 16, 1999							       BSD