Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ xinit(X) — OpenDesktop X11R4-EFS-4.1.1b

Media Vault

Software Library

Restoration Projects

Artifacts Sought


 xinit(X)                 X Version 11 (Release 4)                   xinit(X)



 Name

    xinit - X Window System initializer

 Syntax

    xinit [[client] options] [--[server] [display] options]

 Description

    xinit starts the X Window System server and a first client program (usu-
    ally a terminal emulator) on systems that cannot start X directly from
    /etc/init or in environments that use multiple window systems. When this
    first client exits, xinit kills the X server and then terminates.

    If no arguments are given on the command line, xinit looks for a file in
    the user's home directory called .xinitrc to run as a shell script to
    start up client programs.  If no such file exists, xinit executes the
    following client command line:

               xterm -geometry +1+1 -n login -display :0

    xinit also looks for a file in the user's home directory called .xser-
    verrc to run as a shell script to start up the server.  If no such file
    exists, xinit executes the following server command line:

               X :0

    Note that this assumes that there is a program named X in the current
    search path. On SCO Open Desktop systems, X is linked to Xsco.

    Programs that are run by .xinitrc and .xserverrc should be run in the
    background if they do not exit right away, so that they don't prevent
    other programs from starting up.  The last program started from these
    scripts, usually a window manager or terminal emulator, should run in the
    foreground so that the script does not exit and cause xinit to exit.


 Options


    [client] options
       specifies an alternate client and command line options

    [--[server] [display] options]
       specifies an alternate X server command line.  If server is omitted,
       xinit runs the default server.  If display is omitted, xinit runs the
       server on the default screen, ``:0''.  xinit passes options as argu-
       ments to the server command (see Xsco(X)).

    Both the client program name and the server program name must begin with
    a slash (/) or a period (.).  Otherwise, they are treated as arguments to
    be appended to their respective startup lines.  This makes it possible to
    add arguments (for example, foreground and background colors) without
    having to retype the whole command line.


 Examples

    Below are several examples of how command line arguments in xinit are
    used.

    xinit   starts up a server named X and runs the user's .xinitrc, if it
            exists, or else starts an xterm

    xinit -- /usr/bin/X11/Xsco :1
            starts the Xsco server on an alternate display

    xinit -geometry =80x65+10+10 -fn 8x13 -j -fg white -bg navy
            starts up a server named X, and appends the given arguments to
            the default xterm command.  It ignores .xinitrc.

    xinit -e widgets -- ./Xsco -l -c
            uses the command ./Xsco -l -c to start the server and appends the
            arguments -e widgets to the default xterm command

    xinit /usr/ucb/rsh fasthost cpupig -display ws:1 -- :1 -a 2 -t 5
            starts a server named X on display 1 with the arguments -a 2 -t
            5.  It then starts a remote shell on the machine fasthost in
            which it runs the command cpupig, telling it to display back on
            the local workstation.

    Below is a sample .xinitrc that starts a clock, several terminals, and
    leaves the window manager running as the ``last'' application.  Assuming
    that the window manager has been configured properly, the user then
    chooses the ``Exit'' menu item to shut down X.

       xrdb -load $HOME/.Xres
       xsetroot -solid gray &
       xclock -g 50x50-0+0 -bw 0 &
       xload -g 50x50-50+0 -bw 0 &
       xterm -g 80x24+0+0 &
       xterm -g 80x24+0-0 &
       mwm

    Sites that want to create a common startup environment could simply cre-
    ate a default .xinitrc that references a site-wide startup file:

       #!/bin/sh
       . /usr/local/lib/site.xinitrc

    Another approach is to write a script that starts xinit with a specific
    shell script.  Such scripts are usually named x11, xstart, or startx and
    are a convenient way to provide a simple interface for novice users:

       #!/bin/sh
       xinit /usr/lib/X11/sys.startxrc -- /usr/bin/X11/Xsco :1


 Environment Variables


    DISPLAY the name of the display to which clients should connect

    XINITRC an init file containing shell commands to start up the initial
            windows.  By default, .xinitrc in the home directory is used.

 See Also

    startx(X), X(X), Xsco(X), xrdb(X), xterm(X)

 Copyright

    Copyright 1988, Massachusetts Institute of Technology.
    See X(X) for a full statement of rights and permissions.

















































Typewritten Software • bear@typewritten.org • Edmonds, WA 98026