========================================================================== The checksum's (found through sum -r) of the files that you have received (other than this README) are as follows: 15104 1074 patchSG0003654.cadmin_sw 64120 4 patchSG0003654.idb 24451 12 patchSG0003654.eoe1_man 07943 6 patchSG0003654.eoe1_sw 45591 135 patchSG0003654.eoe2_sw 54103 7 patchSG0003654.cadmin_man 13216 11 patchSG0003654 ========================================================================== - 1 - 1. Patch_SG0003654_Release_Note This release note describes patch SG0003654 to IRIX 5.3. Patch SG0003654 replaces patches SG0000168, SG0000617, SG0000708, SG0001048, SG0001096, SG0001546, SG0001774, and SG0003191. 1.1 Supported_Hardware_Platforms This patch contains bug fixes for all platforms. 1.2 Supported_Software_Platforms This patch contains bug fixes for the Object System and Removable Media Software (version 1021572036) on a system running IRIX 5.3. The software cannot be installed on other configurations. 1.3 Bugs_Fixed_by_Patch_SG0003654 This patch contains fixes for the following bugs in IRIX 5.3. Bug numbers from Silicon Graphics bug tracking system are included for reference. Patch 3654 fixes: o Bug #559765-objectserver security problem. Patch 3654 replaces and rolls up: o Patch 3191, which fixes: o Bug #588005-mediad security problem. (Note: a complete fix for bug #588005 with respect to ISO9660 CD-ROMs also requires a mount_iso9660 fix contained in patch 3189.) o Patch 1774, which fixes: o Bug #352932-Patch 1096 breaks 'cformat' o Patch 1546, which fixes: o Bug #398686-Mediad does not support Teac SCSI floppy disk drives. o Bug #387220-Patch 1096 objectserver reports "Unknown Graphics" on Indigo2 IMPACT systems. - 2 - o Bug #335037-desktop does not recognize cdrom when patch 708 is installed. o Bug #285400-Objectserver core dumps on machines with mixed speed IP19 cpu boards. o Bug #279679-WD95 SCSI adaptor driver prints many selection timeout messages on console. o Patch 1096, which fixes: o Bug #324149-cdman not working with patch 708. o Patch 1048, which fixes: o Bug #324141-security hole in objectserver. Objectserver not keeping in synch with changes to /etc/passwd. o Patch 708, which fixes: o Bug #292017-Objectserver and Mediad do not support PC cards. o Patch 617, which fixes: o Bug #279520-Objectserver hangs in an infinite loop when system time moves backward. o Bug #277297-Objectserver reports 2 gigabyte disks are more than 100% full. o Bug #270358-File Monitor can't talk to objectserver. o Bug #265544-Objectserver does not start reliably when system is booted. o Bug #250002-Objectserver process grows continuously when it can't find a directoryserver. o Bug #206033-Removable media device icons stop displaying state of device. o Patch 168, which fixes: o Bug #207263-Mediad code assumes controller and scsi id are only 1 digit each. - 3 - 1.4 Subsystems_Included_in_Patch_SG0003654 This patch release includes these subsystems: o patchSG0003654.cadmin_man.cadmin o patchSG0003654.cadmin_sw.dso o patchSG0003654.cadmin_sw.objectserver o patchSG0003654.cadmin_sw.objectserver o patchSG0003654.eoe1_man.unix o patchSG0003654.eoe1_sw.unix o patchSG0003654.eoe2_sw.rm_media 1.5 Installation_Method After installation is complete, rebooting the system is recommended. Minimally, running these commands is required: o /etc/init.d/cadmin stop o /etc/init.d/cadmin start 1.6 Installation_Instructions Because you want to install only the patches for problems you have encountered, patch software is not installed by default. After reading the descriptions of the bugs fixed in this patch (see Section 1.3), determine the patches that meet your specific needs. If, after reading Sections 1.1 and 1.2 of these release notes, you are unsure whether your hardware and software meet the requirements for installing a particular patch, run inst. The inst program does not allow you to install patches that are incompatible with your hardware or software. Patch software is installed like any other Silicon Graphics software product. Follow the instructions in your Software Installation Administrator's Guide to bring up the miniroot form of the software installation tools. Follow these steps to select a patch for installation: - 4 - 1. At the Inst> prompt, type install patchSGxxxxxxx where xxxxxxx is the patch number. 2. Initiate the installation sequence. Type Inst> go 3. You may find that two patches have been marked as incompatible. (The installation tools reject an installation request if an incompatibility is detected.) If this occurs, you must deselect one of the patches. Inst> keep patchSGxxxxxxx where xxxxxxx is the patch number. 4. After completing the installation process, exit the inst program by typing Inst> quit 1.7 Patch_Removal_Instructions To remove a patch, use the versions remove command as you would for any other software subsystem. The removal process reinstates the original version of software unless you have specifically removed the patch history from your system. versions remove patchSGxxxxxxx where xxxxxxx is the patch number. To keep a patch but increase your disk space, use the versions removehist command to remove the patch history. versions removehist patchSGxxxxxxx where xxxxxxx is the patch number. 1.8 Known_Problems This patch introduces some minor breakage of transferable administrative privileges for non-root users. - 5 - For example, if privileged users other than root have been added through the User Manager, attempts by an unprivileged user to perform administrative tasks (such as adding or removing user accounts) may fail with the message "Error: cannot access the object" even though the unprivileged user supplies a privileged user's name and password. Administrative tasks can still be performed by logging in as a privileged user, or by providing the root password. Similarly, if an unprivileged user runs the System Manager, chooses the "Change Privilege Level" item from the File menu, and enters a privileged non-root user's name and password, the System Manager will present the incorrect message "You already had these administrator privileges"; subsequently, when performing administrative tasks, the user will be asked for a privileged user's name and password, which still will not allow the unprivileged user to perform some tasks. Again, the administrative tasks can be performed by logging in as a privileged user, or by providing the root password.