PROTOR Knowledge Base

PROTOR Redhat: Setting background images for PROTOR

Author:	Don Davies
Date:	20-Jan-2003

Setting GRUB Splash Screen

It is possible to set the background image displayed when selecting the image to boot when using the GRUB boot loader. The image file to load is specified within the GRUB configuration file /boot/grub/grub.conf. Typically this image has a size of 640x480 pixels and is a gzipped XPM image. A suitable screen for use with PROTOR systems may be found in :

         /home/protor/bmp/splash-prosig.xpm.gz

Display Manager Background Image

During login initialisation for the various display managers available under Redhat( i.e. either xdm, gdm or kdm) a background image file or logo may be specified. For all display managers the background image displayed is controlled by the script:

         /usr/X11R6/lib/X11/xdm/Xsetup_0

By default this script calls the module /usr/bin/xsri to initialise the screen and also adds the options --redhat-login which causes the redhat logo to be displayed. When accessing the system remote, especially when using a modem, the display of this logo can take a long time. For PROTOR system it is best to remove the drawing of this logo. Edit the file /usr/X11R6/lib/X11/xdm/Xsetup_0 and comment out the call to xsri.

User Background Image under FVWM95

For PROTOR we use the FVWM95 Window Manager. It is possible, under this Window Manager to set a different background image for each virtual desktop using the FvwmBacker module. Alternatively it is possible to set the image during initialisation using the xpmroot command.

Edit the FVWM95 control file .fvwm95rc or protor.fvwm95rc. Find the setup of the command InitFunction . If this doesn't aleady do so, add a line to call the module xpmroot specifying the image to load. For example:

    AddToFunc "InitFunction"    "I" Exec xpmroot /home/protor/bmp/blue-sky.xpm &
    +                           "I" Module FvwmButtons
    +                           "I" Module FvwmTaskBar

Author: D.Davies              Date: 20-Jan-2003                     Issue: 1

Return to Knowledge Base