Computing Topics --> Open Computer Labs at Maryland --> All Computer Lab Pages --> How To Change Your Window Manager On WAM Or Glue -->

How To Change Your Window Manager On WAM Or Glue

"fvwm2" is the default Window Manager running under the X windows display manager, "xdm" on Workstations at Maryland (WAM) and Glue is "fvwm2". While this will provide a well-supported environment for working in an X display while logged onto WAM or Glue, there are also other Window Managers available. This document will cover a few of the more popular ones; other documents may come available in the future. Any Window Manager installed on WAM and/or Glue should work, but your mileage may vary; some are fully supported (like "mwm2"), others are installed 'as is' and may not work exactly as expected (like "mwm2").

Essentially you only need to define which Window Manager you want to use by specifying a "WINDOW_MANAGER" environment variable in the .environment file (in your home directory). Some Window Managers, however, need to have access to additional resources that are not in the default WAM/Glue path. In this case, you will need to set the apropriate pathnames to the additional information, usually done via tap.

How to change your Window Manager to the Motif Window Manager (mwm)

To run Motif Window Manager ('mwm') on a Glue or WAM workstation, you should be able to put the following into your ".environment" file:

 
    eval `/usr/local/scripts/twig motif`
    eval `/usr/local/scripts/twig motif2`
    setenv WINDOW_MANAGER /afs/glue.umd.edu/software/motif-1.2.2/bin/mwm

This, however, may not work on all platforms. Platform-related problems may stem from an entry missing from the directory:

    /afs/glue.umd.edu/software/motif-1.2.2/.bin

There are three Sun platforms defined for running 'mwm', with links for nine others to those basic three. If you have problems getting 'mwm' to run, check to make sure your machine type is reflected in the files.

To do this, type:

    uname -m

to determine the hardware type, then:

    uname -a

to determine the OS type. Here's an example:

    altair> uname -m
    sun4u
    altair> uname -a
    SunOS altair.umd.edu 5.5 Generic_103093-13 sun4u sparc SUNW,Ultra-1
    altair>

The OS type is in the third column of output from the 'uname -a' command. The current likely values are "4.1.1", "4.1.4", "5.4", "5.5" and "5.5.1". The first two are SunOS versions, the latter three are Solaris versions. (Solaris 2.4 == SunOS 5.4; Solaris 2.5 == SunOS 5.5.)

From the first command, we see the hardware type is "sun4u", and from the second, we see that the OS is Solaris 2.5 (which is SunOS 5.5 - note the third value).

Now look in the directory:

    /afs/glue.umd.edu/software/motif-1.2.2/.bin

and see if there's a file or link for "sun4u_55". We see there is, so that should work.

If you find a combination that's not in the directory, it's probably due to the fact that the link has not been created.

Please contact the Office of Information Technology (OIT) Help Desk if you have any questions.

How do I:
How are we doing? Comments on this page?
Office of Information Technology
Office of Information Technology Help Desk Web Site University of Maryland Web Site Office of Information Technology Web Site