Install Instructions for Greg J. Badros's Desktop Configuration Contest Entry
-----------------------------------------------------------------------------

Updated 6/11/96


First you should read everything you can.  READMEs in any and all
directories, user documentation, etc.  You should then review and
edit Install.sh making changes appropriate to your system, and
setting which features you want installed.  If you want to rebuild zsh
and/or fvwm, you may want to create a directory, ~/src, and tar xzf their
source code trees there. You may also want to install the libXaw3d rpm
before proceeding.

*********You must edit Install.sh before proceeding

Then:

su root
./Install.sh 2>&1 | tee Install-Log.txt

Check the log closely.  It is not a great install routine, but it should
at least come close to working, and more importantly, be very explicit
about what it specifically hopes to accomplish.

Exit from your root shell, then set your test user's shell to be
zsh (/bin/zsh-- check to make sure it exists and is listed in /etc/shells).

Try logging back in, then running startx; or start xdm as root, and
try loggin in at the new, cool xdm shell.

Be patient-- it can take a few seconds to startup on my Linux box.

You require fvwm2 or fvwm95, auctex for .emacs.el, and various normal
utilities like xrdb, zless, etc.

Also, recommended are arena and xkeycaps (in contrib section of
ftp.redhat.com).  You should install these before this configuration

After installation, you should edit the files:
.fvwm2rc.defines
.Xdefaults-fvwm-defines

Also check /etc/zshenv to see it set ZSH_HELP_DIRECTORY properly

And verify your environment settings in /etc/profile, especially
the PATH variable

To try it out, in one virtual console, do a:

tail -f ~/.FVWM2-errors
(or tail -f ~/.FVWM95-errors if you're using fvwm95)
[The exact filename is set in .xinitrc]

Then do a startx, or login at your xdm screen.  Verify that both startx
and xdm use .xinitrc (as opposed to .xsession, or something else) as their
startup file.  You may want .xsession to be a symlink to .xinitrc.

If things go bad, look at the .FVWM2-errors file (switch back to that
virtual console), or look at /tmp/fvwm*.  By default, some trace commands
are generated by m4 and by FVWM as they each parse your configuration files.
The error diagnostics should be helpful in finding any problems.

Enjoy!
Greg J. Badros
<gjb@cs.duke.edu>
