Problem
Where can I find the OpenServer 6.0.0 Late News?
Solution
This information is available from:htp://www.sco.com/support/docs/openserver/600/600ln.htmland is detailed below:SCO OpenServer Release 6.0.0
Late NewsFirst published 20 June 2005 (Media Kit Release) Last revised 10 March 2006 (Maintenance Pack 2)
This document contains important notes, known limitations, and workarounds for SCO OpenServer Release 6.0.0 and for Release 6.0.0 Maintenance Pack 2 (MP2). You should read these sections before you begin to install either of these products.
NOTE: MP2 and other updates for Release 6.0.0 are available from the OpenServer 6.0.0 Supplements Web Page:
http://www.sco.com/support/update/download/product.php?pfid=12&prid=20.Check back here periodically. New information, including additional limitations and workarounds, is published as it becomes available.
-------------------------------------------------------------------------------Contents Late News for Release 6.0.0 Maintenance Pack 2 Late News for the Release 6.0.0 Media Kit See Also: Release Notes for Release 6.0.0 Media Kit and Maintenance Pack 2
-------------------------------------------------------------------------------Late News for Release 6.0.0 Maintenance Pack 2
Driver Installation Instructions
ftp Manual Page
OpenLDAP Documentation
PostgreSQL Notes
Bug Fix Clarifications
Driver Installation Instructions
The instructions given in the CD and online MP2 Release Notes for installing the device driver packages supplied with MP2 are incorrect. To install any of the drivers included on the MP2 CD, enter the following commands:# mount -F cdfs /dev/cd0 /mnt
# pkgadd -d /mnt/imagename.image drivernameWhere imagename and drivername are any of the following:
imagename drivername Description ahci.image ahci Updated AHCI Host Bus Adapter (HBA) driver. ide.image ide Updated IDE Host Bus Adapter (HBA) driver. nd.image nd Updated Network Driver Package.
ftp Manual Page
The manual page for ftp(TC) on the installed system does not match the ftp command delivered with MP2. The correct page is available at http://osr600doc.xinuos.com/en/man/html.TC/ftp.TC.html.OpenLDAP Documentation The OpenLDAP Administrator's Guide is available on the web in the OpenServer 6 Documentation. The OpenLDAP manual pages are available on your OpenServer 6 system. To display a list at the command line, enter "man -k ldap". To display a complete list in DocView (http://localhost:8457), select "Manual Pages", type "ldap" into the text box, check the "Search descriptions also" check box, and then select Search. You can also see the OpenLDAP manual page list on the web.
PostgreSQL Notes The PostgreSQL Upgrade Notes provided in the MP2 Release Notes refer to version 8.1.2 of PostgreSQL; they should refer to version 8.1.3, which is included in MP2. The upgrade instructions apply equally to version 8.1.3.
The command line startup interface for the previous PostgreSQL 7.4.2 release was /etc/init.d/postgres; in version 8.1.3, the command is /etc/pgsql. The command
/etc/pgsql start starts the database, and /etc/pgsql enable ensures that the database is started automatically on the next reboot of the server. Use /etc/pgsql -h to list all the options.
Bug Fix Clarifications The original bug descriptions can be found by searching the MP2 Release Notes for the reference numbers given below.
527772 -- cm_vtcld core dumps when SFNOLIM set above 32767 The only change in MP2 is to fix cm_vtcld so that it does not dump core when SFNOLIM (the number of files a process can open) is set to a value higher than 32767; this was causing several utilities, including SCOadmin, to fail. While setting SFNOLIM to a value higher than the installed maximum of 2048 is not recommended, doing so is not prevented by the kernel and should not cause a core dump. However, it remains inadvisable to tune SFNOLIM or HFNOLIM higher than 2048. The work to be able to support setting higher values of these tunables is scheduled for an upcoming maintenance pack.
-------------------------------------------------------------------------------Late News for the Release 6.0.0 Media KitHardware support Using SCO OpenServer Release 5 disks USB printers not working System performance is sluggish when configured NIC is disconnected Trouble reconnecting Intel PRO/100+ NIC to network Periodic network hangs with the Intel PRO/Wireless 2200BG NIC
Installation and Licensing Do not use Loaded Software options Network installation and netisl Set system date and time in BIOS before installing SCO OpenServer USB floppy drive not accessible during installation Creating a new UNIX partition on a disk with existing partitions
Backup and Restore Unable to create emergency recovery tape with emergency_rec
Graphical Environment X server display garbled when system enters screen saver mode Context-sensitive help for Panorama (xdt3) Desktop not working
Help and Documentation Running DocView Samba Documentation Includes Unsupported Features Apache documentation not configured Context-sensitive help for some SCOadmin managers not working
Internet and Intranet Small or Unreadable Text in Mozilla or Konqueror
Networking Changing system name causes rpcbind error Permission problems with IP Filter firewall files Valid user unable to log in to NIS client
System Management System not configured for Euro character Trouble generating 8-bit (European) characters in telnet session
Development System SCO OpenServer Release 6.0.0 Development System manual pages not configured
-------------------------------------------------------------------------------Hardware supportUsing SCO OpenServer Release 5 disks For information on using SCO OpenServer Release 5 hard disks on SCO OpenServer Release 6.0.0 systems, see the SCO OpenServer Migration and Upgrade Guide.
USB printers not working At this time, USB printer support is not functioning correctly. We are working on this problem and will post the solution here when it is available. (532127)
System performance is sluggish when configured NIC is disconnected Depending on the network adapter that you are using, you may experience sluggish system performance if you have networking configured on your system but the network cable is disconnected.
This happens because of a conflict between the system and certain network adapters when the system polls the NIC to see if the network cable is attached. This conflict can cause high levels of CPU activity, thereby impacting overall system performance.
To address this problem, modify the DLPI daemon startup script, /etc/nd, so that the dlpid(ADM) command uses the -s option. This flag controls the frequency with which dlpid polls the NIC. The default is every 10 seconds. To increase this interval, specify the desired number of seconds. For example, to change the system to poll the NIC every 60 seconds, specify:
dlpid -s 60Adjust this setting as needed to improve performance on your system. (532289)
Trouble reconnecting Intel PRO/100+ NIC to network If you are using an Intel® PRO/100+ (eeE8) network adapter in half duplex mode and you remove it from the network, your system may fail to reconnect to the network after you plug the network cable back into the NIC. This problem occurs if you are using a 10Mbps or 100Mbps network hub that has problems auto-negotiating with the eeE8 network driver.
If you encounter this problem, run the SCOadmin Network Configuration Manager and modify the Intel PRO/100+ configuration to use the ``HalfDuplex_10Mps'' or ``HalfDuplex_100Mbps'' setting instead of the ``Auto_Auto'' setting. Then reboot your system.
(532453)Periodic network hangs with the Intel PRO/Wireless 2200BG NIC If you are using the Intel Centrino PRO/Wireless 2200BG NIC with Wired Equivalent Privacy (WEP) support enabled, you may experience periodic networking hangs when transferring large files. If the ipw driver senses a hang, it attempts to restart the NIC, which usually corrects the problem.
This problem does not occur if WEP is disabled. To disable WEP, run the SCOadmin Network Configuration Manager and reconfigure your network adapter. Note, however, that disabling WEP relaxes the security of your wireless network.
-------------------------------------------------------------------------------Installation and LicensingDo not use Loaded Software options Problems have been observed when installing from loaded software using custom(ADM). It is recommended that you do not use these options until a fix is available. Instead, use media images from CD, hard disk, or from another machine on your network to install software onto your system. Should you install software using loaded images and experience problems, reinstall the software from media images. (532774)
Network installation and netisl At this time, SCO OpenServer Release 6.0.0 does not support beginning a fresh install over the network. A fresh install must begin using CD media. After the operating system, is installed and running, you can still install individual products over the network from another Release 6.0.0 machine using custom(ADM).
The netisl(ADM) manual page delivered with Release 6.0.0 is not correct and has not yet been updated to reflect how to configure an SCO OpenServer Release 6.0.0 network install server. When network installation is available, a revised manual page will be provided here. (532543)
Set system date and time in BIOS before installing SCO OpenServer To avoid the possibility of license conflicts, it is recommended that you set the correct date and time in your computer's BIOS before installing SCO OpenServer Release 6.0.0.
When you enter your SCO OpenServer license during the installation, SCO OpenServer records the license start date and time based on the current BIOS Real Time Clock (RTC) configuration. If the correct time for your area is actually earlier than the RTC configuration, and you then use the Time Zone selection screen (later in the installation) to correct the system clock, the system will wind up unlicensed.
Note that you cannot remove and reinstall your SCO OpenServer license to correct this type of license conflict. You must wait until the RTC advances to the date and time originally recorded by the installation. At this point, the system will be licensed and functional. (532459)
USB floppy drive not accessible during installation If your system contains multiple disks, you may experience a problem where a USB floppy drive is unable to read an HBA floppy diskette during installation. You might also encounter this problem on a system with a single hard drive if you have multiple USB floppy drives installed.
The simplest way to avoid this problem is to run the installation with only the primary hard drive and one USB floppy drive hooked up.
If you are unable to disable your extra hard drives, run the SCO OpenServer installation and do the following:
At the ``Load more HBA drivers'' prompt, insert the HBA diskette then press <Alt><SysReq>h to switch to the console text screen to see the enumeration of the USB floppy device. You should see:
VT0>0:0,7,0: HBA : (usb_msto,1) USB USB HBA
0,0,0: DISK : MITSUMI USB FDD 1039To determine the p0 device node that is used to access the USB floppy drive (for example, c0b0t0d0p0 or c1b0t0d0p0), run the following commands:
VT0> cd /dev/dsk
VT0> l *p0You should see:brw-rw-rw 1 root sys 7679,184 Jun 9 13:07 c0b0t0d0p0Verify that this is the correct node for the USB floppy drive by briefly opening the device and noting that the light on the floppy drive flashes and that no error message is displayed:
VT0> < c0b0t0d0p0Rename the USB floppy drive node as a c3 node:
VT0> mv c0b0t0d0p0 c3b0t0d0p0Press <Alt><SysReq><F1> to switch back to the installation.
Select Yes at the ``Load more HBA drivers'' prompt to load the HBA driver(s) from the HBA floppy diskette then continue with the rest of the installation.(532574) Creating a new UNIX partition on a disk with existing partitions When unused space exists before an existing disk partition or between existing partitions, adding a new partition from the installation's Disk Setup screen causes the starting and ending cylinder values of the adjoining partition to be re-assigned. Consequently, any data on the affected partition will become inaccessible.
To avoid this problem, press <Alt><SysReq>h on the Licensing screen to switch to the system console. At the VT0> prompt, run fdisk and define a partition that fills the unused space. Then press <Alt><SysReq><F1> to switch back to the Licensing screen and proceed with the installation.
You can now add a new partition (if still necessary) from the Disk Setup Partitions screen without affecting existing partitions and data. (531561)
-------------------------------------------------------------------------------Backup and RestoreUnable to create emergency recovery tape with emergency_rec The emergency_rec -e ctape1 command is not working properly, affecting your ability to create an emergency recovery tape.
To fix this problem, edit the /sbin/emergency_rec file and change line 412 to read:
INDEV=/dev/rdsk/${DV}p0(532582)
-------------------------------------------------------------------------------Graphical EnvironmentX server display garbled when system enters screen saver mode Sometimes when the system enters screen saver mode, the X server display can become garbled with odd white and black lines. To fix this, use <Alt><Ctrl><Fn> to switch to a different multiscreen, then <Alt><Ctrl><F2> to return to tty02 where the X server is running. Your video display should be back to normal. (531815)
Context-sensitive help for Panorama (xdt3) Desktop not working Context-sensitive help for the Panorama (xdt3) desktop is not currently working. This problem also affects context-sensitive help for some of the desktop icons, including the Accessories, Controls, Edit, Mail, System Administration, and UNIX icons.
To get help on specific aspects of the Panorama desktop, please use the DocView Search feature. (532423, 532460)
-------------------------------------------------------------------------------Help and DocumentationRunning DocView The SCO OpenServer online documentation is available via the DocView documentation server. By default, the DocView server starts automatically when the system is booted into multiuser mode.
To determine if the server is running, run /etc/docview. You can also use this command to start and stop the server.
Please note that the ``SCO OpenServer documentation'' section in the Getting Started Guide incorrectly lists the command as /usr/bin/docview.Samba Documentation Includes Unsupported Features The Samba documentation includes descriptions and manual pages for features that are not supported by Release 6. These include:
The winbindd daemon and other features related to PAM/NSS (Pluggable Authentication Modules/Name Service Switch) are not supported. PAM and NSS are not yet supported on Release 6.
The smbfs file system and related commands (smbmount, etc.) are not supported.
-------------------------------------------------------------------------------Internet and IntranetApache documentation not configured The Internet and Intranet category in the online documentation at http://localhost:8457 does not contain a link to the Apache HTTP Server documentation. To fix this problem, log in to the system as root and:
Change to the /usr/share/meta/doc/AdminHelpTopics/INThome/INTgroup/INT_apache directory.Run the following command:# doctool --remove AdminHelpTopics/INThome/INTgroup/INT_apache/INT_apache.desktopEdit the INT_apache.desktop file.Change the following line:
DocPath=/usr/share/doc/apache/docview_index.fr.htmlso that it reads:
DocPath=/usr/share/doc/apache/index.html.frChange the following line:
DocPath=/usr/share/doc/apache/docview_index.en.htmlso that it reads:
DocPath=/usr/share/doc/apache/index.html.enSave and exit the file.Run the following command:# doctool --add AdminHelpTopics/INThome/INTgroup/INT_apache/INT_apache.desktopThe ``Apache HTTP Server Documentation'' topic is now available from the Internet and Intranet category in the online documentation.
(532589)Small or Unreadable Text in Mozilla or Konqueror When the text on a web page appears too small and unclear, it is probably because of the cascading style sheet (.css file, or CSS) associated with that webpage on the server. The CSS is probably requesting the small type size. Because the browsers shipped with OpenServer do not have a default minimum font size configured, they attempt to match the point size specified by the style sheet.
Users can improve the appearance of all such web pages by setting the browser's minimum font size to 10 point or larger. If you are using Mozilla, select the following from the command menu:
Edit -> Preferences -> Appearance -> FontsIf you are using Konqueror, select: Settings -> Configure Konqueror -> Fonts
Select 10 point or larger for the minimum font size and then select OK to set the new value. (532407)
-------------------------------------------------------------------------------NetworkingChanging system name causes rpcbind error There is a problem with the SCOadmin Network Configuration Manager (netconfig) that results in the following error if you change the name of the system:
UX: rpcbind: ERROR: Could not find any loopback transport. Exiting.
To fix this problem, edit the following files:
/etc/net/ticlts/hosts/etc/net/ticots/hosts/etc/net/ticotsord/hosts
In each of these files, locate the ``RPC Hosts'' comment and ensure that the following line exists:sysname sysnamewhere sysname is the new hostname.If any of these files are missing this line, add it.
Once these files are corrected, rpcbind will be able to run successfully. (532255)
Permission problems with IP Filter firewall files Permissions on certain files that control the IP Filter firewall are set incorrectly.
To fix these permission problems, edit /etc/conf/node.d/ipf and add ``0 0 600'' to the end of each line in the file. The file should look like this when you are finished:ipf ipl c 0 0 0 600
ipf ipnat c 1 0 0 600
ipf ipstate c 2 0 0 600
ipf ipauth c 3 0 0 600
ipf ipsync c 4 0 0 600
ipf ipscan c 5 0 0 600
ipf iplookup c 6 0 0 600Then run /etc/conf/bin/idmknod to recreate the nodes. (532560)
Valid user unable to log in to NIS client If a valid distributed user account is unable to log in to an NIS client, it is possible that the account's password entry in the /etc/passwd and/or /etc/passwd.yp files have become corrupted.
To fix this problem, log in to the NIS master server as root and do the following:
Make backup copies of the /etc/passwd and /etc/passwd.yp files.
Edit /etc/passwd and locate the entry for the affected user. Check to see if there are any odd, out-of-place characters in the user's password entry. If so, delete them and then save and exit the file. Do the same thing for the /etc/passwd.yp file.
Run passwd(C) or yppasswd(NC) to update the password for the affected user.
Run the ypmake(NADM) command to rebuild the NIS database and push the updated information to your slave NIS servers and NIS clients. The affected user should now be able to log in to the NIS client.
If you are still having problems after performing the above steps, you can try to re-initialize NIS. To do this, put the system into single-user mode and run one of the following commands:
# mkdev nisor# ypinit(532389)-------------------------------------------------------------------------------System ManagementContext-sensitive help for some SCOadmin managers not working Context-sensitive help for the SCOadmin Network Configuration Manager is not currently working. Also, the Help on Keys, Help on Index, and Help on Help options for most of the SCOadmin managers are not working.
To get help on specific aspects of the Network Configuration Manager, please use the DocView Search feature. (531641, 532304)
System not configured for Euro character Because the SCO OpenServer installation uses the ISO8859-1 codeset (which does not contain support for the Euro character), you need to switch to the ISO8859-15 codeset after the installation if you want to display the Euro character.
To configure the system to display the Euro character:
Run the International Settings Manager.Select Codeset from the Settings menu.Select Internal then change the internal codeset setting to ``ISO8859-15'' and click OK.Select Codeset from the Settings menu again.
Select Console then change the console codeset setting to ``IBM858'' and click OK.In the ``Language'' field on the main window, highlight the desired language and press <Return>.In the ``Keyboard'' field on the main window, highlight the desired keyboard and press <Return>.
The supported keyboards are:ps.858.fra
ps.858.ger
ps.858.ita
ps.858.lsp
ps.858.spa
ps.858.ukd
ps.858.usaSelect Save from the File menu.Select Exit from the File menu.Reboot the system to activate these settings. For more information, see ``Selecting codesets'' in the ``Customizing locale settings'' topic, available from the System Management category in the online documentation. (532323)
Trouble generating 8-bit (European) characters in telnet session If you telnet(TC) to an SCO OpenServer Release 6.0.0 system from a European keyboard, you must use the following commands for the session or 8-bit characters (i.e, the umlaut, Euro symbol, and so forth) will not display.
Use the -8 option with the telnet command, to specify an 8-bit data path:
# telnet -8 hostnameOnce you are logged in to the telnet session, set the terminal input mode so it does not strip input characters to 7-bits by running:
# stty -istripNote that these steps also apply if you want to run a telnet session on the same system to which your European keyboard is attached. (532366)
-------------------------------------------------------------------------------Development SystemSCO OpenServer Release 6.0.0 Development System manual pages not configured Several of the SCO OpenServer Release 6.0.0 Development System manual page sections are unavailable after the Development System product is installed because of a misconfiguration problem. To fix this problem so that all of the Development System manual pages are available, complete the Development System installation and then run the following command:
# /usr/man/bin/makewhatisSee the makewhatis(ADM) manual page for more information. (532375)
-------------------------------------------------------------------------------
Copyright © 2005 The SCO Group, Inc. All rights reserved.