Red Hat 4.2/XFree86 3.3/fvwm2/TheNextLevel/what does it all mean?
Having downloaded and installed Red Hat 4.2(XF86Free 3.3) for the i386
platform. My system:
Pentium 133/48megs memory
two 1.6 gig hard drives
Diamond Stealth 3000 3d/4megs(S3 Virge VX)
Sony Multiscan 15sx monitor
Now the trouble that I(and a number of Linux freaks in Albuquerque New
Mexico, many of whom proported to be paid to deal with X-windows systems)
have had is with the configuration of the X-windows system(XFree86 3.3 that
comes with Red Hat 4.2).
Problem #1
"What resources are used with TheNextLevel"
Take the following .Xclients config file that is the default set up that
Red Hat 4.2 comes with:
#!/bin/bash
########################################################################
# -*- sh -*- #
# #
# ~/.Xclients: used by startx (xinit) to start up a window manager and #
# any other clients you always want to start an X session with. #
# #
# feel free to edit this file to suit your needs. #
########################################################################
# these files are left sitting around by TheNextLevel.
rm -f $HOME/Xrootenv.0
rm -f /tmp/fvwmrc*
# first, find an M4-enabled config file (such as
# the one from TheNextLevel) for fvwm2 or fvwm95.
RCFILE=""
for tryfile in "$HOME/.fvwm2rc.m4" "/etc/X11/TheNextLevel/.fvwm2rc.m4"; do
if [ -f "$tryfile" ]; then
RCFILE="$tryfile"
break
fi
done
# if it really exists, use it; if not, fvwm2 or fvwm95 will
# automagically look for a config file in the regular places.
if [ -n "$RCFILE" ]; then
FVWMOPTIONS="-f 'FvwmM4 -debug $RCFILE'"
else
FVWMOPTIONS=""
fi
# TheNextLevel is supposed to work
# with both fvwm95 and fvwm2
# (try fvwm95 first, then fvwm2).
for FVWMVER in 95 95-2 2; do
if [ -n "$(type -path fvwm${FVWMVER})" ]; then
env > "$HOME"/Xrootenv.0
# if this works, we stop here
eval "exec fvwm${FVWMVER} ${FVWMOPTIONS}" >
"$HOME"/.FVWM${FVWMVER}-errors 2>&1
fi
done
# gosh, neither fvwm95 nor fvwm2 is available;
# let's try regular fvwm (TheNextLevel doesn't
# work with fvwm1).
if [ -n "$(type -path fvwm)" ]; then
# if this works, we stop here
exec fvwm
fi
# wow, fvwm isn't here either ...
# use twm as a last resort.
xterm &
exec twm
------------
By default, this sets up fvwm95 as the default windows manager for X-windows.
The Question:
Starting the window manager fvwm95-2 as show above, does fvwm95-2 use the
system default file /etc/X11/fvwm95-2/fvwm2rc95 or, does TheNextLevel
configure everything from the various files in the /etc/X11/TheNextLevel/
directory?
Problem #2:
"Getting TheNextLevel to work with fvwm2"
Fvwm95 was interesting for about 10 minutes. But I'm want a more
traditional X-windows look, specifically fvwm2. But I also want the great
features of TheNextLevel. This shouldn't be a problem, because TheNextLevel
works with fvwm2(theoretically). I have re-written the above .Xclients file:
-------------------------------------------
#!/bin/bash
########################################################################
# -*- sh -*- #
# #
# ~/.Xclients: used by startx (xinit) to start up a window manager and #
# any other clients you always want to start an X session with. #
# #
# feel free to edit this file to suit your needs. #
########################################################################
# these files are left sitting around by TheNextLevel.
rm -f $HOME/Xrootenv.0
# first, find an M4-enabled config file (such as
# the one from TheNextLevel) for fvwm2 or fvwm95.
RCFILE=""
for tryfile in "$HOME/.fvwm2rc.m4" "/etc/X11/TheNextLevel/.fvwm2rc.m4"; do
if [ -f "$tryfile" ]; then
RCFILE="$tryfile"
break
fi
done
# if it really exists, use it; if not, fvwm2 or fvwm95 will
# automagically look for a config file in the regular places.
if [ -n "$RCFILE" ]; then
FVWMOPTIONS="-f 'FvwmM4 -debug $RCFILE'"
else
FVWMOPTIONS=""
fi
# TheNextLevel is supposed to work
# with both fvwm95 and fvwm2
# (try fvwm95 first, then fvwm2).
for FVWMVER in 2; do
if [ -n "$(type -path fvwm${FVWMVER})" ]; then
env > "$HOME"/Xrootenv.0
# if this works, we stop here
eval "exec fvwm${FVWMVER} ${FVWMOPTIONS}" >
"$HOME"/.FVWM${FVWMVER}-errors 2>&1
fi
done
# gosh, neither fvwm95 nor fvwm2 is available;
# let's try regular fvwm (TheNextLevel doesn't
# work with fvwm1).
if [ -n "$(type -path fvwm)" ]; then
# if this works, we stop here
exec fvwm
fi
# wow, fvwm isn't here either ...
# use twm as a last resort.
xterm &
exec twm
---------------------------------
When I do the startx command, the whole thing crashes horribly. The
following .FVWM2-error file is created:
----------------------------------
[FVWM][executeModule]: <<ERROR>> No such module 'ELF' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 'ÿÿÿƒÄèjýÿÿèU' in
ModulePath '/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 't€ù' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module '‹…ÿÿÿÆ' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 'ëv' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 'jèµýÿÿƒÄ9órÊë¶' in
ModulePath '/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 'ÆÌÂ' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module '¾Á‹ _at_ºë´&' in
ModulePath '/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module '¾ÁöDC' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 'ué1Û‰Uü€:' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 'tv' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 'uôJŠ' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module '¾Á‹5_at_ºë' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module '¾ÁöDF' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 'ÿMGFë«v' in ModulePath
'/usr/lib/fvwm2'
[FVWM][executeModule]: <<ERROR>> No such module 'täGPè+' in ModulePath
'/usr/lib/fvwm2'
----------------------------------
The /usr/lib/fvwm2 path is the correct ModulePath. But where does it get
the "ModulePath" from? Is it using the files in the /etc/X11/TheNextLevel
directory? Or is it using the system default /etc/X11/fvwm2/system.frwm2rc
file?
Any help on this would be greatly appreciated.
Carter Bond
bondl_at_unm.edu
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Sat Jul 19 1997 - 22:24:52 BST