On Thu, Nov 17, 2005 at 05:19:42PM +1030, Always Working On Linux wrote:
> Myles Green wrote:
>
> >On Wed, 16 Nov 2005 22:24:33 +0000
> >Chris Green <[EMAIL PROTECTED]> wrote:
> >
> >
> >>What's the simplest way to get fvwm2 running?
> >>
> >>
> >
> >Hi Chris :)
> >
> >The easiest way to get Fvwm2 to run from [g|k|w|x]dm is to create a
> >~/.xsession file as described by Thomas. Some distros need that file to
> >be called ~/.Xsession instead so it might not work with ~/.xsession. If
> >you want to start it by using startx then rename that file to
> >~/.xinitrc.
> >
That doesn't appear to work, it's the first thing I tried. The
existing .xsession file ran xfce so I moved it and created a new one
that called fvwm2 but that produces the symptoms I described,
absolutely nothing.
[snip]
> >
> Actually the "easiest" way to get fvwm running from any managed session
> is to open an xterm and simply type "fvwm -replace &" and then start
> the gui for the session manager and save the session once fvwm is
> running. Just add a -f filename to start it with a desired fvwm2rc.
>
Yes, I tried that too, I just got the response that "Another window
manager is running", presumably this means that xfce is not well
behaved.
I *have* now managed to get fvmw2 running from startx so fvwm is
installed OK on my system, I just need to work out how to get it to
start from wdm.
Thanks for all the responses, hopefully I'll be back in a while asking
configuration questions. :-)
I also want to get it up and running on my Solaris system at work, the
aim being to have similar setups at work and home. I already use the
same MUA, browser and editor so making the window manager the same
will make life even easier.
--
Chris Green ([EMAIL PROTECTED])
"Never ascribe to malice that which can be explained by incompetence."
