|
|
1.1 root 1: .\" $Header: Xsun.man,v 1.1 87/09/14 14:50:44 toddb Exp $
2: .TH XSUN 8 "9 Sep 1987" "X Version 11"
3: .SH NAME
4: Xsun \- Sun server for X Version 11
5: .SH SYNOPSIS
6: .B Xsun
7: [ option ] ...
8: .SH DESCRIPTION
9: .I Xsun
10: is the server for Version 11 of the X window system on Sun hardware.
11: It will normally be started by
12: .IR xinit (1),
13: or perhaps by some script such as:
14: .LP
15: .nf
16: .ta 0.5i 1i 1.5i
17: #!/bin/sh
18: home=/disk1d/x11
19:
20: case "$1" in
21: "") X=$home/Bin/X;;
22: /*) X=$1;;
23: *) X=`pwd`/$1;;
24: esac
25:
26: clear
27: xinit -- $X -fp $home/Lib/fonts -co $home/Lib/rgb
28: kbd_mode -a
29: .fi
30: .PP
31: .SH
32: CONFIGURATIONS
33: .PP
34: .I Xsun
35: operates under SunOS versions 3.2, 3.4, and 4.0, on Sun/2, Sun/3
36: and Sun/4 architectures.
37: It normally auto-configures to use all available displays; it supports
38: the following display types:
39: .TP
40: \fBbwtwo\fP
41: in both 1152*900 and 1600*1280 versions.
42: .TP
43: \fBcgtwo\fP
44: used both as a color and a monochrome display (for X/160C).
45: .TP
46: \fBcgfour\fP
47: used both as a color and a monochrome display (for 3/110 & 3/60).
48: .PP
49: It does not support the GP, GP+, or GP2. If you have one of these
50: installed, use the
51: .B -dev
52: argument to select
53: .IR /dev/cgtwo0 .
54: .PP
55: On a
56: .BR cgfour ,
57: .I Xsun
58: will use both the monochrome and color screens as if they were
59: two separate screens side-by-side. Sliding the mouse off the left and right
60: edges will swap screens.
61: .SH "USE WITH SUNWINDOWS OR NeWS"
62: .PP
63: The server can be run from outside
64: .BR suntools ,
65: in which case it configures for all available displays (unless overridden
66: by
67: .B -dev
68: options).
69: Otherwise, it can be run ``on top of'' either
70: .B suntools
71: or
72: .BR NeWS .
73: In this case, it takes over the entire screen it was invoked from.
74: .PP
75: If you have multiple displays, you can run
76: .B suntools
77: on both, use
78: .B adjacentscreens
79: to move the mouse between them,
80: and then run
81: .I Xsun
82: on top of one of the desktops.
83: .B Adjacentscreens
84: will still be in effect, so you can move between window systems
85: by sliding the mouse from one screen to another.
86: .SH OPTIONS
87: .TP
88: \fB-mono\fP
89: means use a \fBcgtwo\fP, if present, as a monochrome device. Default is use it as
90: a color device.
91: Using it as a monochrome device is, for the present, mush faster.
92: .TP
93: \fB-debug\fP
94: means that the server is being run from a debugger,
95: such as
96: .IR dbx (1),
97: and that it should
98: .I not
99: set its standard input, output and error files into non-blocking mode.
100: .TP
101: \fB-dev\fP
102: takes the following arument as the name of the special file for
103: a display device. If any
104: .B -dev
105: arguments are supplied, they are used.
106: The server does not auto-configure in this case.
107: .PP
108: Other options are described under
109: .IR X (8).
110: .SH ENVIRONMENT
111: .TP
112: \fBXDEVICE\fP
113: If present, and if no explicit
114: .B -dev
115: options are given, specifies the (colon separated) list of display devices
116: to use.
117: .TP
118: \fBWINDOW_PARENT\fP
119: If present, specifies the
120: .I /dev/win
121: file of the
122: .B suntools
123: desktop.
124: .SH "SEE ALSO"
125: .PP
126: .IR X (8),
127: .IR xinit (1),
128: .IR "Godzilla's Guide to Porting the X.11 Sample Server".
129: .SH BUGS
130: .TP
131: 1
132: If the server crashes, it may leave the keyboard in a non-useful state.
133: The script above uses the
134: .I kbd_mode
135: command (found in the
136: .I server/ddx/sun
137: directory) to repair the damage.
138: .TP
139: 2
140: The server code is completely untuned, and has inferior performance.
141: In particular, the color code is very slow (but it is very portable).
142: .TP
143: 3
144: The auto-configuration depends on there being appropriate
145: special files in the
146: .I /dev
147: directory for the framebuffers which are to be used. Spurious
148: entries can disturb
149: the process.
150: For example, the X/160C in fact has the hardware for a monochrome
151: .B bwtwo0
152: on the CPU board. So if your
153: .I /dev
154: has a special file for
155: .IR /dev/bwtwo0 ,
156: the server will use it, even though there is no monitor attached to the
157: monochrome framebuffer.
158: The server will appear to start, but not to paint a cursor, because the
159: cursor is on the monochrome frame buffer. The solution is to remove the
160: .I /dev
161: entries for any device you don't have a monitor for.
162: .TP
163: 4
164: There is a bug which causes the server to crash driving a
165: .B cgtwo
166: from a Sun/4.
167: .TP
168: 5
169: There is a race condition that sometimes happens when running
170: ``on top of'' NeWS. The symptom is that parts of NeWS show through,
171: and that the keyboard is in a non-useful state. There is no
172: simple work-around.
173: .TP
174: 6
175: Autorepeat for the keyboard cannot be turned off.
176: .TP
177: 7
178: The bell is not implemented yet.
179: .TP
180: 8
181: Use of the pattern (as opposed to the blanking) screensaver
182: may cause the server to loop forever.
183: .TP
184: 9
185: The cursor colors are correct. If you are sceptical, try running
186: .IR hacks/cursorcolor/cursorcolor .
187: .SH AUTHORS
188: .TP
189: U. C. Berkeley
190: Adam de Boor.
191: .TP
192: Sun Microsystems
193: David Rosenthal, Stuart Marks, Robin Schaufler, Mike Schwartz,
194: Frances Ho, Geoff Lee, and Mark Opperman.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.