🚀 go-pugleaf

David Robinson wrote:
> 
> 
>   Thanks David but I've got an RPM (AfterStep-1.0-3.i386.rpm) which I then ran
> as root rpm -ivh [filename] & everything there went fine - no errors.  Then
> checking it using glint it seems fine!!
> I think my problem lies in getting my system files to point to Afterstep.
> I'm doing something wrong but I don't know what :-(
> In the 7 mths. using Linux I've never tried to change my wm - I suppose I
> could always get RedHat 5.0 But I need to learn to do this & I'm sick of the
> Win95 look :-))
> PS I have an EVERYTHING install of Redhat 4.2 from the Powertools CD (wastes a
> lot of space but then I know I've got make etc. on my system - big grin)

Are you running xdm or startx to bring up X?  xdm is `best', but you
need to set the default run level in /etc/inittab.  Fairly self
explanatory, given the comments in the 4.2 version of the file.  Set the
initdefault line to
id:5:initdefault:

Otherwise, just stick with startx, and adapt the following comments.

There are two sets of startup files which can find their way into your
home directory.  The xdm `standards' are ~/.xsession as the startup
executable, and ~/.Xresources as the resources file.  For startx, the
files are, I think, .Xclients as the executable, and .Xdefaults as the
resources file.  I always make .xsession a link to .Xclients and
.Xresources a link to .Xdefaults, or vice versa.  That way, you can
experiment with the two start methods and still get much the same
results.

I'll talk about xdm startup, with which I am more familiar.

.xsession (.Xclients) which must be executable, will arrange to do an
xrdb -merge ~/.Xresources
to get your resources set up, and then, after possibly starting up a few
clients in the background (although this tends to be done in the window
manager startup files) it will exec your window manager.  That way, when
you exit from the wm, the .xsession process dies, and the xdm login
dialogue is displayed again.

You will probably find that there are a few different wm startup
attempts at the end of the .Xclients file, in order of preference. 
Change the call to fvwm95 (or fvwm95-2) to an afterstep invocation, then
try to work out how the afterstep setup files are configured.

Yours faithfully,
-- 
 __ /__   Peter B. West
   /     p.west@mailbox.uq.edu.au
  /    "Master, to whom shall we go?"