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