1.\" $NetBSD: compat_ultrix.8,v 1.4 1997/11/13 03:39:37 thorpej 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 June 7, 1997 34.Dt COMPAT_ULTRIX 8 35.Os NetBSD 36.Sh NAME 37.Nm compat_ultrix 38.Nd setup procedure for Ultrix compatibility on mips and vax architectures 39.Sh DESCRIPTION 40 41NetBSD/mips and NetBSD/vax architectures can run Risc ULTRIX and Vax 42ULTRIX executables, respectively. However, you have to worry about 43the legal issues of ensuring that you have a right to use any ULTRIX 44binaries on your machine. 45.Pp 46Most executables will work. The exceptions include programs that use 47proprietary, Ultrix-specific features (LAT, CI support, DECnet 48support) and various system calls, ioctl()'s, or Ultrix kernel 49semantics that are difficult to emulate (e.g., Ultrix packetfilter) or 50buggy (e.g., Ultrix YP). 51.Pp 52All Ultrix executables are static, so no shared libraries are required 53for Ultrix compatiblity. However, Ultrix is based on a 4.3BSD alpha 54release. Ultrix commands and libraries are often much older than 55their NetBSD or even SunOS 4.x equivalents, and may require incompatible 56configuration files. 57.Sh SYSTEM CONFIGURATION FILES 58Set up resolv.conf and svc.conf as below: 59.Pp 60.Bl -tag -width 123 -compact -offset indent 61.It # mkdir -p /emul/ultrix/etc 62.br 63.It # cd /emul/ultrix/etc 64.br 65.It # egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf 66.br 67.It # cp -p /usr/share/examples/emul/ultrix/etc/* ./ 68.El 69.Pp 70.Ss /etc/resolv.conf 71The Ultrix resolver library only understands 72.Sy domain 73and 74.Sy nameserver 75lines in 76.Xr /etc/resolv.conf 5 . 77You should create a copy of /etc/resolv.conf containing only those 78commands and put it in /emul/ultrix/etc/resolv.conf. Note that the 79domain search order used by Ultrix executables may not be the same as 80native binaries; there is no good way around this. 81.Pp 82.Ss /etc/svc.conf 83Ultrix uses /etc/svc.conf to select an ordered search of YP, Hesiod, 84or local flat-file mappings. You should create an 85/emul/ultrix/etc/svc.conf specifying either local files or bind (DNS) 86lookups for all Ultrix name services. 87.Sh BUGS 88.Pp 89RISC Ultrix YP(NIS) is know to not work. The Ultrix YP libraries have 90a consistent endian-ness bug. Ultrix YP client will not inter-operate 91with the NetBSD 92.Xr ypbind 8 93process. The only workaround is to use 94/etc/svc.conf to disable YP(NIS). 95.Pp 96The ndbm hashed-password file used by Ultrix are incompatible with the 97db hashed-password file used by NetBSD. There is no good solution for 98this. (YP would be a good one, if Ultrix YP worked.) 99.Pp 100The API used by Xservers to talk to the kernel is currently compatible 101with Ultrix 4.1. An implementation of the Ultrix 4.2 Xws interface 102(used by X11R6) is in progress. 103.Pp 104A complete list of things which fail to work in Ultrix compatibility 105mode should be added here. 106.Sh SEE ALSO 107.Xr resolv.conf 5 . 108