diff options
Diffstat (limited to 'static/netbsd/man8/compat_ultrix.8 4.html')
| -rw-r--r-- | static/netbsd/man8/compat_ultrix.8 4.html | 106 |
1 files changed, 0 insertions, 106 deletions
diff --git a/static/netbsd/man8/compat_ultrix.8 4.html b/static/netbsd/man8/compat_ultrix.8 4.html deleted file mode 100644 index f4275366..00000000 --- a/static/netbsd/man8/compat_ultrix.8 4.html +++ /dev/null @@ -1,106 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">COMPAT_ULTRIX(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">COMPAT_ULTRIX(8)</td> - </tr> -</table> -<div class="manual-text"> -<section class="Sh"> -<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1> -<p class="Pp"><code class="Nm">compat_ultrix</code> — - <span class="Nd">setup procedure for ULTRIX compatibility on MIPS and VAX - architectures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><span class="Ux">NetBSD</span>/mips and - <span class="Ux">NetBSD</span>/vax architectures can run Risc ULTRIX and VAX - ULTRIX executables, respectively. However, you have to worry about the legal - issues of ensuring that you have a right to use any ULTRIX binaries on your - machine.</p> -<p class="Pp" id="ioctl">Most executables will work. The exceptions include - programs that use proprietary, ULTRIX-specific features (LAT, CI support, - DECnet support) and various system calls, - <a class="permalink" href="#ioctl"><code class="Fn">ioctl</code></a>()'s, or - ULTRIX kernel semantics that are difficult to emulate (e.g. ULTRIX - packetfilter) or buggy (e.g. ULTRIX NIS).</p> -<p class="Pp">All ULTRIX executables are static, so no shared libraries are - required for ULTRIX compatibility. However, ULTRIX is based on a - <span class="Ux">4.3BSD</span> alpha release. ULTRIX commands and libraries - are often much older than their <span class="Ux">NetBSD</span> or even SunOS - 4.x equivalents, and may require incompatible configuration files.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYSTEM_CONFIGURATION_FILES"><a class="permalink" href="#SYSTEM_CONFIGURATION_FILES">SYSTEM - CONFIGURATION FILES</a></h1> -<p class="Pp">Set up <span class="Pa">resolv.conf</span> and - <span class="Pa">svc.conf</span> as below:</p> -<p class="Pp"></p> -<div class="Bd-indent"> -<dl class="Bl-tag Bl-compact"> - <dt># mkdir -p /emul/ultrix/etc</dt> - <dd> - <br/> - </dd> - <dt># cd /emul/ultrix/etc</dt> - <dd> - <br/> - </dd> - <dt># egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf</dt> - <dd> - <br/> - </dd> - <dt># cp -p /usr/share/examples/emul/ultrix/etc/* ./</dt> - <dd style="width: auto;"> </dd> -</dl> -</div> -<section class="Ss"> -<h2 class="Ss" id="/etc/resolv.conf"><a class="permalink" href="#/etc/resolv.conf">/etc/resolv.conf</a></h2> -<p class="Pp">The ULTRIX resolver library only understands - <a class="permalink" href="#domain"><b class="Sy" id="domain">domain</b></a> - and - <a class="permalink" href="#nameserver"><b class="Sy" id="nameserver">nameserver</b></a> - lines in <a class="Xr">resolv.conf(5)</a>. You should create a copy of - <span class="Pa">/etc/resolv.conf</span> containing only those commands and - put it in <span class="Pa">/emul/ultrix/etc/resolv.conf</span>. Note that - the domain search order used by ULTRIX executables may not be the same as - native binaries; there is no good way around this.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="/etc/svc.conf"><a class="permalink" href="#/etc/svc.conf">/etc/svc.conf</a></h2> -<p class="Pp">ULTRIX uses <span class="Pa">/etc/svc.conf</span> to select an - ordered search of NIS, Hesiod, or local flat-file mappings. You should - create an <span class="Pa">/emul/ultrix/etc/svc.conf</span> specifying - either local files or bind (DNS) lookups for all ULTRIX name services.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE - ALSO</a></h1> -<p class="Pp"><a class="Xr">resolv.conf(5)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">RISC ULTRIX NIS (YP) is known to not work. The ULTRIX NIS - libraries have a consistent endian-ness bug. ULTRIX NIS client will not - inter-operate with the <span class="Ux">NetBSD</span> - <a class="Xr">ypbind(8)</a> process. The only workaround is to use - <span class="Pa">/etc/svc.conf</span> to disable NIS (YP).</p> -<p class="Pp">The ndbm hashed-password file used by ULTRIX are incompatible with - the db hashed-password file used by <span class="Ux">NetBSD</span>. There is - no good solution for this. NIS would be a good one, if ULTRIX NIS - worked.</p> -<p class="Pp">The API used by Xservers to talk to the kernel is currently - compatible with ULTRIX 4.1. An implementation of the ULTRIX 4.2 Xws - interface (used by X11R6) is in progress.</p> -<p class="Pp">A complete list of things which fail to work in ULTRIX - compatibility mode should be added here.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">January 16, 1999</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |