Novell Linux Desktop 9 Support Pack 1/AMD64 & EM64T Readme

February 11, 2005


Note:

NLD 9 for AMD64 & EM64T includes the updated packages and bug fixes included in NLD 9 SP1.

1.0 New Items for NLD 9 SP1
1.1 New Packages
1.2 Updated Packages
1.3 Known Issues Fixed
2.0 Installing NLD 9 SP 1
2.1 Hardware Requirements
2.2 Installing NLD 9 SP1
2.3 Installing NLD On an AMD64-bit Machine
2.4 Updating NLD 9 to SP1
2.5 Supported Languages
3.0 Known Issues
3.1 Detecting Monitors Correctly during Installation
3.2 Download Failed Error When Updating NLD Using Red Carpet
3.3 netapplet Incompatible with Some Wireless Drivers
3.4 MetaFrame XP Applications
3.5 OpenOffice Known Issues
3.6 iFolder 2.1.5 Issues
3.7 Accessibility Themes
3.8 Keyboard Mappings Defaults to German
3.9 Monitor Reporting Error
3.10 Power Management Issues
3.11 Printing from Firefox
3.12 Mounting Remote Windows Filesystems via the Command Line
3.13 Changing Your KDE Language When Logged Into GNOME
4.0 Evolution
4.1 Exchange Connector
4.2 Evolution Issues
4.3 Exchange Issues
5.0 International Issues
5.1 Root User Authentication to the International NLD KDE Desktop
5.2 Root User Authentication to the International NLD GNOME Desktop
5.3 International Language Dual Desktop Environment (GNOME/KDE)
6.0 Release Notes of Base System
6.1 Enhancements
6.2 Known Issues
7.0 Online Documentation
8.0 Legal Notices


1.0 New Items for NLD 9 SP1


1.1 New Packages

  • ncpfs

    Contains client and administration tools for use with Novell networks.

  • smartlink-softmodem

    Contains utilities for configuring the Smart Link Soft modem.


1.2 Updated Packages

  • Evolution 2.0.3
  • Mono 1.0.4
  • Gaim 1.0.3
  • iFolder 2.1.5
  • Firefox 1.0


1.3 Known Issues Fixed

  • RPM types are now associated with Red Carpet in all browsers.
  • Added the ability to lock the GNOME top panel (the one that has the Programs, System, and Help menus) by default. Lock and Unlock options are now available when you right-click the panel.
  • When esd is running, applications (such as RealPlay) that could not start because esd was blocking the device will now run.
  • OpenOffice.org Issues:
    • The KDE file picker now asks if you want to overwrite an existing file on Save As.
    • KDE file picker crash fix
    • Simplified Chinese characters now display correctly on screen.
    • Several Input Method issues have been fixed.
    • Right-to-left language rendering fixed in GNOME.
  • The Make Default option (Edit >Make Default) in the context menus in gnome-cups-manager no longer requires root access. Added a way to become root in order to delete a printer (Printer > Remove Printer).
  • Evolution Issues:
    • Almost the same email address are no longer considered identical.
    • Repeated saves when you have bad data in the birthdate or anniversary edit areas no longer result in double, triple, or multiple copies of the other data for the contact.
    • Date in reminder window no longer appears in UTF-8 in non-UTF-8 locales.
    • Events ending at 12:00 a.m. no longer show as ending at 12:00 p.m
    • In the calendar, the wrong alarm time is no longer displayed.
    • The task description box in the Appointment dialog box now re-sizes when the dialog box is resized.
    • Signed mail with attachments no longer displays everything with multipart/boundaries.
    • Mail is no longer shown as an attachment if some headers are upper case.
    • Moving a message from an IMAP INBOX to an IMAP folder no longer causes a crash.
    • HTML email is now rendered in the preview pane.
    • Evolution no longer crashes after viewing previously-sent email and copying a URL from it.


2.0 Installing NLD 9 SP 1


2.1 Hardware Requirements

The minimum hardware requirements for running NLD SP1 are as follows:

  • Personal computer with a Pentium* II processor or later and a bootable CD-ROM drive
  • 800 MB hard disk space (4 GB recommended)
  • 128 MB of RAM (256 MB recommended)
  • Super VGA display adapter.
  • Network card (if you will be connecting to a network)
  • USB, PS/2*, or serial mouse.


2.2 Installing NLD 9 SP1

Use the bootable CD to perform a new install of NLD SP1. To update an existing NLD 9 system to NLD 9 SP1, see 2.4 Updating NLD 9 to SP1.

You will need access to the original NLD 9 CDs or DVD in order to complete installation.

  1. Insert NLD 9 SP1 CD 1 in your drive and boot your machine.

    The kernel will load and the following dialog will appear:

    "Make sure that CD number 1 is in your drive."

  2. Insert the original NLD 9 CD 1, then click OK to run the regular installation.

  3. Complete the normal NLD installation steps, such as accepting the license agreement, and selecting a language, default desktop, and other installation settings.

    HINT:  If you get an error message during the media installation indicating that a certain file couldn't be installed, skip that file and continue to the end. Then run the update again. During the reinstall, only the skipped packages will be installed.

  4. Click Yes, Install to start the installation.

  5. Insert NLD 9 SP1 CD 1 when prompted, followed by NLD 9 SP1 CD 2.

  6. When prompted, insert NLD CD 1 again, followed by NLD 9 CD 2 and 3.

  7. Continue as usual with the installation (entering a password for root, network configuration, testing your internet connection, activating the ZENworks® Online Update Service, user authentication method, and user name and password).

    For instructions on installing NLD, see the Novell Linux Desktop Quick Start or quickstart-en.pdf at the root of the Novell Linux Desktop CD 1 or DVD.

If you have to install many machines, we recommend booting off of the SP1 CD and using a network install server.


2.3 Installing NLD On an AMD64-bit Machine

After what appears to be a successful installation of NLD on an AMD64 bit machine, the operating system freezes on init. Setting the following kernel parameter provides a workaround for this issue:

acpi=off


2.4 Updating NLD 9 to SP1

You can update an existing NLD installation to NLD SP1 in two ways:

  • (Preferred) Using Red Carpet
  • (Alternate) Using the SP1 CDs or DVD


2.4.1 Updating NLD 9 Using Red Carpet

Use Red Carpet to install the packages that will update an existing NLD installation to NLD SP1. An update notice is shown only for software you already have installed that is in a channel to which you are subscribed, and for which there is a newer version than what you already have.

  1. Start the Red Carpet client:

    GNOME: Click System > Software Update.

    KDE: Click the red N on the bottom panel > System > Configuration > Red Carpet.

  2. If you are not logged in as root, enter the root password, then click OK.

  3. On the Updates tab, select one or more packages in the list of available updates.

  4. Mark the selected packages for installation by clicking the Mark for Installation button.

  5. Click Run Now to perform the update.

IMPORTANT:  In some instances, after Red Carpet finishes updating NLD to SP1, the Red Carpet daemon might consume all available CPU resouces. To resolve this issue, restart the Red Carpet daemon (rcd) immediately after the upgrade using the following steps:

  1. As root, run the following command:

    # /etc/init.d/rcd restart

  2. You might see a message box with the following message:

    "Lost contact with the daemon!"

    Do not take any immediate action. After a few seconds, the first message box should be replace by a second message box with the following message:

    "Connection to daemon restored."

  3. Click Close.


2.4.2 Updating NLD 9 Using SP1 CDs or DVD

  1. Insert the NLD SP1 CD 1 in your CD drive, then click Yes when the hardware detection notice appears.

    NOTE:   If the CD isn't autodetected, try reinserting it. If autodetect continues to fail, choose System > Administrator Settings > Software, then choose Patch CD Update.

  2. If you are not logged in as root, enter the root password when prompted.

    The YaST Online Update dialog appears.

  3. Click Next to begin the update process.

    The Download and Installation log will track update progress.

    HINT:  If you see a patch installation error message at any time during the update, click Skip Patch, complete the update, then repeat the update process to install the skipped packages. Only the skipped packages will be installed when the process is repeated.

  4. When prompted for the YOU Patch CD CD2, insert NLD SP1 CD2, then click OK.

    NOTE:  This prompt will not appear if you are updating from a DVD.

  5. Click Finish when you see Installation Finished reported near the end of the progress log.

  6. If you skipped patches, repeat this update process.


2.5 Supported Languages

The supported languages for this release of Novell Linux Desktop include English, French, German, Italian, Spanish, Brazilian-Portuguese, Chinese-Simplified, Chinese-Traditional, and Japanese.


3.0 Known Issues


3.1 Detecting Monitors Correctly during Installation

In some cases, monitors are not being detected correctly when NLD is installed to a computer that is sharing a monitor through a switch box. This has also been shown to prevent the graphic mode of YaST from starting. In less severe cases, the installation of NLD is successful, but the monitor is not detected and defaults to a resolution of 640 x 480.

If you are using a switch box and get an X server error, try installing while using a dedicated monitor with the computer you are installing to.

If you have installed successfully but a generic monitor has been installed and the resolution has defaulted to 640 x 480, you must manually identify your monitor and reset the resolution.


3.2 Download Failed Error When Updating NLD Using Red Carpet

Occasionally, when updating NLD using Red Carpet, the following error appears:

Download Failed, IO Error

To work around this issue, close the error message and click Refresh on the Red Carpet toolbar. Then click Run Now again and the update transaction should resume.


3.3 netapplet Incompatible with Some Wireless Drivers

The netapplet program is incompatible with some wireless drivers.

  • Some Airo network cards or their drivers are incapable of measuring the strength of wireless access points. For those cards, netapplet displays the strength of the access points as zero.
  • Some Atheros network cards or their drivers are incapable of detecting when the current access point has gone away. For those cards, netapplet is not able to intelligently fall back on another access point.
  • Some Orinoco network cards or their drivers are incapable of scanning for access points. For those cards, netapplet is not able to provide a list of available access points. To switch networks, type the network name into the field after clicking "Other..."


3.4 MetaFrame XP Applications

MetFrame XP NFuse/Presentation Server applications are not, by default, associated with the Citrix ICA Client. The associated application is: /usr/lib/ICAClient/wfica


3.5 OpenOffice Known Issues

  • Evolution / LDAP integration can cause long application delays for unresponsive servers.
  • OpenOffice won't open password protected files.


3.6 iFolder 2.1.5 Issues


3.6.1 General Issues

  • Do not use special characters such as " ` \ * in files or directory names in an iFolder directory.
  • If the iFolder location is a remote filesystem, then it should be in the user's home directory.
  • iFolder crashes if the Conflict bin screen is closed when it is empty.
  • At times, the iFolder Client might crash while restoring a file from conflict bin.
  • If you create a FAT32 partition and share the iFolder store from Windows and Linux on this partition (thus eliminating the need to duplicate data), iFolder corruption could occur.


3.6.2 Sync Related Issues

  • If a user has read access for a file but read and execute permission for the directory, the file and directory are synchronized.
  • If there are two files or directories with the same name, but in different cases, the synchronization behavior is not known. For example, if the files with the names doc1 and DOC1 exist, then the synchronization behavior is not known.


3.6.3 iFolder Places .desktop file in ~/Desktop Instead of an Actual Link

iFolder uses a .desktop file to represent iFolder on the desktop. Because of this, some programs will not recognize iFolder on the desktop. If you want something that will be visible in file selectors, create a symlink in ~/Desktop and remove the iFolder .desktop file.


3.6.4 Running the iFolder Client While Logged In With a Local User ID Containing Uppercase Letters

If you log in to a local Linux workstation with a username that contains uppercase letters then try to run the iFolder client, you might get an Invalid Port = 0 error. When you create your username, YaST warns you that some e-mail systems might have issues with usernames that contain uppercase letters, but it will still let you create the username.


3.7 Accessibility Themes

Certain accessibility themes will change fonts when selected in the theme selector. To fix this, click System > Personal Settings > Fonts and return the fonts to your desired settings.


3.8 Keyboard Mappings Defaults to German

Under certain obscure circumstances, even if during installation you selected the English (US) keyboard type, keyboards will appear in German. To fix this, change the keyboard type to English (UK).


3.9 Monitor Reporting Error

With some monitors, you might receive the following warning dialog:

"Your monitor didn't report its X- and Y-Size, this might cause display problems like unreadable fonts."

This is generally harmless and you can ignore it.


3.10 Power Management Issues


3.10.1 Suspending a Laptop

With the new kernel 2.6, standby/suspend is now supported with ACPI. Note that this feature is still experimental and is not supported by all hardware. To use it, you need the powersave package. Further information about the package can be found at /usr/share/doc/packages/powersave. A graphical front end can be found in the kpowersave package.

To suspend a laptop, perform the following steps:

  1. mv /etc/sysconfig/powersave/common /etc/sysconfig/powersave/common.orig

  2. cp /usr/share/doc/packages/powersave/contrib/common_ACPI\ /etc/sysconfig/powersave/common

  3. sed -i \ 's/DISABLE_USER_SUSPEND=no/DISABLE_USER_SUSPEND=yes/' /etc/powersave.conf

  4. rcpowersaved restart

You can use the following command (which you can run as a regular user) to test if it works:

powersave --suspend

NOTE:  You might see warning messages printed on the screen, but you can ignore them.

If you are using GNOME, right-click on the batt-stat applet and choose "Suspend Computer..." to do the same thing.


3.10.2 powersave Daemon Causes Machine to Lock Up

Certain VIA Ezra CentaurHauls processors and their associated south bridges can result in machine lock up in certain circumstances, primarily those related to power management. Disabling the powersave daemon might provide a workaround. Contact your hardware vendor for a possible hardware or BIOS upgrade.


3.11 Printing from Firefox

Firefox outputs Postscript Level 3 when printing. Some older printers cannot handle Level 3. If you get an error page from the printer saying that the Postscript interpreter in your printer is older than the version required, you need to modify your printer configuration.

Select a filter that will convert the output from Firefox to either Postscript level 2 or 1 depending on what you printer can handle. You can do this in the specific printers Properties. Change the "GhostScript pre-filtering" option to "Convert to PS level 2." Try changing it to "Convert to PS level 1" if you still get the same error.

Some printer drivers do not have this option. If the one you are using does not, try a different driver for you printer. If all else fails, use the Generic Postscript printer driver.


3.12 Mounting Remote Windows Filesystems via the Command Line

The following item only pertains to you if you are mounting remote Windows filesystems directly, via the command line. The common manner of using Windows shares---from your desktop---is unaffected by the following.

The preferred filesystem when using the mount(1) command to mount a remote Windows share is "cifs" instead of "smbfs," which is not supported. To mount a remote Windows share from the command line, use the following syntax:

mount -t cifs [-o <options>] '//server/share/' mount-point

For example:

	mount -t cifs '//monopoly/c$' /media/windows

This will mount the "c$" share at "/media/windows" on the "monopoly" machine via CIFS.


3.13 Changing Your KDE Language When Logged Into GNOME

When using KDE applications when you are logged into GNOME (including the NLD Help Center, CD burning tool, and Run as Root dialog), the application uses the language set in KDE. This defaults to the language chosen during installation.

To change the default language for the entire system, run YaST (System > Administrator Settings in GNOME.). Click System > Choose Language. This change is persistent across reboots and across all users, but can be overridden by individual user selections.

To change this for the current user when logged into GNOME, run kcontrol (using the terminal or System > Run Program). In the KDE Control Center, click Regional & Accessibility > Country/Region & Language. Add the language you want to use to the top of this list. If the language you want to add is not present in this list, you must first install the kde3-i18n package corresponding to this language.


4.0 Evolution


4.1 Exchange Connector

The Exchange Connector enables you to connect Evolution to Microsoft* Exchange. Novell Linux Desktop includes Exchange Connector 2.0.


4.1.1 Exchange Connector Version

In order to use the Exchange Connector with Evolution, you must install version 2.0 for both the Exchange Connector and for Evolution. The Exchange Connector is included with NLD, but is not part of the base installation.


4.1.2 Exchange Connector Requirements

The Exchange Connector works with Exchange 2000 and Exchange 2003. In addition, it requires that Outlook* Web Access be enabled.


4.2 Evolution Issues


4.2.1 No Support for Inline PGP or GPG

Currently there is no support for messages that use PGP/GPG encoding in the text/plain part of a message. However, Evolution does support PGP/GPG when a message has its own specific MIME type.


4.2.2 Evolution Might Become Unresponsive When Loading a Remote Calendar

When loading a remote calendar, Evolution might become unresponsive.


4.2.3 Using the "Show Only Subscribed Folders" Setting

If you toggle the "Show only subscribed folders" setting when editing an IMAP account, you must restart Evolution in order for the setting to take effect.


4.3 Exchange Issues


4.3.1 Authentication in Calendar/Tasks/Contacts Components

If the Remember Password option is not enabled, you must authenticate either through the Exchange Component or the Mailer Component before using the Calendar/Tasks/Contacts Components.


4.3.2 Exchange Component Required for Folder Operations

You cannot use folder operations such as Create/Delete/Modify for Calendar/Tasks/Contacts in a component other than the Exchange Component.


4.3.3 Authentication Failures to Exchange

If the Exchange server is restarted when connected to Evolution, you might receive authentication failures. To resolve the problem, enter evolution --force-shutdown at the prompt, and then restart Evolution.


5.0 International Issues


5.1 Root User Authentication to the International NLD KDE Desktop

Authentication to the international KDE desktop with root user credentials results in several applications reverting to U.S. English. Examples include Red Carpet, Sax2, and Novell iFolder. This functions by design as the root LANG environment variables are unassigned by default in NLD. This system default is required to ensure that all third-party services function correctly.

HINT:  Launch an instance of the shell and input the locale command to view the default root LANG environment variables.

Perform the following steps to set the locale environment variables for root to be identical to that of the other users.

  1. To start YaST, click the red N on the bottom panel, then click System > YaST.

  2. In YaST, click System > Choose Language > Details.

  3. In the Locale Settings for User Root drop-down list, click Yes.

  4. Click OK > Accept > Close.

  5. Reauthenticate to the KDE desktop with root user credentials.


5.2 Root User Authentication to the International NLD GNOME Desktop

The LANG environment variables are unassigned when authenticating to the international NLD GNOME desktop with root user credentials. The international GNOME desktop resources can be invoked manually by performing the following steps.

  1. Click the Language menu displayed on the GNOME Login dialog.

  2. Click the required language, then enter the root username.

  3. Enter the root password in the password input field.

  4. Choose to apply these language settings Just For This Session or Make Default by selecting the appropriate option.

    The international GNOME desktop resources appear when authenticated as the root user.

Failure to employ this language selection will result in the display of the U.S. English GNOME desktop


5.3 International Language Dual Desktop Environment (GNOME/KDE)

The dual installation method facilitates the display of the international GNOME and KDE desktops when authenticated as any user, including root.

If a dual desktop machine is mandatory, perform the following steps when commencing the installation of NLD:

  1. Follow the installation as normal until the Select Your Default Desktop installation window appears, then click the GNOME radio button.

  2. Click Change > Software on the Installation Settings screen.

  3. Click Detailed Selection, then click the checkbox next to KDE - The KDE Desktop.

    All additional options should remain unchanged.

  4. Click Accept and then proceed with the installation in the typical manner.

    Upon completion of the installation, the authentication dialog appears.

  5. Click Sessions and note the availability of both the GNOME and KDE desktops.

  6. Click the required desktop and authenticate using the appropriate login credentials.

    The international GNOME and KDE desktops will now be available, irrespective of the user credentials (root/non-root) used for authentication.


6.0 Release Notes of Base System


6.1 Enhancements


6.1.1 Installation / YaST2

  • Updated sax2 monitor database.
  • Added support in YaST partitioner for disks with size > 2 TB.
  • Added 'netwait=N' option to wait N seconds after network setup.
  • Added kernel parameter "ide=noraid" to prevent IDE drivers which are compiled into the kernel to initialize IDE RAID devices. You must use this option to enable the modular LSI MegaIDE controller.
  • Added command line support for samba-server BackendHandler.
  • Added hooks for installing Novell Open Enterprise Server.
  • Made sure that configurations stored in LDAP will also work with Novell eDirectory.
  • Fixed the cd-creator module.
  • The following YaST modules had smaller bug fixes:
    • yast2-bootloader
    • yast2-country
    • yast2-ldap-server
    • yast2-storage
  • Fixed several problems with Asian font support.
  • Improved support for Asian input methods (ami, scim).
  • Several bug fixes to RPM including relocations and database locking.
  • Added installation support and translations for traditional Chinese.
  • Added support to cache an installation source.

    This helps to, for example, insert CDs only once during installation as all needed RPMs from this source will be copied into an installation source cache.

  • Added dialog to allow assigning PCI IDs to drivers.

    This enables us to teach a driver about additional PCI IDs it is able to handle as well, because often an existing driver works well with new hardware released later but does not know it because the PCI IDs are unknown to the driver.

    This information will then be used during installation but also persist in the installed system.


6.1.2 Platforms / Hardware / Drivers

  • Introduced the concept of "cloned" drivers to minimize impact on HW certifications.

    We have been discussing how to best solve the dilemma of extending the hardware support with driver updates during the maintenance of a product while at the same time minimizing the effort for new or re-certifications of hardware.

    The best compromise we found was the following:

    • In case only very few HW certifications are affected default to update the driver in case it provides significant additional hardware support or value
    • In case many HW certifications would be affected keep the old driver <DRIVER> untouched and add a "clone" <DRIVER>-new using the latest version but only serving the new PCI IDs. This is achieved by removing the PCI IDs which exist in <DRIVER> from the <DRIVER>-new in order for them to be disjunct, which will automatically ensure the right driver gets loaded.

    Furthermore, we have introduced a new YaST dialog which will allow to "map" additional PCI IDs to a driver. This both allows teaching any driver about new PCI IDs, and forcing the use of the new driver for the old PCI IDs.

  • Support many new hardware components via driver and PCI ID updates:
    • Cloned tg3-new with version 3.10 to support Broadcom 5721 and 5751.
    • Cloned bcm-new with version 7.3.5 to support Broadcom 5721.
    • Updated e1000-new with version 5.3.19 to support one new PCI ID.
    • Updated ixgb to version 1.0.82 to support 10 GB Ethernet.
    • Updated ipr to version 2.0.10.1 to support new RAID types.
    • Updated IBM ServeRAID driver ips to 7.10.18 to fix bugs.
    • Updated s2io driver to version 1.7.5.1.
    • Updated qlogic to version 8.00.00 to use official release which is better and binary compatible to version 8.00.00b14 which was used in SLES 9 GA.
    • Updated megaide to version 5.07r to support LSI controllers.
    • Updated megaraid2 to version 2.20.4 for new hardware support.
    • Updated cciss driver to version 2.6.4 to support SAS.
    • Updated gdth to version 3.04 for new hardware support.
    • Updated Emulex lpfc driver to version 2.10g for bugfixes.
    • Added driver jsm version 1.1 to support Digi Neo PCI serial cards.
    • Updated avm_fcdsl driver to support Fritz!Card DSL USB analog driver and Fritz!Card DSL USB 2.0 driver.
    • Updated avmfritzcapi to support new Eumex devices.
    • Included support for Intel i915 chipset (hwinfo, sax2, xf86).
    • Enhanced driver update dialog to also support USB disks/sticks.
    • Fixed 4-port SATA support in the ICH6 driver.
    • Updated MPT fusion driver to version 3.01.14.23.
    • Fixed aic7?xx driver probe info.
    • Added Altix system controller communication driver.
    • Cloned aic79xx-new with version 2.0.12 to support AIC7901 and 39320.
    • Added Qlogic iSCSI support (qla4xxx).
    • Added patches to Infiniband Gen1 code.
    • Backported dpt_i2o from 2.6.8.
    • Updated aacraid driver to version 1.1.2-lk2 from 2.6.9.
    • Added TIO support for SGI Altix.
  • Fixed files > 2 GB in isofs.
  • Merged new Lustre hooks.
  • Updated XFS filesystem and tools to latest CVS snapshot.
  • Updated CIFS to 1.22.
  • Updated CKRM to E16.
  • Improved iSCSI and SAN/NAS support with patches from EMC, NetAPP and others.
  • Backported several NFS bugfixes from upstream/mainline kernel.
  • Backported epoll fixes from 2.6.9.
  • Integrated numerous other bugfixes from upstream/mainline kernel.
  • Several backports from upstream/mainline kernel:
    • unmap_mapping_range() from 2.6.6
    • generic_file_direct_write() and generic_file_buffered_write() from 2.6.9-rc4
    • backport mapping_mapped()
    • export sync_page_range
  • Support official variable name INSTALL_MOD_DIR in addition to our MOD_DIR.
  • Fixed hooks to enable CA.
  • Added kernel support for POSIX message queue.
  • Integrated patches to allow enabling ext3 reservation code.
  • Integrated bug fix to SHPC PCI hotplug driver.
  • Added CPU controller to CKRM.


6.1.3 Standards

  • Updated openhpi to version 1.0.2 to comply with the SA Forum HPI A.1.1 spec.
  • Added POSIX message queue support to glibc on x86 (CGL 2.0 spec Prio 1 req).

    POSIX messages queues where added to glibc after the development was stopped for librtkaio. glibc librt contains a full implementation for POSIX message queues on all architectures. librtkaio does not contain any support for POSIX message queues. Adding POSIX message queues to librtkaio is possible for x86 only. Other architectures are not possible due a change in the glibc syscall handling.


6.1.4 Availability

  • Updated multipath-tools to 0.3.6.
  • Updated device-mapper to 1.00.19.
    • Multipath enhancements
    • Added support for message passing ioctl.
  • Added multipath fixes for barrier handling.
  • With SP1 we now disabled by default the multipathing failover support in the QLogic driver as it caused many problems. We print a warning that it is depreciated and how one can still turn it on if needed using ql2xfailover=1.
  • Added patches for OES to EVMS.
  • Provide code to enable recovery from PCI EEH errors.
  • Fixed lvm2 to cope with minor device number larger than 255.
  • Fixed lvm2 to prevent hang on resizing a LV containing an active root fs.


6.1.5 Serviceability

  • Updated kdb to version 4.4.
  • Updated Linux kernel crash dump (lkcd) and lkcdutils.
  • Added powernow K8 cpufreq support for CG stepping K8.
  • Added SGI Altix hardware performance monitoring API.
  • Exported some symbols needed by ES7000 Service Processor.
  • Added tg3 ethtool stats.
  • Updated sysfsutils in udev package to version 1.2.0.
  • Added cpufreq support for SMP systems.
  • Added modular kdb support for x86_64.
  • Added clustered APIC support for x86_64.


6.1.6 Scalability

  • Improved RCU scalability.
  • Fixed scalability problem in dnotify_parent.
  • Assorted scalability enhancements for big IPF machines.
  • Support SGI Altix and 512 CPUs with Linux kernel crash dump (LKCD).
  • Added CPUSET support for IPF.
  • Added scalability enhancements for big IPF machines.
  • Added PAGG support for High Performance Computing on IPF.
  • Added support for systems with many IRQ resources.


6.1.7 Performance

  • Default readahead to 512 KB (instead of 128 KB).
  • Updated schedutils to version 1.4.0 to add cpu list support.
  • Updated Performance CoPilot to version 2.4.0.


6.1.8 Security

  • Added amtu package in preparation for CC-EAL4 certification.
  • Included all security fixes released via the maintenance Web since the GA version.


6.1.9 Applications and Tools

  • Updated ypbind to version 1.18 which adds a -ping option so that the system administrator can specify the ping interval of ypbind.
  • Added linuxthreads patch to glibc to make old JVM 1.3.1 work.
  • Backported all NPTL fixes to glibc to solve deadlock problems.
  • Provided POSIX message queue support for x86 with glibc which can be used by apps now.
  • Made usage of MDNS configurable via /etc/host.conf (see man page).
  • Changed the AIO glibc interface from librtkaio to librt.

    For completeness we want to clarify that there are two different AIO interfaces: One separate from glibc, provided via the package "libaio", and one via "librt" from glibc.

    The libaio is really just a wrapper for the kernel AIO syscalls. These functions all start with io_*(). This is what most database vendors are using. This interface is not POSIX compatible, but is, for example, used by Oracle. It is contained in the package "libaio" on SLES 9. This has nothing to do with glibc and will not change for SP1.

    Then we have librt provided by glibc, which contains a set of aio_*() functions defined by POSIX. There are two different implementations of this library: One fully implemented in userland (librt from glibc) and one, which tries to use the Kernel AIO interface (called librtkaio). Both libraries install as "librt" and are binary compatible. The interface expects a file descriptor, so it should be usable with everything which could be opened by open().

    The librt aio_* functionality is not really implementable in userland, this is the reason why the glibc librt does not work for most users. To solve this, there was the try to implement this functions with help of the Kernel AIO. But the kernel interface was not designed for this (kernel developers implemented it for the need of database vendors, not for POSIX nor glibc usage), as result, it does not work as expected, too, and needs much more CPU usage than the glibc librt.

    We know from bug reports from IBM, that both librt implementations (librt and librtkaio) do not work for them. Both implementations also don't pass 100% any test suite. Since librtkaio is worse by wasting a lot of CPU power, we will switch back to the standard glibc librt implementation with SP1.

    This in an internal implementation change of librt but is binary compatible to what we had in SLES 9 GA version.

  • Fixed blocking in gethostbyaddr with corrupted UDP packets.
  • Added gcc_old on i386 to support linking of old apps.
  • Fixed several Heimdal problems:
    • Correctly handle RESPONSE_TOO_BIG response from Windows kdc.
    • Fixed crash with certain versions of winbind of Samba.
    • Fixed crash in telnet used with w2k kdc.
  • Added large file support (LFS) to wget and rsh.
  • Updated parted to version 1.6.15:
    • Fixed two problems.
    • Added support for ATA over Ethernet.
    • Added support for partitioning device-mapper devices (for dmraid).
  • Added fixes for iManager to Mozilla 1.6.
  • Backported bdb backend from stable OpenLDAP release.
  • Added certificate revocation list (CRL) support for OpenLDAP.
  • Increased limits in quota package to match the fact that the kernel can support more than 256 mounts.
  • Integrated client side of ZLM 6.6 + fixes on fresh default install.
  • Included menu entry to easily start ZMD/ZLM.
  • Updated Samba to version 3.0.9:
    • Added eDirectory patch from Vince Brimhall
    • Added alias migration code from Volker Lendecke
    • More detailed info on changes/fixes comes with the samba-doc package in /usr/share/doc/packages/samba/WHATSNEW.txt.


6.2 Known Issues


6.2.1 Konqueror: kio_slp

In NLD's KDE desktop environment, the new network browser shown on the desktop can be used to display and use services based on SLP and MDNS. Apart from the service:/ URLs, the following types are also supported: slp:/ (to browse SLP services) and mdns:/ (to browse multicast-DNS services).


6.2.2 SSH and Terminal Applications

When using remote access (notably SSH, Telnet, and RSH) between NLD (in its default configuration with UTF-8 enabled) and older versions of the underlying SUSE® Linux Enterprise Server (9.0 and earlier, where UTF-8 is not enabled by default or not supported), terminal applications might display garbled characters.

This is because OpenSSH does not forward locale settings, so system defaults are used which might not match the remote terminal settings. This affects text mode YaST and applications run remotely as nonroot user. The applications run as root are affected only when the user changes the default locales for root (only LC_CTYPE is set by default).


6.2.3 Applications Using ncurses

If problems occur with ncurses-based applications running on the text console, simply issuing unicode_stop (reverting keyboard and console from Unicode* mode) should provide a fix.


6.2.4 Pthreads/Linuxthreads

SUSE LINUX 9.1/SLES 9/NLD 9 SP1 features a new pthread implementation called NPTL, which is faster and better than the old implementation called linuxthreads.

If your old program is incompatible with this new threading implementation, we also provide the old one. To switch to the old version, set the environment variable LD_ASSUME_KERNEL to 2.4.21 by using, for example, export LD_ASSUME_KERNEL=2.4.21 in bash.


6.2.5 Wireless LAN Cards

Some wireless LAN cards (PrismGT, Centrino, Atmel, ACX100) need firmware to operate. Due to licensing issues, we cannot ship these firmware binaries. Please read /usr/share/doc/packages/wireless-tools/README.firmware for information on how to obtain and install the firmware.


6.2.6 X Server Does Not Listen on Port 6000

Fresh Novell Linux Desktop installations default to a secure setup of the system to limit possible security concerns to the bare minimum. The ongoing development of the product results in improvements that are not always visible, but that are useful for security. This text is to inform you that the X Server does not listen on port 6000+/tcp any more.

The X Window System uses TCP protocol starting at port 6000, plus the display number used in the X session, to allow for a client to display its window over a network connection, thereby providing network transparency for the X Window System. While using reasonably strong authentication methods to approve or reject client connections which default to deny access to the display, the X Server still exposes port 6000+/tcp on the network. While the use of bare, unencrypted X Windows network protocol can be considered secure enough on a trusted network, it is not reasonable to even offer the service on an untrusted/hostile network environment. Therefore, the new setup defaults to not listen on port 6000+/tcp any more.

As a side effect, one of the two authentication mechanisms in X Windows, the host based authentication using the xhost(1) command, becomes nearly meaningless as only clients that make use of the (local) unix domain socket can connect to the X Server, regardless of the list of remote hosts displayed by the xhost command. The cookie-based X Windows client authentication method remains unchanged.

This means that the command xhost +<hostname> allows clients executed by users not in possession of the necessary credentials for other authentication methods can connect to the Xserver only when started locally (that is, on the same machine the X server runs on).

Network transparency is one of the key strengths of the X Window System, and despite the change in the default setup, there is no need to abstain from it. Either you revert the change on your system by changing the variable DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN in /etc/sysconfig/displaymanager, or you use the ssh command from the openssh package to log on to a remote system. The ssh utility allows for the forwarding of X client connections through the encrypted ssh connection, without the need to set DISPLAY variables or the use of the xhost command. The use of ssh with X11 client connection forwarding is the recommended method to make use of the network transparency of the X Window System.


7.0 Online Documentation

For the Novell Linux Desktop online documentation, see http://www.novell.com/documentation/nld/index.html.

For the most recent NLD SP1 readme file, see http://www.novell.com/documentation/nld/readme/nld_readme.html.


8.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

You may not use, export, or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

Copyright © 2004-2005 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

Novell, NetWare, Red Carpet, iFolder, ZENworks, and GroupWise are registered trademarks of Novell, Inc. in the United States and other countries.

Evolution is a trademark of Novell, Inc.

SUSE is a registered trademark of SUSE AG, a Novell company.

All third-party trademarks are the property of their respective owners.