1DISPLAYS(5) File Formats Manual DISPLAYS(5)
2
3
4
6 displays - Display Configuration File
7
9 The interactive graphics programs Caesar, Magic, and Gremlin use two
10 separate terminals: a text terminal from which commands are issued, and
11 a color graphics terminal on which graphical output is displayed.
12 These programs use a displays file to associate their text terminal
13 with its corresponding display device.
14
15 The displays file is an ASCII text file with one line for each text
16 terminal/graphics terminal pair. Each line contains 4 items separated
17 by spaces: the name of the port attached to a text terminal, the name
18 of the port attached to the associated graphics terminal, the phosphor
19 type of the graphics terminal's monitor, and the type of graphics ter‐
20 minal.
21
22 An applications program may use the phosphor type to select a color map
23 tuned to the monitor's characteristics. Only the std phosphor type is
24 supported at UC Berkeley.
25
26 The graphics terminal type specifies the device driver a program should
27 use when communicating with its graphics terminal. Magic supports
28 types UCB512, AED1024, and SUN120. Other programs may recognize dif‐
29 ferent display types. See the manual entry for your specific applica‐
30 tion for more information.
31
32 A sample displays file is:
33
34 /dev/ttyi1 /dev/ttyi0 std UCB512
35 /dev/ttyj0 /dev/ttyj1 std UCB512
36 /dev/ttyjf /dev/ttyhf std UCB512
37 /dev/ttyhb /dev/ttyhc std UCB512
38 /dev/ttyhc /dev/ttyhb std UCB512 ®
39
40 In this example, /dev/ttyi1 connects to a text terminal. An associated
41 UCB512 graphics terminal with standard phosphor is connected to
42 /dev/ttyi0.
43
44
46 Magic uses the displays file ~cad/lib/displays. Gremlin looks in
47 /usr/local/displays.
48
49
51 magic(1)
52
53
54
553rd Berkeley Distribution 2/19/85 DISPLAYS(5)