1.\" $NetBSD: compat_ultrix.8,v 1.16 2002/02/13 08:18:23 ross 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, 51.Fn ioctl Ns 's , 52or Ultrix kernel 53semantics that are difficult to emulate (e.g. Ultrix packetfilter) or 54buggy (e.g. Ultrix 55.Tn NIS ) . 56.Pp 57All Ultrix executables are static, so no shared libraries are required 58for Ultrix compatibility. However, Ultrix is based on a 59.Bx 4.3 60alpha release. Ultrix commands and libraries are often much older 61than their 62.Nx 63or even 64.Tn SunOS 4.x 65equivalents, and may require 66incompatible configuration files. 67.Sh SYSTEM CONFIGURATION FILES 68Set up 69.Pa resolv.conf 70and 71.Pa svc.conf 72as below: 73.Pp 74.Bl -tag -width 123 -compact -offset indent 75.It # mkdir -p /emul/ultrix/etc 76.br 77.It # cd /emul/ultrix/etc 78.br 79.It # egrep 'domain|nameserver' /etc/resolv.conf \*[Gt] ./resolv.conf 80.br 81.It # cp -p /usr/share/examples/emul/ultrix/etc/* ./ 82.El 83.Ss /etc/resolv.conf 84The Ultrix resolver library only understands 85.Sy domain 86and 87.Sy nameserver 88lines in 89.Xr resolv.conf 5 . 90You should create a copy of 91.Pa /etc/resolv.conf 92containing only those commands and put it in 93.Pa /emul/ultrix/etc/resolv.conf . 94Note that the 95domain search order used by Ultrix executables may not be the same as 96native binaries; there is no good way around this. 97.Ss /etc/svc.conf 98Ultrix uses 99.Pa /etc/svc.conf 100to select an ordered search of 101.Tn NIS , 102Hesiod, 103or local flat-file mappings. You should create an 104.Pa /emul/ultrix/etc/svc.conf 105specifying either local files or bind (DNS) 106lookups for all Ultrix name services. 107.Sh SEE ALSO 108.Xr resolv.conf 5 109.Sh BUGS 110RISC Ultrix 111.Tn NIS 112(YP) is known to not work. The Ultrix 113.Tn NIS 114libraries have a consistent endian-ness bug. Ultrix 115.Tn NIS 116client will not inter-operate with the 117.Nx 118.Xr ypbind 8 119process. The only workaround is to use 120.Pa /etc/svc.conf 121to disable 122.Tn NIS 123(YP). 124.Pp 125The ndbm hashed-password file used by Ultrix are incompatible with the 126db hashed-password file used by 127.Nx . 128There is no good solution for 129this. 130.Tn NIS 131would be a good one, if Ultrix 132.Tn NIS 133worked. 134.Pp 135The API used by Xservers to talk to the kernel is currently compatible 136with Ultrix 4.1. An implementation of the Ultrix 4.2 Xws interface 137(used by X11R6) is in progress. 138.Pp 139A complete list of things which fail to work in Ultrix compatibility 140mode should be added here. 141