Imported Upstream version 1.15.1
[deb_xorg-server.git] / man / Xserver.man
CommitLineData
a09e091a
JB
1.\" $Xorg: Xserver.man,v 1.4 2001/02/09 02:04:07 xorgcvs Exp $
2.\" $XdotOrg: xserver/xorg/doc/Xserver.man.pre,v 1.4 2005/12/23 20:11:12 alanc Exp $
3.\" Copyright 1984 - 1991, 1993, 1994, 1998 The Open Group
4.\"
5.\" Permission to use, copy, modify, distribute, and sell this software and its
6.\" documentation for any purpose is hereby granted without fee, provided that
7.\" the above copyright notice appear in all copies and that both that
8.\" copyright notice and this permission notice appear in supporting
9.\" documentation.
10.\"
11.\" The above copyright notice and this permission notice shall be included
12.\" in all copies or substantial portions of the Software.
13.\"
14.\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
15.\" OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
16.\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
17.\" IN NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY CLAIM, DAMAGES OR
18.\" OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
19.\" ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
20.\" OTHER DEALINGS IN THE SOFTWARE.
21.\"
22.\" Except as contained in this notice, the name of The Open Group shall
23.\" not be used in advertising or otherwise to promote the sale, use or
24.\" other dealings in this Software without prior written authorization
25.\" from The Open Group.
26.\" $XFree86: xc/programs/Xserver/Xserver.man,v 3.31 2004/01/10 22:27:46 dawes Exp $
27.\" shorthand for double quote that works everywhere.
28.ds q \N'34'
29.TH XSERVER 1 __xorgversion__
30.SH NAME
31Xserver \- X Window System display server
32.SH SYNOPSIS
33.B X
34[option ...]
35.SH DESCRIPTION
36.I X
37is the generic name for the X Window System display server. It is
38frequently a link or a copy of the appropriate server binary for
39driving the most frequently used server on a given machine.
40.SH "STARTING THE SERVER"
41The X server is usually started from the X Display Manager program
42\fIxdm\fP(1) or a similar display manager program.
43This utility is run from the system boot files and takes care of keeping
44the server running, prompting for usernames and passwords, and starting up
45the user sessions.
46.PP
47Installations that run more than one window system may need to use the
48\fIxinit\fP(1) utility instead of a display manager. However, \fIxinit\fP is
49to be considered a tool for building startup scripts and is not
50intended for use by end users. Site administrators are \fBstrongly\fP
51urged to use a display manager, or build other interfaces for novice users.
52.PP
53The X server may also be started directly by the user, though this
54method is usually reserved for testing and is not recommended for
55normal operation. On some platforms, the user must have special
56permission to start the X server, often because access to certain
57devices (e.g. \fI/dev/mouse\fP) is restricted.
58.PP
59When the X server starts up, it typically takes over the display. If
60you are running on a workstation whose console is the display, you may
61not be able to log into the console while the server is running.
62.SH OPTIONS
63Many X servers have device-specific command line options. See the manual
64pages for the individual servers for more details; a list of
65server-specific manual pages is provided in the SEE ALSO section below.
66.PP
67All of the X servers accept the command line options described below.
68Some X servers may have alternative ways of providing the parameters
69described here, but the values provided via the command line options
70should override values specified via other mechanisms.
71.TP 8
72.B :\fIdisplaynumber\fP
73The X server runs as the given \fIdisplaynumber\fP, which by default is 0.
74If multiple X servers are to run simultaneously on a host, each must have
75a unique display number. See the DISPLAY
76NAMES section of the \fIX\fP(__miscmansuffix__) manual page to learn how to
77specify which display number clients should try to use.
78.TP 8
79.B \-a \fInumber\fP
80sets pointer acceleration (i.e. the ratio of how much is reported to how much
81the user actually moved the pointer).
82.TP 8
83.B \-ac
84disables host-based access control mechanisms. Enables access by any host,
85and permits any host to modify the access control list.
86Use with extreme caution.
87This option exists primarily for running test suites remotely.
88.TP 8
89.B \-audit \fIlevel\fP
90sets the audit trail level. The default level is 1, meaning only connection
91rejections are reported. Level 2 additionally reports all successful
92connections and disconnects. Level 4 enables messages from the
93SECURITY extension, if present, including generation and revocation of
94authorizations and violations of the security policy.
95Level 0 turns off the audit trail.
96Audit lines are sent as standard error output.
97.TP 8
98.B \-auth \fIauthorization-file\fP
99specifies a file which contains a collection of authorization records used
100to authenticate access. See also the \fIxdm\fP(1) and
101\fIXsecurity\fP(__miscmansuffix__) manual pages.
102.TP 8
103.BI \-background\ none
104Asks the driver not to clear the background on startup, if the driver supports that.
105May be useful for smooth transition with eg. fbdev driver.
106For security reasons this is not the default as the screen contents might
107show a previous user session.
108.TP 8
109.B \-br
110sets the default root window to solid black instead of the standard root weave
111pattern. This is the default unless -retro or -wr is specified.
112.TP 8
113.B \-bs
114disables backing store support on all screens.
115.TP 8
116.B \-c
117turns off key-click.
118.TP 8
119.B c \fIvolume\fP
120sets key-click volume (allowable range: 0-100).
121.TP 8
122.B \-cc \fIclass\fP
123sets the visual class for the root window of color screens.
124The class numbers are as specified in the X protocol.
125Not obeyed by all servers.
126.TP 8
127.B \-core
128causes the server to generate a core dump on fatal errors.
129.TP 8
130.B \-displayfd \fIfd\fP
131specifies a file descriptor in the launching process. Rather than specify
132a display number, the X server will attempt to listen on successively higher
133display numbers, and upon finding a free one, will write the display number back
134on this file descriptor as a newline-terminated string. The \-pn option is
135ignored when using \-displayfd.
136.TP 8
137.B \-deferglyphs \fIwhichfonts\fP
138specifies the types of fonts for which the server should attempt to use
139deferred glyph loading. \fIwhichfonts\fP can be all (all fonts),
140none (no fonts), or 16 (16 bit fonts only).
141.TP 8
142.B \-dpi \fIresolution\fP
143sets the resolution for all screens, in dots per inch.
144To be used when the server cannot determine the screen size(s) from the
145hardware.
146.TP 8
147.B dpms
148enables DPMS (display power management services), where supported. The
149default state is platform and configuration specific.
150.TP 8
151.B \-dpms
152disables DPMS (display power management services). The default state
153is platform and configuration specific.
154.TP 8
155.BI \-extension extensionName
156disables named extension. If an unknown extension name is specified,
157a list of accepted extension names is printed.
158.TP 8
159.BI +extension extensionName
160enables named extension. If an unknown extension name is specified,
161a list of accepted extension names is printed.
162.TP 8
163.B \-f \fIvolume\fP
164sets beep (bell) volume (allowable range: 0-100).
165.TP 8
166.B \-fc \fIcursorFont\fP
167sets default cursor font.
168.TP 8
169.B \-fn \fIfont\fP
170sets the default font.
171.TP 8
172.B \-fp \fIfontPath\fP
173sets the search path for fonts. This path is a comma separated list
174of directories which the X server searches for font databases.
175See the FONTS section of this manual page for more information and the default
176list.
177.TP 8
178.B \-help
179prints a usage message.
180.TP 8
181.B \-I
182causes all remaining command line arguments to be ignored.
183.TP 8
184.B \-maxbigreqsize \fIsize\fP
185sets the maximum big request to
186.I size
187MB.
188.TP 8
189.B \-nocursor
190disable the display of the pointer cursor.
191.TP 8
192.B \-nolisten \fItrans-type\fP
193disables a transport type. For example, TCP/IP connections can be disabled
194with
195.BR "\-nolisten tcp" .
196This option may be issued multiple times to disable listening to different
197transport types.
198.TP 8
199.B \-noreset
200prevents a server reset when the last client connection is closed. This
201overrides a previous
202.B \-terminate
203command line option.
204.TP 8
205.B \-p \fIminutes\fP
206sets screen-saver pattern cycle time in minutes.
207.TP 8
208.B \-pn
209permits the server to continue running if it fails to establish all of
210its well-known sockets (connection points for clients), but
211establishes at least one. This option is set by default.
212.TP 8
213.B \-nopn
214causes the server to exit if it fails to establish all of its well-known
215sockets (connection points for clients).
216.TP 8
217.B \-r
218turns off auto-repeat.
219.TP 8
220.B r
221turns on auto-repeat.
222.TP 8
223.B -retro
224starts the stipple with the classic stipple and cursor visible. The default
225is to start with a black root window, and to suppress display of the cursor
226until the first time an application calls XDefineCursor(). For the Xorg
227server, this also sets the default for the DontZap option to FALSE. For
228kdrive servers, this implies -zap.
229.TP 8
230.B \-s \fIminutes\fP
231sets screen-saver timeout time in minutes.
232.TP 8
233.B \-su
234disables save under support on all screens.
235.TP 8
236.B \-seat \fIseat\fP
237seat to run on. Takes a string identifying a seat in a platform
238specific syntax. On platforms which support this feature this may be
239used to limit the server to expose only a specific subset of devices
240connected to the system.
241.TP 8
242.B \-t \fInumber\fP
243sets pointer acceleration threshold in pixels (i.e. after how many pixels
244pointer acceleration should take effect).
245.TP 8
246.B \-terminate
247causes the server to terminate at server reset, instead of continuing to run.
248This overrides a previous
249.B \-noreset
250command line option.
251.TP 8
252.B \-to \fIseconds\fP
253sets default connection timeout in seconds.
254.TP 8
255.B \-tst
256disables all testing extensions (e.g., XTEST, XTrap, XTestExtension1, RECORD).
257.TP 8
258.B tty\fIxx\fP
259ignored, for servers started the ancient way (from init).
260.TP 8
261.B v
262sets video-off screen-saver preference.
263.TP 8
264.B \-v
265sets video-on screen-saver preference.
266.TP 8
267.B \-wm
268forces the default backing-store of all windows to be WhenMapped. This
269is a backdoor way of getting backing-store to apply to all windows.
270Although all mapped windows will have backing store, the backing store
271attribute value reported by the server for a window will be the last
272value established by a client. If it has never been set by a client,
273the server will report the default value, NotUseful. This behavior is
274required by the X protocol, which allows the server to exceed the
275client's backing store expectations but does not provide a way to tell
276the client that it is doing so.
277.TP 8
278.B \-wr
279sets the default root window to solid white instead of the standard root weave
280pattern.
281.TP 8
282.B \-x \fIextension\fP
283loads the specified extension at init.
284This is a no-op for most implementations.
285.TP 8
286.B [+-]xinerama
287enables(+) or disables(-) the XINERAMA extension. The default state is
288platform and configuration specific.
289.SH SERVER DEPENDENT OPTIONS
290Some X servers accept the following options:
291.TP 8
292.B \-ld \fIkilobytes\fP
293sets the data space limit of the server to the specified number of kilobytes.
294A value of zero makes the data size as large as possible. The default value
295of \-1 leaves the data space limit unchanged.
296.TP 8
297.B \-lf \fIfiles\fP
298sets the number-of-open-files limit of the server to the specified number.
299A value of zero makes the limit as large as possible. The default value
300of \-1 leaves the limit unchanged.
301.TP 8
302.B \-ls \fIkilobytes\fP
303sets the stack space limit of the server to the specified number of kilobytes.
304A value of zero makes the stack size as large as possible. The default value
305of \-1 leaves the stack space limit unchanged.
306.TP 8
307.B \-render
308.BR default | mono | gray | color
309sets the color allocation policy that will be used by the render extension.
310.RS 8
311.TP 8
312.I default
313selects the default policy defined for the display depth of the X
314server.
315.TP 8
316.I mono
317don't use any color cell.
318.TP 8
319.I gray
320use a gray map of 13 color cells for the X render extension.
321.TP 8
322.I color
323use a color cube of at most 4*4*4 colors (that is 64 color cells).
324.RE
325.TP 8
326.B \-dumbSched
327disables smart scheduling on platforms that support the smart scheduler.
328.TP
329.B \-schedInterval \fIinterval\fP
330sets the smart scheduler's scheduling interval to
331.I interval
332milliseconds.
333.SH XDMCP OPTIONS
334X servers that support XDMCP have the following options.
335See the \fIX Display Manager Control Protocol\fP specification for more
336information.
337.TP 8
338.B \-query \fIhostname\fP
339enables XDMCP and sends Query packets to the specified
340.IR hostname .
341.TP 8
342.B \-broadcast
343enable XDMCP and broadcasts BroadcastQuery packets to the network. The
344first responding display manager will be chosen for the session.
345.TP 8
346.B \-multicast [\fIaddress\fP [\fIhop count\fP]]
347Enable XDMCP and multicast BroadcastQuery packets to the network.
348The first responding display manager is chosen for the session. If an
349address is specified, the multicast is sent to that address. If no
350address is specified, the multicast is sent to the default XDMCP IPv6
351multicast group. If a hop count is specified, it is used as the maximum
352hop count for the multicast. If no hop count is specified, the multicast
353is set to a maximum of 1 hop, to prevent the multicast from being routed
354beyond the local network.
355.TP 8
356.B \-indirect \fIhostname\fP
357enables XDMCP and send IndirectQuery packets to the specified
358.IR hostname .
359.TP 8
360.B \-port \fIport-number\fP
361uses the specified \fIport-number\fP for XDMCP packets, instead of the
362default. This option must be specified before any \-query, \-broadcast,
363\-multicast, or \-indirect options.
364.TP 8
365.B \-from \fIlocal-address\fP
366specifies the local address to connect from (useful if the connecting host
367has multiple network interfaces). The \fIlocal-address\fP may be expressed
368in any form acceptable to the host platform's \fIgethostbyname\fP(3)
369implementation.
370.TP 8
371.B \-once
372causes the server to terminate (rather than reset) when the XDMCP session
373ends.
374.TP 8
375.B \-class \fIdisplay-class\fP
376XDMCP has an additional display qualifier used in resource lookup for
377display-specific options. This option sets that value, by default it
378is "MIT-Unspecified" (not a very useful value).
379.TP 8
380.B \-cookie \fIxdm-auth-bits\fP
381When testing XDM-AUTHENTICATION-1, a private key is shared between the
382server and the manager. This option sets the value of that private
383data (not that it is very private, being on the command line!).
384.TP 8
385.B \-displayID \fIdisplay-id\fP
386Yet another XDMCP specific value, this one allows the display manager to
387identify each display so that it can locate the shared key.
388.SH XKEYBOARD OPTIONS
389X servers that support the XKEYBOARD (a.k.a. \*qXKB\*q) extension accept the
390following options. All layout files specified on the command line must be
391located in the XKB base directory or a subdirectory, and specified as the
392relative path from the XKB base directory. The default XKB base directory is
393.IR __projectroot__/lib/X11/xkb .
394.TP 8
395.BR [+-]accessx " [ \fItimeout\fP [ \fItimeout_mask\fP [ \fIfeedback\fP [ \fIoptions_mask\fP ] ] ] ]"
396enables(+) or disables(-) AccessX key sequences.
397.TP 8
398.B \-xkbdir \fIdirectory\fP
399base directory for keyboard layout files. This option is not available
400for setuid X servers (i.e., when the X server's real and effective uids
401are different).
402.TP 8
403.B \-ardelay \fImilliseconds\fP
404sets the autorepeat delay (length of time in milliseconds that a key must
405be depressed before autorepeat starts).
406.TP 8
407.B \-arinterval \fImilliseconds\fP
408sets the autorepeat interval (length of time in milliseconds that should
409elapse between autorepeat-generated keystrokes).
410.TP 8
411.B \-xkbmap \fIfilename\fP
412loads keyboard description in \fIfilename\fP on server startup.
413.SH "NETWORK CONNECTIONS"
414The X server supports client connections via a platform-dependent subset of
415the following transport types: TCP\/IP, Unix Domain sockets, DECnet,
416and several varieties of SVR4 local connections. See the DISPLAY
417NAMES section of the \fIX\fP(__miscmansuffix__) manual page to learn how to
418specify which transport type clients should try to use.
419.SH GRANTING ACCESS
420The X server implements a platform-dependent subset of the following
421authorization protocols: MIT-MAGIC-COOKIE-1, XDM-AUTHORIZATION-1,
422XDM-AUTHORIZATION-2, SUN-DES-1, and MIT-KERBEROS-5. See the
423\fIXsecurity\fP(__miscmansuffix__) manual page for information on the
424operation of these protocols.
425.PP
426Authorization data required by the above protocols is passed to the
427server in a private file named with the \fB\-auth\fP command line
428option. Each time the server is about to accept the first connection
429after a reset (or when the server is starting), it reads this file.
430If this file contains any authorization records, the local host is not
431automatically allowed access to the server, and only clients which
432send one of the authorization records contained in the file in the
433connection setup information will be allowed access. See the
434\fIXau\fP manual page for a description of the binary format of this
435file. See \fIxauth\fP(1) for maintenance of this file, and distribution
436of its contents to remote hosts.
437.PP
438The X server also uses a host-based access control list for deciding
439whether or not to accept connections from clients on a particular machine.
440If no other authorization mechanism is being used,
441this list initially consists of the host on which the server is running as
442well as any machines listed in the file \fI/etc/X\fBn\fI.hosts\fR, where
443\fBn\fP is the display number of the server. Each line of the file should
444contain either an Internet hostname (e.g. expo.lcs.mit.edu) or a DECnet
445hostname in double colon format (e.g. hydra::) or a complete name in the format
446\fIfamily\fP:\fIname\fP as described in the \fIxhost\fP(1) manual page.
447There should be no leading or trailing spaces on any lines. For example:
448.sp
449.in +8
450.nf
451joesworkstation
452corporate.company.com
453star::
454inet:bigcpu
455local:
456.fi
457.in -8
458.PP
459Users can add or remove hosts from this list and enable or disable access
460control using the \fIxhost\fP command from the same machine as the server.
461.PP
462If the X FireWall Proxy (\fIxfwp\fP) is being used without a sitepolicy,
463host-based authorization must be turned on for clients to be able to
464connect to the X server via the \fIxfwp\fP. If \fIxfwp\fP is run without
465a configuration file and thus no sitepolicy is defined, if \fIxfwp\fP
466is using an X server where xhost + has been run to turn off host-based
467authorization checks, when a client tries to connect to this X server
468via \fIxfwp\fP, the X server will deny the connection. See \fIxfwp\fP(1)
469for more information about this proxy.
470.PP
471The X protocol intrinsically does not have any notion of window operation
472permissions or place any restrictions on what a client can do; if a program can
473connect to a display, it has full run of the screen.
474X servers that support the SECURITY extension fare better because clients
475can be designated untrusted via the authorization they use to connect; see
476the \fIxauth\fP(1) manual page for details. Restrictions are imposed
477on untrusted clients that curtail the mischief they can do. See the SECURITY
478extension specification for a complete list of these restrictions.
479.PP
480Sites that have better
481authentication and authorization systems might wish to make
482use of the hooks in the libraries and the server to provide additional
483security models.
484.SH SIGNALS
485The X server attaches special meaning to the following signals:
486.TP 8
487.I SIGHUP
488This signal causes the server to close all existing connections, free all
489resources, and restore all defaults. It is sent by the display manager
490whenever the main user's main application (usually an \fIxterm\fP or window
491manager) exits to force the server to clean up and prepare for the next
492user.
493.TP 8
494.I SIGTERM
495This signal causes the server to exit cleanly.
496.TP 8
497.I SIGUSR1
498This signal is used quite differently from either of the above. When the
499server starts, it checks to see if it has inherited SIGUSR1 as SIG_IGN
500instead of the usual SIG_DFL. In this case, the server sends a SIGUSR1 to
501its parent process after it has set up the various connection schemes.
502\fIXdm\fP uses this feature to recognize when connecting to the server
503is possible.
504.SH FONTS
505The X server can obtain fonts from directories and/or from font servers.
506The list of directories and font servers
507the X server uses when trying to open a font is controlled
508by the \fIfont path\fP.
509.LP
510The default font path is
511__default_font_path__ .
512.LP
513A special kind of directory can be specified using the \fBcatalogue\fP:
514prefix. Directories specified this way can contain symlinks pointing to the
515real font directories. See the FONTPATH.D section for details.
516.LP
517The font path can be set with the \fB\-fp\fP option or by \fIxset\fP(1)
518after the server has started.
519.SH "FONTPATH.D"
520You can specify a special kind of font path in the form \fBcatalogue:<dir>\fR.
521The directory specified after the catalogue: prefix will be scanned for symlinks
522and each symlink destination will be added as a local fontfile FPE.
523.PP
524The symlink can be suffixed by attributes such as '\fBunscaled\fR', which
525will be passed through to the underlying fontfile FPE. The only exception is
526the newly introduced '\fBpri\fR' attribute, which will be used for ordering
527the font paths specified by the symlinks.
528
529An example configuration:
530
531.nf
532 75dpi:unscaled:pri=20 \-> /usr/share/X11/fonts/75dpi
533 ghostscript:pri=60 \-> /usr/share/fonts/default/ghostscript
534 misc:unscaled:pri=10 \-> /usr/share/X11/fonts/misc
535 type1:pri=40 \-> /usr/share/X11/fonts/Type1
536 type1:pri=50 \-> /usr/share/fonts/default/Type1
537.fi
538
539This will add /usr/share/X11/fonts/misc as the first FPE with the attribute
540\N'39'unscaled', second FPE will be /usr/share/X11/fonts/75dpi, also with
541the attribute 'unscaled' etc. This is functionally equivalent to setting
542the following font path:
543
544.nf
545 /usr/share/X11/fonts/misc:unscaled,
546 /usr/share/X11/fonts/75dpi:unscaled,
547 /usr/share/X11/fonts/Type1,
548 /usr/share/fonts/default/Type1,
549 /usr/share/fonts/default/ghostscript
550.fi
551
552.SH FILES
553.TP 30
554.I /etc/X\fBn\fP.hosts
555Initial access control list for display number \fBn\fP
556.TP 30
557.IR __datadir__/fonts/X11/misc , __datadir__/fonts/X11/75dpi , __datadir__/fonts/X11/100dpi
558Bitmap font directories
559.TP 30
560.IR __datadir__/fonts/X11/TTF , __datadir__/fonts/X11/Type1
561Outline font directories
562.TP 30
563.I /tmp/.X11-unix/X\fBn\fP
564Unix domain socket for display number \fBn\fP
565.TP 30
566.I /usr/adm/X\fBn\fPmsgs
567Error log file for display number \fBn\fP if run from \fIinit\fP(__adminmansuffix__)
568.TP 30
569.I __projectroot__/lib/X11/xdm/xdm-errors
570Default error log file if the server is run from \fIxdm\fP(1)
571.SH "SEE ALSO"
572General information: \fIX\fP(__miscmansuffix__)
573.PP
574Protocols:
575.I "X Window System Protocol,"
576.I "The X Font Service Protocol,"
577.I "X Display Manager Control Protocol"
578.PP
579Fonts: \fIbdftopcf\fP(1), \fImkfontdir\fP(1), \fImkfontscale\fP(1),
580\fIxfs\fP(1), \fIxlsfonts\fP(1), \fIxfontsel\fP(1), \fIxfd\fP(1),
581.I "X Logical Font Description Conventions"
582.PP
583Keyboards: \fIxkeyboard-config\fP(__miscmansuffix__)
584.PP
585Security: \fIXsecurity\fP(__miscmansuffix__), \fIxauth\fP(1), \fIXau\fP(1),
586\fIxdm\fP(1), \fIxhost\fP(1), \fIxfwp\fP(1),
587.I "Security Extension Specification"
588.PP
589Starting the server: \fIstartx\fP(1), \fIxdm\fP(1), \fIxinit\fP(1)
590.PP
591Controlling the server once started: \fIxset\fP(1), \fIxsetroot\fP(1),
592\fIxhost\fP(1), \fIxinput\fP(1), \fIxrandr\fP(1)
593.PP
594Server-specific man pages:
595\fIXorg\fP(1), \fIXdmx\fP(1), \fIXephyr\fP(1), \fIXnest\fP(1),
596\fIXvfb\fP(1), \fIXquartz\fP(1), \fIXWin\fP(1).
597.PP
598Server internal documentation:
599.I "Definition of the Porting Layer for the X v11 Sample Server"
600.SH AUTHORS
601The sample server was originally written by Susan Angebranndt, Raymond
602Drewry, Philip Karlton, and Todd Newman, from Digital Equipment
603Corporation, with support from a large cast. It has since been
604extensively rewritten by Keith Packard and Bob Scheifler, from MIT.
605Dave Wiggins took over post-R5 and made substantial improvements.