This document is probably only of historical value, because Ultrix version 4 dates from the early 1990s.
One of the bugs of Ultrix's /bin/sh is that shell-variables set in arguments of `:' expand to garbage if expanded in here-documents.
Ultrix's FD_SET_SIZE is 4096, but getdtablesize() returns 64 by default, if not increased when building a new kernel.
www.postfix.org /ULTRIX_README.html (273 words)
Ultrix(Site not responding. Last check: )
These features make ULTRIX the leader in the field of vertical, multipurpose machining centers for high-speed machining.The proprietary Metalquartz structure assures better perforance in every kind of machining, over machines fabricated completely of steel or cast iron, and as well as over those with a bed completely from agglomerate.
All the high-frequency spindles, are thermally stabilized by an electric refrigerator to guarantee maximum precision of the machining process both the coolant (at high and low pressure) and the air to clean the cone pass inside the spindle.
ULTRIX 800RT, designed by Breton, has been expressly designed both vertical and horizontal turning in addition to traditional milling operations.
Ultrix 4.2, as well as some of Digital's Ethernet interface hardware, is strict about checking 802.3 header, and does not accept these packets.) As of this writing, a patch is not yet available and there is no workaround.
ULTRIX releases prior to V4.2A are unable to handle logical block numbers greater than (2**21 - 1).
If you are running Ultrix 4.2, you don't need to edit ultrix.cf, but for other versions of Ultrix, be sure to cd to mit/config and change the OSMinorVersion (and, for versions of Ultrix prior to 4.0, the OSMajorVersion) number to the appropriate number for your version of Ultrix.
The /big/ problem here is that ULTRIX is no longer mainained by any group of developers so this bug will most probably stay around for quite some time, On the other hand I also heard from the same list that there is an NYC based company that is realy developing ULTRIX[1].
I think the problem is question is more likely to be "Ultrix can crash when fed TCP packets containing RFC1323/SACK TCP options as specified in the RFC's" which did not exist at the time the Ultrix networking code was written.
However the RFC's which were present at the time of the writing of the Ultrix networking code, say to ignore TCP options which one does not understand.
Ultrix commands and libraries are often much older than their OpenBSD or even SunOS 4.x equivalents, and may require incompatible con- figuration files.
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.
An implementation of the Ultrix 4.2 Xws interface (used by X11R6) is in progress.
2.1.99 sends ULTRIX death packet(Site not responding. Last check: )
The /big/ problem here is that ULTRIX is no longer mainained by any group of developers so this bug will most probably stay around for quite some time, On the other hand I also heard from the same list that there is an NYC based company that is realy developing ULTRIX[1].
I think the problem is question is more likely to be "Ultrix can crash when fed TCP packets containing RFC1323/SACK TCP options as specified in the RFC's" which did not exist at the time the Ultrix networking code was written.
However the RFC's which were present at the time of the writing of the Ultrix networking code, say to ignore TCP options which one does not understand.
However, BSD and Ultrix put their labels in completely different locations on the disk, so they can coexist.) First you need to decide on how you are going to partition your disk and create a disktab(5) entry for it.
Ultrix keeps its label in the superblock, so chpt won't work unless there is a filesystem on partition a or c already.
Ultrix filesystems are exactly the same as 4.3BSD ones, so initially your new BSD filesystems will be 4.2/4.3 vintage, since they have been created under Ultrix.
Unless otherwise specified, these answers refer to ULTRIX 4.2, which is the current release of ULTRIX.
A version of the 4.3BSD syslog library and daemon that detects either 4.2bsd-compatible clients (which is what the Ultrix libc.a will help you create) or 4.3bsd-compatible clients, which are more flexible, is available by anonymous FTP from gatekeeper.dec.com in /pub/DEC/jtkohl-syslog.shar.
To build an R5 server on ULTRIX 4.1 system, edit the Edit the file ultrix.cf in mit/config and #define OSMinorVersion to be 1.
By checking certain fields in the ICMP echo packet received from a host, it is possible to determine whether the server is a Windows 2000, Ultrix, FreeBSD, and more.
This enables attackers to perform easy host fingerprinting and discover what type of operating system is installed.
To determine if your ULTRIX host running DECnet/ULTRIX is currently vulnerable, execute the command: /usr/bin/ncp show exec char Note: if your system doesn't have the file /usr/bin/ncp, it does not have DECnet/ULTRIX installed.
To protect ULTRIX V4.0, V4.1, and V4.2 systems, DEC has provided the following workaround: Edit /etc/passwd to specify "/bin/false" in the shell field of the "guest" account.
CIAC and DEC recommend this workaround be applied to all ULTRIX V4.0, V4.1, and V4.2 machines running DECnet/ULTRIX, even those with the gateway functionality disabled, as a prudent precaution.
Ultrix version 4.5 is vulnerable to a buffer overflow in the dxterm utility.
A local attacker could use this vulnerability to overflow a buffer and execute arbitrary code on the system or possibly cause a denial of service.
CVE-2004-1326: Buffer overflow in dxterm in Ultrix 4.5 allows local users to execute arbitrary code via a long -setup parameter.
xforce.iss.net /xforce/xfdb/18613 (253 words)
Differences in ULTRIX and Tru64 UNIX Header Files and Library Routines(Site not responding. Last check: )
Some ULTRIX functions are not defined on Tru64 UNIX systems; others have different parameters or return values.
ULTRIX and Tru64 UNIX systems have different implementations of some of the processing options that are extensions to the POSIX and X/Open standards, as shown in the following table:
Several header files that are part of the ULTRIX system are not included in the Tru64 UNIX system.
WorkMan was ported to ULTRIX by Chris Ross (cross@eng.umd.edu).
You will need to use "imake" to build a Makefile suitable for ULTRIX; the supplied Makefile is tuned for Suns (though it isn't hard to adjust if you prefer not to use imake).
For those who'd like to read through the source, note that the ULTRIX- specific code is all contained in plat_ultrix.c.
As well as the CERT advisory, this came in the post from DEC. DEC don't support versions of Ultrix prior to 4.3, so I guess you'll just have to move with the times and upgrade if you want to ping-proof your systems.
Digital has discovered that this isn't strictly true; ULTRIX can in fact be crashed by a variant of the ping attack under certain circumstances.
To be safe, Digital has prepared patches for versions 4.3 through 4.5 of ULTRIX.