"Thomas J. Downey Jr" wrote:
-> The problem was the the LD_LIBRARY_PATH was not set until i ran openwin.
-> I set it in my .cshrc and got past that problem.
->
-> Now I get:
->
-> fvwm: can't open display :0
->
-> I checked the documentation and FAQ and there is no entry for
-> "now that I've compiled fvwm, how do I run it?"
(looking at the following after I wrote it, I realize I made several
assumptions about your local setup that may be incorrect. If so, let
me know...)
When you start OpenWindows with the "openwin" command you usually get
the "olwm" window manager, which is started from /usr/openwin/lib/Xinitrc.
Something that might work would be to copy that file to ~/.xinitrc and
change the three lines that start olwm:
sleep 15 & pid=$! # OpenLook Window Manager
olwm -syncpid $pid &
wait $pid # Pause until olwm inits
to a line that starts fvwm instead:
fvwm &
I think you need to make .xinitrc executable ("chmod 0700 ~/.xinitrc")
though I'm not certain... this is all based on my old setup from back in
the Dark Ages when I too was stuck with OpenWindows (spit).
It may be helpful to start OpenWindows with a command like
openwin >& openwin-errs
so you can look at the file "openwin-errs" if things go wrong and you'll
at least have some idea what the error messages are.
Something else that might help would be to see if anyone else where you
work has startup files (.xinitrc, .openwin-init, etc) that you can use
as a starting point. That's what a lot of us do... I think there are
probably only about 12 original .xinitrc files in the world... :-)
-Robert Tarrall.-
Unix System/Network Admin
Laboratory for Computational Dynamics
CU - Boulder
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Jan 30 1996 - 19:44:19 GMT