Problem
What problems are fixed by Support Level Supplement (SLS) OSS706B, the OpenServer 6 Maintenance Pack 2 Supplement?
Solution
OSS706B contains the following fixes and enhancements, which were first provided in OSS706A:
1. Fixed an ODM problem which prevented the system from booting
from a second hard disk after encapsulating the root disk and
mirroring it to the second hard disk.
fz5336882. Fixed an ODM problem which prevented removing and replacing
disk drives that are part of a mirrored configuration.
fz5338933. In the XENIX emulator (xemul/xrun), fixed bugs in the dup2(S)
and rdchk(S) system calls.
fz5336664. In the XENIX emulator, modified the behavior of the system
call chsize(S) in order to allow users to work around a
problem in early versions of Microsoft Basic which may cause
some programs using the ISAM facilities of Microsoft Basic to
generate very large files with corrupt data.To enable the workaround, define an environment variable
XEMUL_CHSIZE24. This can be done in the shell with the
following commands:XEMUL_CHSIZE24=1
export XEMUL_CHSIZE24Sh or ksh users could place these lines in the .profile files in their home directories.
For system call chsize(fd, len), if XEMUL_CHSIZE24 is set in the environment, and if len > 224, and the low-order 16 bits of len are 0, then chsize will act as if len is 0 and truncate the specified file. fz533666
5. Fixed various problems in ppp. First, ppp will now support
baud rates above 38400. Second, it is no longer necessary
to disable a serial port before dialing out. Finally, the
pppframe module now handles TCFLSH ioctls(), eliminating
an error message that formerly appeared in the pppd.log file
whenever a link was disconnected.
fz533476OSS706B contains the following new fixes and enhancements:
6. An internal compiler error (ICE) in the C++ compiler detected
when porting Open Office 2.0.x has been corrected. The ICE
occurred when initializing a large, complex static const array
needing runtime results from template functions.
fz5340437. Modified the system behavior so that, by default, it will
attempt to determine at runtime whether or not an 8042
keyboard/mouse controller is present, rather than assume one
is present. Autodetection of the 8042 improves system response
on platforms which lack an 8042 controller, and in particular,
avoids temporary keyboard lockups that can occur on such
platforms immediately after certain keyboard operations such as
VT-switches or pressing the Caps Lock key.The system's treatment of the 8042 controller can be modified
by changing the value of the variable i8042_detection in
/etc/conf/pack.d/ws/space.c and then rebuilding and rebooting
the kernel. If i8042_detection is initialized to 1, which is
the default, then the operating system detects the presence or
absence of an 8042 controller at runtime. If i8042_detection
is initialized to 0, then the system bypasses the runtime
detection and always acts as if an 8042 controller is present.
If i8042_detection is initialized to -1, then the system
bypasses the runtime detection and always acts as if an 8042
controller is not present.
fz5340348. The /usr/bin/javaexec command, used by the kernel to control
Java VM invocation for first-class executables, has been
updated to handle J2SE 5.0 Java classes.
fz5340299. Provided correct routing of non-maskable interrupts (NMIs) when
hyperthreading, multicore, and/or ACPI are enabled.
fz53396910. Made various PSM-related changes as follows:a. Added support for "hybrid" ACPI/MPS system initialization, required on some platforms when hyperthreading or multicore support is enabled. Hybrid ACPI/MPS system initialization takes processor information from ACPI BIOS tables and all other platform information from MPS BIOS tables.
Specifying "ACPI=X" in /stand/boot or at the interactive
boot prompt enables hybrid ACPI/MPS initialization when
hyperthreading or multicore support is also enabled. Hybrid
ACPI/MPS initialization should be enabled only if the default
full-ACPI based initialization fails.b. Implemented dynamic PCI interrupt assignment to fix interrupt related problems seen on some platforms when hyperthreading, multicore, and/or ACPI are enabled. Observed problems included excess interrupt activity, poor device response, and device timeouts.
c. Allowed override of kernel algorithms for sorting the
processors listed in ACPI BIOS tables through the use of the
new LAPIC_SORT parameter. This is necessary on some
platforms to ensure that all logical processors can be used
even if the ACPIS BIOS tables does not list them in the
proper order.Specifying "LAPIC_SORT=Y" in /stand/boot or at the
interactive boot prompt will cause the kernel to reorder the
processors listed in the ACPI BIOS tables; "LAPIC_SORT=N"
disables that reordering. If LAPIC_SORT is unspecified,
then the kernel uses its own internal algorithm to determine
whether to reorder the processors listed in the tables.fz53392611. Fixed problems that may cause a kernel panic after hot removal
of a device.
fz53371412. The clock interrupt frequency is now configurable using a new boot parameter KHZ. The configurable values are 100, 200, 500, 1000 and 2000. The default value is 1000. Only the setitimer system call is affected, now it can give control to the application at a higher resolution. This is primarily for multimedia applications which need to gain control frequently to send data to say an audio device. fz533870
13. Implemented kernel support as necessary for Virtual Bridge's
MergePRO product, including KQEMU support.
fz53373914. Fixed an ODM problem whereby disks listed in disks.exclude file
are not actually excluded while running vxinstall.
fz53391115. Fixed an ODM problem which prevented replacing a mirrored root
disk using vxdiskadm from working.
fz53391216. Selecting the "Always Check" mount option for Veritas filesystems
using the SCOadmin Filesystem Manager caused a mount
failure, due to the vxfs version of fsck not understanding
the -a "always check" option. This problem has been fixed.
fz53390217. Selecting the "Fast Check" mount option for Veritas filesystems
using the SCOadmin Filesystem Manager caused a mount
failure, due to the vxfs version of fsck not understanding
the -f "fast check" option. This problem has been fixed.
fz53390318. mkdev hd failed on many dynamic RAID configurations when disks
are used as hot spares or combined into RAID volumes. The
problem was caused because the disk aliases become non-
sequential (disk1, disk2, disk5) and mkdev hd assumed that the
aliases will always be sequential. This problem has been fixed.
fz533954This supplement can be installed on the following SCO OpenServer releases:
SCO OpenServer Release 6.0.0 with Maintenance Pack 2----------------------------------------------------------I. Software Notes and Recommendations1. If you have any questions concerning this supplement, please contact your SCO software supplier or your SCO Support Representative.
----------------------------------------------------------II. Installation InstructionsTo install OSS706B follow these steps:1. Login as root2. Create an empty directory, such as /tmp/oss706b, to which the patch will be downloaded.
3. Download the OSS706B patch file fromhttps://ftp.scoexpert.com/openserver6/600/patches/oss706bto the directory created in step 2.
4. Run the Software Manager with the command:
# scoadmin softwareor double-click on the Software Manager icon in the desktop.
5. Pull down the "Software" menu and select "Install New".
6. When prompted for the host from which to install, choose the local machine and then "Continue".
7. In the "Select Media" menu, pull down the "Media Device" menu. Select "Media Images", then choose "Continue".
8. When prompted for the "Image Directory", enter "/tmp/oss706b" (or the directory where you placed the VOL files in step 2) and choose "OK".
9. When prompted to select software to install, make sure that
the "OSS706" entry is highlighted. Choose "Install".10. Installation of SLS OSS706B is now complete. To exit the
Software Manager, select "Exit" from the "Host" menu.11. Once the installation has completed, you can remove or
archive the downloaded patch and remove the containing
directory created in step 2.12. You will need to reboot your system for the changes to take effect.
----------------------------------------------------------III. Removal InstructionsNote: Patches must be rolled back in the reverse order in which they were installed on a per-component basis.
1. Log in as root.2. Execute the command:# scoadmin softwareordouble-click on the Software Manager icon in the desktop.
3. Highlight the "OSS706" entry.4. Pull down the "Software" menu and select "Remove Software".
5. Once the removal finishes, quit the Software Manager.
Removal of SLS OSS706B is now complete.