Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   9087 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

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 vari‐
     ous 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 pro‐
     cedure 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 off‐
     sets with information in the upper 32 bits.  These errors should rarely
     happen, but can be avoided by mounting this filesystem with offset trans‐
     lation 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

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome