Below are the contents of the Readme.txt file.

This file contains instructions on how to rebuild your mvfs module for 
Red Hat 6.2, Red Hat 7.0 and Red Hat 7.1 releases while running ClearCase
V4.2

If you are running:
   Red Hat 6.2 with Linux kernel version 2.2.14-5.0, or
   Red Hat 7.0 with Linux kernel version 2.2.16-22, or
   Red Hat 7.1 with Linux kernel version 2.4.2-2
you should not have to rebuild your mvfs--the modules shipped in this
release should work as-is.

If you are running any other combination of Red Hat releases and Linux
kernel versions, you will have to rebuild the mvfs.

If you try to load the mvfs and you have errors such as:
	/lib/modules/fs/mvfs.o: unresolved symbol d_move_Rafc77e5e
	/lib/modules/fs/mvfs.o: unresolved symbol vmtruncate_R1e2bef14
	/lib/modules/fs/mvfs.o: unresolved symbol vfs_unlink_R5e6fb932
	/lib/modules/fs/mvfs.o: unresolved symbol dput_R2d62b6c1

then you will need to rebuild your mvfs.

REBUILD INSTRUCTIONS for ClearCase V4.2

After Install has completed and while you are running as the superuser:

1)  Verify that there is no mvfs.o file leftover from previous versions
    of ClearCase in the directory /lib/modules/`uname -r`/fs.  If there
    is such a file, delete it or rename it.  Otherwise, this mvfs module
    will be loaded instead of the one you create by this process.

2)  Verify that your top level linux source directory contains a .config
    file which matches your actual system configuration.  If you are running
    a kernel which you have patched, there should be one from when you last
    rebuilt your kernel.  If you are running a system with a default kernel
    from Red Hat, you may go into the configs directory and find the config
    file that matches your system and copy it into the tol level directory
    and give it the name .config.  If you are running a custom configured
    kernel, and there isn't a .config file, you will have to run 
    make xconfig or make menuconfig to regenerate your .config file.

3)  #cd /var/adm/atria/mvfs


4)  If your kernel sources are somewhere other than /usr/src/linux, edit
    the Makefile in this directory.  Change the definition of
    LINUX_KERNEL_DIR to point to the location of your kernel build directory.
    Alternatively, you can define it in the make command line.

5)  #make

    or

    #make LINUX_KERNEL_DIR=/usr/mydir/mykernelsources

6)  Restart ClearCase by running /usr/atria/etc/atria_start.

Possible errors:

If make gives errors of the sort:

Makefile:8: /usr/no_such_dir/src/linux/.config: No such file or directory
make: *** No rule to make target `/usr/no_such_dir/src/linux/.config'.  Stop.

then you did not pass a valid LINUX_KERNEL_DIR argument to the make
command: either the kernel tree that resides at that path was not
configured, or the path does not name the top of a Linux kernel build
tree.

If you get an error of the sort:


/usr/include/linux/modversions.h:1:2: #error Modules should never use kernel-headers system headers,
/usr/include/linux/modversions.h:2:2: #error but headers from an appropriate kernel-source

then the LINUX_KERNEL_DIR argument you passed was not for a kernel
source directory, but rather a set of include files for applications.
You need to use a kernel source tree to relink the MVFS module.

If the mvfs module builds and installs cleanly but you get error 
messages on your console about structure size mismatches, your kernel may
include changes incompatible with MVFS.  MVFS attempts to identify these 
cases by checking the sizes of its compiled-in data structures with the sizes 
of structures used to re-link MVFS with new symbol exports.  If there are any 
mismatches, MVFS will print them out to the console when you attempt to load 
the module, and the module load will fail.

To correct this, you need to build a Linux kernel from unmodified
sources.