On Mon, 01 Oct 2007 11:39:49 -0500 "Billy N. Patton" <[EMAIL PROTECTED]> wrote:
> I've searched the FAQ and cannot find what I'm loking for. > > I run fvwm2 in my vnc connection just fine. When I come to work and set at > my desk my Linux box is > running kde. > here is my .xinitrc This doesn't start fvwm. > #!/bin/sh > > exec >$HOME/.xsession.$DISPLAY 2>&1 > > if [ -f $HOME/.bashrc ] > then > . $HOME/.bashrc > fi > > #xrdb $HOME/.Xdefaults # Load X11 resource database > #exec $HOME/local/kde1.1/bin/startkde > #exec /usr/bin/startkde > #exec /home/cjitlal/bin/startkde3.1.1 > > #xterm -geometry 80x24-0-0 & > /usr/local/bin/icewm > I don't know where this came from, but this .xinitrc is utterly useless. As someone said, you are putting icewm, not fvwm in here. I can't figure how do you expect fvwm to start ok. But there are bigger flaws in that script. To start with, you should be using '&' at the end of each command. Otherwise, the server will just wait until that process has ended to start the following. But there is an even bigger flaw: you are using exec at the very beginning of the script. When you call something with 'exec', you tell the parent shell to close itself, and completely transfer the control to the new process you are launching (as far as I know). So, anything below the exec line, is, virtually, nonexistent. Also, and this is one thing I really can't figure out: why the heck are you sourcing your bashrc file from xinitrc??? If you have some doubts or something I can help, though this list is not really for this kind of stuff, but for fvwm stuff (this has nothing to do with fvwm, really). Regards. -- Jesús Guerrero <[EMAIL PROTECTED]>
