|
|
1.1 root 1: .NH
2: Installation Under Ultrix-32 1.1
3: .PP
4: The name of the executable built in the "X" directory for QVSS is
5: Xqvss.
6: Note that some of the files mentioned here are only available on the
7: MIT distribution of X.
8: .PP
9: We recommend upgrading to Ultrix-32 1.2 as soon as possible.
10: When you do, be sure to rebuild \fIXqvss\fP and \fIxterm\fP.
11: .PP
12: If you need to relocate the font directory,
13: edit the file \fIlibqvss/vssite.h\fP, recompile \fIlibqvss/ddxfontloc\fP,
14: and replace the file into \fIlibqvss/libqvss.a\fP using \fIar(1)\fP.
15: .PP
16: Note that the \fIXqvss\fP server and the \fIxterm\fP
17: executable should be recomiled
18: when you upgrade to 1.2.
19: A server built under 1.1 will not execute under field test two of Ultrix-32 1.2
20: or under version 1.2 release due to a system call
21: change.
22: .PP
23: The improved pty driver has already been installed, but the TCP problem
24: is still with you.
25: X will be slightly unreliable when pushed hard until you upgrade to Ultrix
26: 1.2 when using the TCP domain on the local host.
27: Everything should run reliably if you run using the Unix domain.
28: (use a DISPLAY variable of \fIunix:0\fP).
29: The file provided should be added to your \fIBINARY.mvax\fP directory, and
30: your kernel rebuilt.
31: This will change the keyboard handling in the
32: shared event queue of the QVSS driver to match what this version of X requires.
33: .PP
34: In addition, the file \fIsys/vaxuba/qevent.h\fP should replace the file of that
35: name in \fI/usr/include/vaxuba\fP.
36: This file avoids the redefinition problems you would encounter with the
37: original.
38: The bit-blit code is not available in source. There is an object
39: library \fIX/libqvss/libqvss.a\fP containing the object of the device dependent
40: library.
41: Note that you should not just \fIrcp(1)\fP the distribution tree, as there
42: are symbolic links in the tree.
43: If you have, you may need to \fIranlib(1)\fP the QVSS object library.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.