ULTRIX 4: Unterschied zwischen den Versionen
|Zeile 533:||Zeile 533:|
'''Installing ULTRIX 4.
'''Installing ULTRIX 4.on a MicroVAX 3100:'''
[[Datei:Microvax3100.jpg |thumb|right|MicroVAX 3100]]
[[Datei:Microvax3100.jpg |thumb|right|MicroVAX 3100]]
Aktuelle Version vom 3. April 2019, 02:01 Uhr
DEC released ULTRIX for the DECstation with release 3 in 1989. ULTRIX 4.0 already came in 1990 and quickly most DECstation and VAX machines were running some release of 4.X. When people think of ULTRIX, they usually remember some 4.X release. ULTRIX 4 is based on 4.2BSD + some 4.3BSD + some System V. ULTRIX never received some modern features like shared libraries. Early 4.X releases sometimes had nasty bugs and people kept upgrading until it was stable. The last release was 4.5, released in 1995, but only few sites actually ran it. DECstations weren't really important by 1995 and there was little to be gained over 4.4 or 4.3A. ULTRIX comes with a full development system, TCP/IP, NFS, and so on. ULTRIX/RISC ships with a port of the MIPS C-Compiler. ULTRIX/VAX has the older VAX C compiler. In general, ULTRIX releases become better over times as bugs get fixed by newer releases. Unless you are into serious retro-computing or have many machines and want some diversity, ULTRIX 4.5 is the version to go for. Compaq has released a Y2K patch kit for the last ULTRIX releases, which is also nice to have. The ULTRIX 4.5 release of this patch kit fixes several other bugs, patches the libc, and so on.
There are two potential X11 environments for ULTRIX: DECwindows/XUI and DECwindows/Motif. Motif is much bigger and slower. If you have a slow machine like a VAXstation or a DECstation 3100, you may want to keep XUI and avoid Motif. Later ULTRIX releases offer a choice of desktops during installation. You can't have both installed at the same time. On the other hand, you might want to replace it all with a generic installation of X11R5 or even newer.
ULTRIX got the ability to use and install on generic SCSI disks with 4.2. There was a bug in the disk driver that corrupts data on disks larger than 1GB on ULTRIX release 4.2 and earlier. A fix was introduced in 4.2A. If you have an ULTRIX release that can handle large disks, you are only limited by a maximum filesystem size of 2GB. ULTRIX has classic BSD disklabels and counts filesystems from "a" to "h". Filesystems can be up to 2GB in size. You can use larger disks with multiple GB if you partition the disk carefully.
ULTRIX/RISC 4.5 supports all DECstations and DECsystems from the earliest 3100 to the latest 5000/260. R4000 based machines need 4.3A or newer. ULTRIX/VAX runs on all VAX machines up to the CVAX range, including the popular first generation MicroVAX 3100 and VAXstation 3100. ULTRIX supports SMP on the large DECsystem 5800 and VAX 6000. ULTRIX/VAX does not run on any more modern VAX, like the VAXstation 4000 series. To bring some perspective: The first DECstation, the DS3100, was released at the time as the VAXstation 3100. The DECstation 3100 delivers about 12 MIPS, while the VAXstation 3100 brings about 3 MIPS. It was obvious already in 1989 and people did not buy VAXstations as ULTRIX machines in large numbers. The fastest small VAX supported is the VAXstation 3100/38, which will get you something between 3 to 4 MIPS. So in the end, every DECstation is a lot faster than a VAX running ULTRIX.
ULTRIX 4 requires license PAKs ("Product Activation Key") like all the other DEC operating systems. A two-user system will boot up fine without any licenses installed. Having more than two users and using layered products needs extra licenses.
When you look for ULTRIX, you should also search for the "software product library" or "layered product software".
Installing ULTRIX on a DECstation
Get the CDs ready: ULTRIX 4.5 installation CD. ULTRIX software product library CDs ULTRIX consolidated software distribution
if ($term == xterm-256color) then setenv TERM vt100 endif
# set a fancy prompt PS1='\u@\h:\w\$ ' export PS1
if [ $TERM = "xterm-256color" ] then TERM=vt100; export TERM fi
install ULTRIX 4.5
boot ULTRIX installation media. choose single user shell partition disk with chpt
show partition table
chpt -q /dev/rrz0c
create default table
chpt -d /dev/rrz0c
chpt -pa 0 65536 /dev/rrz0c
choose advanced installation select everything
load license PAKs lmf reg <template>
load layered products DECnet, Fortran, C++, Pascal, disk shadowing
build kernel for DECnet /usr/etc/decnetsetup kernel
DEC released a Y2K patchset for ULTRIX 4.3A and later:
load patchsets Base and UWS
setenv PATCHES /path/to/patch/dir
run patch scripts like:
for i in `ls U*`; do ./$i ; done
configure TCP/IP network:
ULTRIX /bin/sh is an ancient Bourne shell. It is best to replace it:
mv /bin/sh /bin/sh.save cp -p /usr/bin/ksh /bin/sh
if bash is build copy /usr/local/bin/bash to /bin/sh
interesting things and tools:
diskless management services utility
remote installation services
MIPS RISC C compiler
DEC ANSI C compiler
DEC C++ compiler
DEC Fortran compiler
MIPS Pascal compiler
get gcc-2.95.3 get [] libIO patch copy patch to libio dir apply patch like: /usr/local/bin/patch < libio_patch.txt build gcc-2.95.3 as usual
build without C++
needs [] libIO patch. needs fixes for libstdc++ config.h.in: add "#define LITTLE_ENDIAN 1" comment or undef "#define HAVE_IEEEFP_H 1" the ieeefp.h fix might only be applieable for config.h when the build has failed.
I chose to build with gcc. You need to change the CFLAGS in hints/ultrix_4.sh choose "none" for shared libraries, because ULTRIX doesn't have SL. set LANG or LC_ALL to "C"
take install-sh out of gawk-3.1.8 and install it as /usr/local/bin/install
If the program you are trying to build complains about that there is no symbol strdup to link to, then add the library “libiberty” (found in for example GNU binutils package) i.e. add the switch –liberty when you link.
copy snprintf.h to /usr/local/include
include snprintf.h in lib/argp-fmtstream.c add -libiberty when linking tar
top-3.5: don't include color support
assumes libintl, and failes, because "undefined reference to `libintl_fprintf'" add "-lintl" undefined reference to `mkstemp' include <mkstemp.h>
needs strdup() add -liberty
needs an #include <snprintf.h> in pngrutil.c.
--disable-shared note: readline uses terminal lib functions, such as tputs, but doesn't link to any such library. This means that apps using readline also need to link to libtermcap, libcurses or libncurses. Remember when you see "undefined reference to `tputs'".
screen-3.9.15: needs #include <sys/syslog.h> in acls.c
if you link pcre with readline remember to also link to libncurses or similar.
some tests failed
add SM and ICE to XLIBS in Makefile if you use X11R6. Not necessary with X11R5.
check that xpm.h gets installed
problems with libtool. remove -version_info
remove #include sys/socket.h from prngd.c, serverloop.c, unix_socket.c, tcp_socket.c, sockio.c,
make install doesn't work, because it assumes shared libs
words just fine out of the box.
remove sys/socket.h and netinet/ip.h from several files when "includes.h" is included.
#define BROKEN_READV_COMPARISON #undef HAVE_TYPE_IN_UTMP #define DISABLE_UTMPX #undef ENABLE_PKCS11
running sshd in debug mode: /bin/sshd -p <listening port> -D -d -e
ssh-keygen.c remove references to pkcs11_init and pkcs11_terminate from ssh-keygen.c on lines 1410 and 1493.
#define ssize_t size_t in lib/nfkc.c EILSEQ undefined in gltests/test-errno.c lstat undefined in gltests/test-lstat.c no solution yet installed without testing, but looks okay
strdup undefined. needs -liberty in lib add "LIBS = -liberty" to src/Makefile "#define ssize_t size_t" in lib/stringprep.h
some problems with Xsetlocale for unknown reasons. I think this used to just work. "#define _Xsetlocale setlocale" in gtk/gtkrc.c and gdk/gdkim.c
comment out #include setlocale.h in lib/system.h
remove #include sys/socket.h from src/host.h add #include sys/socket.h in ftp.c ftp-ls.c headers.c http.c main.c rbuf.c recur.c retr.c add -lintl to src/Makefile under LIBS
./Configure zlib --prefix=/usr/local --openssldir=/usr/local ultrix-gcc temporally create a link /usr/local as /usr/local/ssl then rebuild some apps that rely on openssl.
follow the instructions for building outside the source tree
vec.sv_flags = (SV_ONSTACK #ifdef SV_RESETHAND | SV_RESETHAND #endif );
some tests fail with doc/m4.texinfo. This is known.
RIS - remote installation service
ULTRIX provides ris, as a way to install from the network. It is easy to setup by scripts.
A common failure is this:
Cannot find rzux1 in risdb file. Check the sytem manager of your host server.
If this happens, make sure:
the client is in the /etc/hosts of the server the r services have to be enabled in /etc/inetd.conf on the server /usr/adm/ris/.rhosts should include the client /usr/adm/ris/clients/risdb should include the client
/etc/hosts should be beautiful like this:
192.168.2.123 ds3100 ds3100.domain.tld
but NOT like this:
192.168.2.123 ds3100.domain.tld ds3100
ULTRIX 4.1 contains a floating point signalling bug. a patch is supplied with and needed for DEC Fortran.
ULTRIX 4.1 on RISC is also full of bugs. It is really best to avoid that version.
ULTRIX 4.1 partition for DECstation 3100:
make sure there is enough swap space!
ULTRIX can only swap on partations that are configured in the kernel.
config vmunix root on rz0a swap on rz0b and rz0e dumps on rz0b
/dev/rz0a:/:rw:1:1:ufs:: /dev/rz0d:/var:rw:1:2:ufs:: /dev/rz1a:/usr:rw:1:2:ufs:: /dev/rz0f:/home:rw:1:2:ufs:: /dev/rz0e::sw:::::
bash-2.05b# chpt -q /dev/rrz0a /dev/rrz0a Current partition table: partition bottom top size overlap a 0 131071 131072 c,g,h / b 131072 327679 196608 c swap1 c 0 832526 832527 a,b,d,e,f,g,h d 327680 393215 65536 c /var e 589824 832526 242703 c swap2 f 393216 589823 196608 c /home g 0 0 0 a,c,h h 0 0 0 a,c,g bash-2.05b# chpt -q /dev/rrz1a /dev/rrz1a Current partition table: partition bottom top size overlap a 0 2050859 2050860 b,c,d,e,f,g,h /usr b 0 0 0 a,c,d,e,f,g,h c 0 2050859 2050860 a,b,d,e,f,g,h d 0 0 0 a,b,c,e,f,g,h e 0 0 0 a,b,c,d,f,g,h f 0 0 0 a,b,c,d,e,g,h g 0 0 0 a,b,c,d,e,f,h h 0 0 0 a,b,c,d,e,f,g
important note: the ULTRIX kernel cannot be built with any GNU tools in the path
installing ULTRIX 4.0 RISC
some save sets were unreadable from the distribution tapes. unable to install X11 UDTEXER
ULTRIX 4.0 does not remember the correct ethernet device. Installation assumes that ln0 is correct. Drop to system shell and /etc/ifconfig ln1.
Install software from a remote server using setld:
/etc/setld -l dxsoft:
the colon is necessary!
set default gateway and start services: add to /etc/rc.local:
# prngd echo 'starting pseudo random number generator' > /dev/console /usr/local/sbin/prngd /var/run/egd-pool
# SSHd echo 'starting SSH daemon' > /dev/console /usr/local/sbin/sshd
# default route echo 'setting default route' > /dev/console /etc/route add default 192.168.2.253 1
# start DECnet # %OSIAPPLSTART% # # Start all OSI applications # if [ -s /etc/osi_applstartup ] then echo "OSI Applications Starting" ; /bin/sh5 /etc/osi_applstartup fi # %OSIAPPLEND%
Installing ULTRIX 4.5 on a MicroVAX 3100:
add secure to all ttys
replace /bin/sh with bash
cp install-sh /usr/local/bin/install from gawk-3.0.6
use libIO patch