Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Jan 1999 11:47:07 -0600
From:      Bill Hamilton <billh@finsco.com>
To:        "Norman C. Rice" <nrice@emu.sourcee.com>
Cc:        Nesi Unanaowo <nesi_unanaowo@net.com>, nesi@net.com, freebsd-questions@FreeBSD.ORG
Subject:   Re: Window manager problem.
Message-ID:  <36AF511B.6D39DA86@finsco.com>
References:  <36AE3DFA.269DDA0C@net.com> <36AE4874.31B85169@finsco.com> <36AF40D9.92E5C787@net.com> <19990127120521.A22560@emu.sourcee.com>

next in thread | previous in thread | raw e-mail | index | archive | help
The way you worded your original message, it sounded as if you just
copied
the xinitrc file to your home directory and did not modify it.
I used the info on the man page or some web page and it worked fine for
me.
In fact, when I added the default xinitrc info at the top of it, it
broke. It
would not start up.
All you need in .xinitrc is something like the following 3 lines (no
execs at all)
xhost +
xterm -fn 10x20 -ls -fg black -bg lemonchiffon2 -sb -geometry 91x24+64+6
-n "Main"&
fvwm2


> > I am beginning to think that for some obscure reason the
> > fvwm2 is not started. I know for sure that my .xinitrc file
> > is being read because the xterms and the xclock referenced
> > are started when X is started.
> > The command that starts fvwm2 has the format: exec fvwm2
(snip)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36AF511B.6D39DA86>