--------------------------------------------------------------------------------
EXECUTING THE OPENLINUX 2.4.000.7 UPDATE SCRIPT                    February 2000

This section explains how to execute the OpenLinux 2.4.000.7 update script.
Before you execute the update script, you should read this entire document.

This document includes the following information:

- A word about the new version number scheme
- Obtaining the latest update script
- New features in the update script
- Executing the update script


A WORD ABOUT THE NEW VERSION NUMBER SCHEME
==========================================
You may have noticed that some version numbers have changed with this release
of the update.col script. The new update script is called "2.4.000.7"

Here's a description of each field in the version number (for example,
"update.col-2.4.000.7"):

- The First Number field indicates the major release.

- The Second Number field indicates the minor release.

- The Third Number field indicates the maintenance release.

- The Fourth Number indicates the iteration version of the script.

NOTE: To determine the version of a certain "update.col" script, enter
"./update.col --version".


OBTAINING THE LATEST UPDATE SCRIPT
==================================
To obtain the latest version of the update script, visit Caldera's FTP site at
ftp://ftp.calderasystems.com/pub/openlinux/updates/.


NEW FEATURES IN THE UPDATE SCRIPT
=================================
This update.col utility supports updating from COL 2.2 to newer OpenLinux
release levels.

Examples of updates:

        OpenLinux-2.2-7 => OpenLinux-2.4-7
        ...

An update engine embedded within the script dynamically builds a script for
your machine based on your update path.


EXECUTING THE UPDATE SCRIPT
===========================
WARNING! Please follow these steps exactly.

 1. Back up your existing system. It is always a good idea to back up your
    system before updating software, especially since the update.col script 
    is a complex procedure.

 2. Log in locally as the root user.

    NOTE: To avoid problems with rebooting, don't log in as the superuser (su)
    or as the root user over a network.

 3. Insert the OpenLinux CD you are updating to.

 4. Mount the CD-ROM (for example, enter "mount /mnt/cdrom").

    All packages must reside in /mnt/cdrom/Packages/RPMS. In the case of a
    security update distributed on diskette (as with OpenLinux Standard 1.1),
    /mnt/floppy/security/RPMS is included in the package path and may be used
    if the diskette has been mounted with the "mount /mnt/floppy" command.

    If update packages reside in directories other than what was specified above
    on the CD-ROM or diskette, see the usage notes by entering
    "/sbin/update.col --help".

 5. Copy the "update-2.4.000.7.tgz" file to the root directory (/) of your
    filesystem (not "/root").

 6. To extract the contents of the archive:

    a. Access the root (/) directory (for example, enter "cd /").

    b. Enter "tar zxvf update-2.4.000.7.tgz", where "2.4.000.7" is the
       current update script. The "update.col" script is added to the /sbin
       directory.  Do not move the script! The script MUST reside in the root
       filesystem partition for the update to function properly.

 7. Have all users log off the system you're updating, then change to
    runlevel 1 by entering "/sbin/telinit 1".

 8. To show the steps that will occur when you execute the script:

    a. Enter "/sbin/update.col --test". The "update.script" file is added to
       the "/tmp/update.$PID" directory, where "$PID" is the process ID number
       under which the test was run.

    b. Verify the "update.script" file in the "/tmp/update.$PID" directory,
       where "$PID" is the process ID number under which the test was run. Note
       any  problems that may conflict with your system's current configuration,
       such as modifications to packages shipped by Caldera.

       NOTE: The update script should not replace any custom updates you made.

 9. To execute the update script, enter "/sbin/update.col".

    Log files will be kept of what was done. The log files appear in the
    "/tmp/update.$PID" directory, where "$PID" is the process ID number under
    which the test was run.
 
    If the system detected the update, you are prompted to reboot the system.

10. If you're asked if you want to reboot the system, enter "yes". If you're
    not prompted to reboot the system, enter "/sbin/reboot" or enter
    "/sbin/reboot -f".

    If any e2fsck filesystem errors appear after the system reboots, disregard
    them. These errors are caused by temporary files and the filesystem
    automatically repairs them.

11. Check the log file.

    If you encounter problems with this update, check the "update.log" file in
    the "/tmp/update.$PID/update.log" directory, where "$PID" is the process ID
    number under which the script was run.