Dear SCO Customer, The enclosed Support Level Supplement (SLS) PTF3209B, the Emergency Recovery Disk Supplement, merges the fixes from PTF3053B and PTF3209 and provides additional corrections and functionality including modifications to emergency_rec(1M) and emergency_disk(1M). Both PTF3209 and PTF3053B are superseded by PTF3209B. Note: After_installation, new emergency disks should be created with emergency_disk(1M), and a new recovery tape with emergency_rec(1M). As always, the new emergency set of disks should be tested by booting from them. Symptoms -------- When used, the recovery floppy created from an installed UnixWare 2.1 system asks for a 10-character serial number. However, the serial number (or license number) provided in the SCO UnixWare product has 14 characters. After correcting the problem with 14 character input, it was discovered the checking mechanism was old. So, even with 14-character serial number, the system would not allow a user into recovery mode. This problem was addressed in PTF3209. PTF3053B, the SCO UnixWare 'disksetup' Supplement, provided a correction to disksetup(1M) to allow support for 2 gigabyte filesystems. An integer overflow occurs when a defaults file (-d option) is used to specify the configuration of the disk when the slice size is 2097152K. (The error does NOT occur when the slice size is smaller than 2097152K or if it is specified in M, m or W. See the disksetup(1M) manual page for description of size specifiers). Emergency recovery tapes contain defaults files to re-create your slice information on recovery. These defaults files use the K (Kilobytes) size specifier and could therefore cause a misconfiguration of the disks. The disksetup binary is copied to the emergency recovery tape when emergency_disk is invoked. You are therefore advised to create a new emergency tape after installation of PTF3209B. Other corrections are detailed further under General Description below. SOLUTION SPECIFICS ------------------ General Description ------------------- 1) The user interface has been changed to accept 14-character serial number input. Also, the serial number checking mechanism has been changed to cover 14 characters, 10 characters, and 9 characters. The last two cases are for backward compatibility and Compaq SmartStart respectively. 2) The parsing of /etc/vfstab was incorrect. emergency_rec(1M) assumed tabs were always used as separators; some users tend to use spaces when manually editing this file. Therefore, when creating a recovery tape the disk layout files (stored in the first archive on the tape) were corrupt. The tape would appear to be created successfully, but a restore would not be possible. 3) emergency_rec(1M) needs to start NWS (if configured) to allow the archiving of the extended file attributes. The server was being stopped too soon, causing cpio(1) to generate screens of errors. The recovery tape could not be used for a restore, although this would not be obvious to a user when creating the tape. 4) emergency_disk(1M) had a problem with handling the working directory. This could destroy the contents of mounted filesystems. 5) A new option, '-d', dd(1M)s each filesystem to tape. This is needed for the 'sfs' filesystem when a root hard disk greater than 2GB is being used. NOTE: When restoring from a '-d' recovery tape, the target disk(s) _must_ be of the same geometry as the original[s], and installed on the same controller/bus/target/device/lun number. Also, as dd(1M) is being used, there cannot be a prompt to insert a second tape. Therefore, the tape must have enough capacity for the operation or emergency_rec(1M) will fail. 6) When booting from the emergency disk set, a sane hard disk would occasionally be reported as 'not sane'. This was a string compare error and has been corrected. 7) After restoring a system, disksetup(1M) would not be present. This has been addressed in PTF3209B. 8) Creation of emergency tape would fail if /tmp were a separate, on-disk filesystem (that is, not memfs), which is corrected in this PTF. Software Notes and Recommendations ---------------------------------- PTF3209B should only be installed on these releases: SCO UnixWare Application Server Release 2.1.0, 2.1.1, 2.1.2 SCO UnixWare Personal Edition Release 2.1.0, 2.1.1, 2.1.2 Installation Instructions ------------------------- 1. Become root and create a new directory by typing the following: $ su Password: # mkdir /tmp/pkg # chmod 700 /tmp/pkg # cd /tmp/pkg 2. Download the ptf3209b.Z and the ptf3209b.txt files to the newly created /tmp/pkg directory on your machine. 3. Read the Release Notes contained in the ptf3209b.txt file. 4. Uncompress the file and add the package to your system using these commands: # uncompress /tmp/pkg/ptf3209b.Z # pkgadd -d /tmp/pkg/ptf3209b Note: After_installation, new emergency disks should be created with emergency_disk(1M), and a new recovery tape with emergency_rec(1M). As always, the new emergency set of disks should be tested by booting from them. Removal Instructions --------------------- 1. Become root and remove the package by typing these commands: $ su Password: # pkgrm ptf3209b If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier. We appreciate your business. SCO Support Services