Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!jim
From: jim@EXPO.LCS.MIT.EDU (Jim Fulton)
Newsgroups: comp.windows.x
Subject: Re: xinit lacks init in it
Message-ID: <8808291905.AA16353@EXPO.LCS.MIT.EDU>
Date: 29 Aug 88 19:05:40 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 37


The approach we've encouraged in the past has been to create two scripts:

    1.  something that loads the right defaults, puts some windows in a
	nice place, and starts a window manager.  For now, think of it
	as /usr/local/bin/defxenv:

		#!/bin/sh
		DISPLAY=:0 ; export DISPLAY
		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 &
		uwm


    2.  something called "x11" or "startx" or whatever calls xinit with
	the preceeding script as an argument along with whatever the right
	server ought to be (if you have more than or, if your site admin
	didn't make a link called X somewhere in your path).  For now,
	lets pretend that it is called /usr/local/bin/x11:

		#!/bin/sh
		xinit /usr/local/bin/defxenv


You can then instruct your users to type "x11" to start the world.

Just to show you that we're nice guys and that we really do listen to other
people's suggestions, if you have a $HOME/.xinitrc, the R3 xinit will use that
instead of the default xterm command if no client arguments are given.  But, we
still prefer friendly front-end scripts....


Jim Fulton
MIT X Consortium