Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Uppercase ULTRIX. Igor Sobrado in PR 19678.

This commit is contained in:
wiz 2003-03-30 21:20:17 +00:00
parent 1f7cb18fb0
commit 3425830569
9 changed files with 38 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
dist/tcpdump/tcpdump.8 vendored
View File

@ -1,4 +1,4 @@
.\" $NetBSD: tcpdump.8,v 1.7 2002/12/16 10:35:04 wiz Exp $
.\" $NetBSD: tcpdump.8,v 1.8 2003/03/30 21:23:43 wiz Exp $
.\" @(#) Header: /tcpdump/master/tcpdump/tcpdump.1,v 1.120 2002/05/17 09:57:50 guy Exp (LBL)
.\"
.\" Copyright (c) 1987, 1988, 1989, 1990, 1991, 1992, 1994, 1995, 1996, 1997
@ -678,7 +678,7 @@ True if the DECNET source address is
.IR host ,
which may be an address of the form ``10.123'', or a DECNET host
name.
[DECNET host name support is only available on Ultrix systems
[DECNET host name support is only available on ULTRIX systems
that are configured to run DECNET.]
.IP "\fBdecnet dst \fIhost\fR"
True if the DECNET destination address is

4
share/man/man4/bba.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: bba.4,v 1.3 2001/09/21 09:11:40 gmcgarry Exp $
.\" $NetBSD: bba.4,v 1.4 2003/03/30 21:20:17 wiz Exp $
.\"
.\" Copyright (c) 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -59,4 +59,4 @@ The
.Nm
device driver appeared in
.Nx 1.5 .
The name for the driver was adopted from the same driver in Ultrix.
The name for the driver was adopted from the same driver in ULTRIX.

4
share/man/man4/bpf.4
View File

@ -1,6 +1,6 @@
.\" -*- nroff -*-
.\"
.\" $NetBSD: bpf.4,v 1.24 2003/02/25 10:35:13 wiz Exp $
.\" $NetBSD: bpf.4,v 1.25 2003/03/30 21:20:17 wiz Exp $
.\"
.\" Copyright (c) 1990, 1991, 1992, 1993, 1994
.\" The Regents of the University of California. All rights reserved.
@ -663,7 +663,7 @@ struct bpf_insn insns[] = {
The Enet packet filter was created in 1980 by Mike Accetta and
Rick Rashid at Carnegie-Mellon University. Jeffrey Mogul, at
Stanford, ported the code to BSD and continued its development from
1983 on. Since then, it has evolved into the Ultrix Packet Filter
1983 on. Since then, it has evolved into the ULTRIX Packet Filter
at DEC, a STREAMS NIT module under SunOS 4.1, and BPF.
.Sh AUTHORS
Steven McCanne, of Lawrence Berkeley Laboratory, implemented BPF in

4
share/man/man4/man4.pmax/fb.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: fb.4,v 1.3 2002/02/13 08:18:02 ross Exp $
.\" $NetBSD: fb.4,v 1.4 2003/03/30 21:20:18 wiz Exp $
.\"
.\" Copyright (c) 2001 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -55,7 +55,7 @@ The devices to which this applies are the
.Xr pm 4 (colour and mono),
.Xr px 4 , and
.Xr xcfb 4
frame buffers. It provides support for the Ultrix-compatible
frame buffers. It provides support for the ULTRIX-compatible
pm/QVSS-style interface, mostly so that X consortium Xservers work.
It also provides support for the Sun-style frame buffer interface
which is compatible with exisiting

4
share/man/man4/options.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: options.4,v 1.200 2003/03/30 18:05:22 wiz Exp $
.\" $NetBSD: options.4,v 1.201 2003/03/30 21:20:17 wiz Exp $
.\"
.\" Copyright (c) 1996
.\" Perry E. Metzger. All rights reserved.
@ -211,7 +211,7 @@ option for 64-bit kernels, in addition to this option.
.It Cd options COMPAT_ULTRIX
On those architectures that support it, this enables binary
compatibility with
.Tn Ultrix
.Tn ULTRIX
applications built for the same architecture.
This currently is limited to the pmax.
The functionality of this option is unknown.

8
share/man/man4/scc.4
View File

@ -27,7 +27,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $NetBSD: scc.4,v 1.1 2001/09/21 09:11:41 gmcgarry Exp $
.\" $NetBSD: scc.4,v 1.2 2003/03/30 21:20:18 wiz Exp $
.\"
.Dd September 19, 2001
.Dt SCC 4
@ -93,12 +93,12 @@ supported.
.Pp
The mapping from device-special files (major and minor number) to chip
and port is arguably backwards.
.Tn Ultrix
.Tn ULTRIX
tries to hide the hardware mapping, but
.Nx
does not.
Users wanting to use
.Tn "Ultrix"
.Tn ULTRIX
compatible tty names
.Pa /dev/tty0
and
@ -106,4 +106,4 @@ and
for the
.Nm
comm-port lines should make links or device-special files which match
their hardware setup.
their hardware setup.

40
share/man/man8/compat_ultrix.8
View File

@ -1,4 +1,4 @@
.\" $NetBSD: compat_ultrix.8,v 1.17 2003/03/30 21:03:45 wiz Exp $
.\" $NetBSD: compat_ultrix.8,v 1.18 2003/03/30 21:21:41 wiz Exp $
.\"
.\" Copyright (c) 1997 Jonathan Stone
.\" All rights reserved.
@ -35,7 +35,7 @@
.Os
.Sh NAME
.Nm compat_ultrix
.Nd "setup procedure for Ultrix compatibility on mips and VAX architectures"
.Nd "setup procedure for ULTRIX compatibility on mips and VAX architectures"
.Sh DESCRIPTION
.Nx Ns Tn /mips
and
@ -46,18 +46,18 @@ the legal issues of ensuring that you have a right to use any ULTRIX
binaries on your machine.
.Pp
Most executables will work. The exceptions include programs that use
proprietary, Ultrix-specific features (LAT, CI support, DECnet
proprietary, ULTRIX-specific features (LAT, CI support, DECnet
support) and various system calls,
.Fn ioctl Ns 's ,
or Ultrix kernel
semantics that are difficult to emulate (e.g. Ultrix packetfilter) or
buggy (e.g. Ultrix
or ULTRIX kernel
semantics that are difficult to emulate (e.g. ULTRIX packetfilter) or
buggy (e.g. ULTRIX
.Tn NIS ) .
.Pp
All Ultrix executables are static, so no shared libraries are required
for Ultrix compatibility. However, Ultrix is based on a
All ULTRIX executables are static, so no shared libraries are required
for ULTRIX compatibility. However, ULTRIX is based on a
.Bx 4.3
alpha release. Ultrix commands and libraries are often much older
alpha release. ULTRIX commands and libraries are often much older
than their
.Nx
or even
@ -81,7 +81,7 @@ as below:
.It # cp -p /usr/share/examples/emul/ultrix/etc/* ./
.El
.Ss /etc/resolv.conf
The Ultrix resolver library only understands
The ULTRIX resolver library only understands
.Sy domain
and
.Sy nameserver
@ -92,10 +92,10 @@ You should create a copy of
containing only those commands and put it in
.Pa /emul/ultrix/etc/resolv.conf .
Note that the
domain search order used by Ultrix executables may not be the same as
domain search order used by ULTRIX executables may not be the same as
native binaries; there is no good way around this.
.Ss /etc/svc.conf
Ultrix uses
ULTRIX uses
.Pa /etc/svc.conf
to select an ordered search of
.Tn NIS ,
@ -103,15 +103,15 @@ Hesiod,
or local flat-file mappings. You should create an
.Pa /emul/ultrix/etc/svc.conf
specifying either local files or bind (DNS)
lookups for all Ultrix name services.
lookups for all ULTRIX name services.
.Sh SEE ALSO
.Xr resolv.conf 5
.Sh BUGS
RISC Ultrix
RISC ULTRIX
.Tn NIS
(YP) is known to not work. The Ultrix
(YP) is known to not work. The ULTRIX
.Tn NIS
libraries have a consistent endian-ness bug. Ultrix
libraries have a consistent endian-ness bug. ULTRIX
.Tn NIS
client will not inter-operate with the
.Nx
@ -122,19 +122,19 @@ to disable
.Tn NIS
(YP).
.Pp
The ndbm hashed-password file used by Ultrix are incompatible with the
The ndbm hashed-password file used by ULTRIX are incompatible with the
db hashed-password file used by
.Nx .
There is no good solution for
this.
.Tn NIS
would be a good one, if Ultrix
would be a good one, if ULTRIX
.Tn NIS
worked.
.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
with ULTRIX 4.1. An implementation of the ULTRIX 4.2 Xws interface
(used by X11R6) is in progress.
.Pp
A complete list of things which fail to work in Ultrix compatibility
A complete list of things which fail to work in ULTRIX compatibility
mode should be added here.

4
usr.sbin/pppd/pppd/pppd.8
View File

@ -1,4 +1,4 @@
.\" $NetBSD: pppd.8,v 1.37 2003/03/15 19:24:02 wiz Exp $
.\" $NetBSD: pppd.8,v 1.38 2003/03/30 21:23:44 wiz Exp $
.\"
.\" manual page [] for pppd 2.4
.\" Id: pppd.8,v 1.57 2001/03/12 22:49:25 paulus Exp
@ -597,7 +597,7 @@ option, pppd will wait for the CD (Carrier Detect) signal from the
modem to be asserted when opening the serial device (unless a connect
script is specified), and it will drop the DTR (Data Terminal Ready)
signal briefly when the connection is terminated and before executing
the connect script. On Ultrix, this option implies hardware flow
the connect script. On ULTRIX, this option implies hardware flow
control, as for the \fIcrtscts\fR option.
.TP
.B mp

4
usr.sbin/traceroute/traceroute.8
View File

@ -1,4 +1,4 @@
.\" $NetBSD: traceroute.8,v 1.19 2003/02/04 23:07:38 perry Exp $
.\" $NetBSD: traceroute.8,v 1.20 2003/03/30 21:23:43 wiz Exp $
.\"
.\" Copyright (c) 1989, 1995, 1996, 1997
.\" The Regents of the University of California. All rights reserved.
@ -335,7 +335,7 @@ ICMP's) until we probe with a ttl that's at least twice the path
length. I.e., rip is really only 7 hops away. A reply that
returns with a ttl of 1 is a clue this problem exists.
Traceroute prints a "!" after the time if the ttl is \*[Le] 1.
Since vendors ship a lot of obsolete (DEC's Ultrix, Sun 3.x) or
Since vendors ship a lot of obsolete (DEC's ULTRIX, Sun 3.x) or
non-standard (HPUX) software, expect to see this problem
frequently and/or take care picking the target host of your
probes.