netbsd32(8) [netbsd man page]

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

NAME

     compat_netbsd32 -- setup procedure for 32-bit compatibility on 64-bit platforms

DESCRIPTION

     The compat_netbsd32 module allows NetBSD/sparc64 to run NetBSD/sparc executables, and NetBSD/amd64 to run NetBSD/i386 executables.

     To use compat_netbsd32, one must either have COMPAT_NETBSD32 and EXEC_ELF32 in the kernel, or load the compat_netbsd32 and exec_netbsd32 ker-
     nel modules.

     Static executables typically need no additional setup.  Dynamic binaries require the dynamic linker plus shared libraries.  Most of these
     files will need to be placed under /emul/netbsd32.

     The easiest method of installing support for these is via the emulators/netbsd32_compat14, emulators/netbsd32_compat15, and
     emulators/netbsd32_compat16 packages, provided in the NetBSD packages collection.	These install 32-bit a.out and ELF compatibility
     libraries, respectively.  The details of what is actually necessary for correct operation are given below.  This obviously is handled by the
     emulator packages.

     For a.out compatibility, /usr/libexec/ld.so from a 32-bit distribution is required to exist as /emul/netbsd32/usr/libexec/ld.so.  For 32-bit
     ELF compatibility, /usr/libexec/ld.elf_so needs to be in /emul/netbsd32/usr/libexec/ld.elf_so.

     The shared libraries for a.out binaries do not live under the /emul/netbsd32 directory, but under the /emul/aout directory, where the a.out
     dynamic linker will find them.

BUGS

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

     IPC is not well supported.

     sysctl(3) is not well supported.

BSD
								  March 11, 2006							       BSD

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

NAME

     compat_sunos -- setup procedure for m68k, sparc and sparc64 architectures

DESCRIPTION

     NetBSD/sparc64, NetBSD/sparc and some of the NetBSD/m68k architectures can run SunOS executables.	Most executables will work.

     The exceptions include programs that use the SunOS kvm library, and various system calls, ioctl()'s, or kernel semantics that are difficult
     to emulate.  The number of reasons why a program might fail to work is (thankfully) longer than the number of programs that fail to run.

     Static executables will normally run without any extra setup.  This procedure details the directories and files that must be set up to allow
     dynamically linked executables to work.

     The files you need are on your SunOS machine.  You need to worry about the legal issues of ensuring that you have a right to use the required
     files on your machine.  On your NetBSD machine, do the following:

	1.   mkdir -p /emul/sunos/usr/lib /emul/sunos/usr/5lib

	2.   cp SunOS:/usr/lib/lib*.so.*.* NetBSD:/emul/sunos/usr/lib

	3.   cp SunOS:/usr/5lib/lib*.so.*.* NetBSD:/emul/sunos/usr/5lib

	4.   cp SunOS:/usr/lib/ld.so NetBSD:/emul/sunos/usr/lib/ld.so

	5.   If you ever expect to use YP, you will want to create a link:
	     ln -s /var/run/ypbind.lock /etc/ypbind.lock

     Alternatively, you can use an NFS mount to accomplish the same effect.  On your NetBSD machine, do the following:

	1.   mkdir -p /emul/sunos/usr

	2.   mount SunOS:/usr /emul/sunos/usr

     This will place the SunOS libraries on your NetBSD machine in a location where the SunOS compatibility code will look for first, where they
     do not conflict with the standard libraries.

NOTES

     When using compat_sunos on NetBSD/sparc64, the COMPAT_NETBSD32 option must also be used.

BUGS

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

     SunOS executables can not handle directory offset cookies > 32 bits.  Should such an offset occur, you will see the message ``sunos_getdents:
     dir offset too large for emulated program''.  Currently, this can only happen on NFS mounted filesystems, mounted from servers that return
     offsets with information in the upper 32 bits.  These errors should rarely happen, but can be avoided by mounting this filesystem with offset
     translation enabled.  See the -X option to mount_nfs(8).  The -2 option to mount_nfs(8) will also have the desired effect, but is less
     preferable.

     The NetBSD/sparc64 support is less complete than the other ports.

BSD
								 February 3, 2001							       BSD