1.\" $NetBSD: compat_ultrix.8,v 1.12 2000/07/05 15:45:35 msaitoh Exp $ 2.\" 3.\" Copyright (c) 1997 Jonathan Stone 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by Jonathan Stone. 17.\" 4. Neither the name of the author nor the names of its contributors 18.\" may be used to endorse or promote products derived from this software 19.\" without specific prior written permission. 20.\" 21.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND 22.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 23.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 24.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE 25.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 26.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 27.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 28.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 29.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 30.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 31.\" SUCH DAMAGE. 32.\" 33.Dd January 16, 1999 34.Dt COMPAT_ULTRIX 8 35.Os 36.Sh NAME 37.Nm compat_ultrix 38.Nd "setup procedure for Ultrix compatibility on mips and vax architectures" 39.Sh DESCRIPTION 40.Nx Ns Tn /mips 41and 42.Nx Ns Tn /vax 43architectures can run Risc ULTRIX and Vax 44ULTRIX executables, respectively. However, you have to worry about 45the legal issues of ensuring that you have a right to use any ULTRIX 46binaries on your machine. 47.Pp 48Most executables will work. The exceptions include programs that use 49proprietary, Ultrix-specific features (LAT, CI support, DECnet 50support) and various system calls, ioctl()'s, or Ultrix kernel 51semantics that are difficult to emulate (e.g., Ultrix packetfilter) or 52buggy (e.g., Ultrix 53.Tn NIS ). 54.Pp 55All Ultrix executables are static, so no shared libraries are required 56for Ultrix compatibility. However, Ultrix is based on a 57.Bx 4.3 58alpha release. Ultrix commands and libraries are often much older 59than their 60.Nx 61or even 62.Tn SunOS 4.x 63equivalents, and may require 64incompatible configuration files. 65.Sh SYSTEM CONFIGURATION FILES 66Set up resolv.conf and svc.conf as below: 67.Pp 68.Bl -tag -width 123 -compact -offset indent 69.It # mkdir -p /emul/ultrix/etc 70.br 71.It # cd /emul/ultrix/etc 72.br 73.It # egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf 74.br 75.It # cp -p /usr/share/examples/emul/ultrix/etc/* ./ 76.El 77.Pp 78.Ss /etc/resolv.conf 79The Ultrix resolver library only understands 80.Sy domain 81and 82.Sy nameserver 83lines in 84.Xr /etc/resolv.conf 5 . 85You should create a copy of /etc/resolv.conf containing only those 86commands and put it in /emul/ultrix/etc/resolv.conf. Note that the 87domain search order used by Ultrix executables may not be the same as 88native binaries; there is no good way around this. 89.Pp 90.Ss /etc/svc.conf 91Ultrix uses /etc/svc.conf to select an ordered search of 92.Tn NIS , 93Hesiod, 94or local flat-file mappings. You should create an 95/emul/ultrix/etc/svc.conf specifying either local files or bind (DNS) 96lookups for all Ultrix name services. 97.Sh BUGS 98RISC Ultrix 99.Tn NIS 100(YP) is known to not work. The Ultrix 101.Tn NIS 102libraries have a consistent endian-ness bug. Ultrix 103.Tn NIS 104client will not inter-operate with the 105.Nx 106.Xr ypbind 8 107process. The only workaround is to use 108/etc/svc.conf to disable 109.Tn NIS 110(YP). 111.Pp 112The ndbm hashed-password file used by Ultrix are incompatible with the 113db hashed-password file used by 114.Nx . 115There is no good solution for 116this. 117.Tn NIS 118would be a good one, if Ultrix 119.Tn NIS 120worked. 121.Pp 122The API used by Xservers to talk to the kernel is currently compatible 123with Ultrix 4.1. An implementation of the Ultrix 4.2 Xws interface 124(used by X11R6) is in progress. 125.Pp 126A complete list of things which fail to work in Ultrix compatibility 127mode should be added here. 128.Sh SEE ALSO 129.Xr resolv.conf 5 130