Version 11.2.27 (2014-01-09)
Abstract
These release notes are generic for all SUSE Linux Enterprise Desktop 11 based products. Some parts may not apply to particular architectures or products. Where this is not obvious, the respective architectures are listed explicitly.
An Installation Quick Start can be found in the
docu directory on the media. Any documentation
(if installed) can be found below
/usr/share/doc/ in the installed system.
This SUSE product includes materials licensed to SUSE under the GNU General Public License (GPL). The GPL requires SUSE to provide the source code that corresponds to the GPL-licensed material. The source code is available for download at http://www.suse.com/download-linux/source-code.html. Also, for up to three years after distribution of the SUSE product, upon request, Novell will mail a copy of the source code. Requests should be sent by e-mail to mailto:sle_source_request@novell.com or as otherwise instructed at http://www.suse.com/download-linux/source-code.html. Novell may charge a reasonable fee to recover distribution costs.
SUSE Linux Enterprise Desktop is the market's only enterprise-quality Linux desktop ready for routine business use. Developed and backed by SUSE, SUSE Linux Enterprise Desktop provides market-leading usability, seamless interoperability with existing IT systems, and dozens of essential applications—all at a fraction of the price of proprietary operating systems. It comes bundled with the latest versions of leading applications such as LibreOffice office productivity suite, Mozilla Firefox web browser, and Evolution email and calendar suite. In addition, it integrates with Microsoft SharePoint and Novell Teaming for group collaboration and supports a wide range of multimedia file formats, wireless and networking standards, and plug-and-play devices.
Through the latest enhancements in power management and security, SUSE Linux Enterprise Desktop also provides an environmentally friendly IT experience (Green IT) and an error-proof desktop. Finally, SUSE Linux Enterprise Desktop unparalleled flexibility. You can deploy it on a wide range of thick client devices (including desktops, notebooks, netbooks, and workstations), on thin client devices, or as a virtual desktop. By leveraging the power of SUSE Linux Enterprise Desktop, your business can dramatically reduce costs, improve end-user security and increase workforce productivity.
For users upgrading from a previous SUSE Linux Enterprise Desktop release it is recommended to review:
These Release Notes are identical across all architectures, and the most recent version is always available online at http://www.suse.com/releasenotes/.
Btrfs is a copy-on-write (CoW) general purpose file system. Based on the CoW functionality, btrfs provides snapshoting. Beyond that data and metadata checksums improve the reliability of the file system. btrfs is highly scalable, but also supports online shrinking to adopt to real-life environments. On appropriate storage devices btrfs also supports the TRIM command.
Support
With SUSE Linux Enterprise 11 SP2, the btrfs file system joins ext3, reiserfs, xfs and ocfs2 as commercially supported file systems. Each file system offers disctinct advantages. While the installation default is ext3, we recommend xfs when maximizing data performance is desired, and btrfs as a root file system when snapshotting and rollback capabilities are required. Btrfs is supported as a root file system (i.e. the file system for the operating system) across all architectures of SUSE Linux Enterprise 11 SP2. Customers are advised to use the YaST partitioner (or AutoYaST) to build their systems: YaST will prepare the btrfs file system for use with subvolumes and snapshots. Snapshots will be automatically enabled for the root file system using SUSE's snapper infrastructure. For more information about snapper, its integration into ZYpp and YaST, and the YaST snapper module, see the SUSE Linux Enterprise documentation.
Migration from "ext" File Systems to btrfs
Migration from existing "ext" file systems (ext2, ext3, ext4) is supported "offline" and "in place". Calling "btrfs-convert [device]" will convert the file system. This is an offline process, which needs at least 15% free space on the device, but is applied in place. Roll back: calling "btrfs-convert -r [device]" will roll back. Caveat: when rolling back, all data will be lost that has been added after the conversion into btrfs; in other words: the roll back is complete, not partial.
RAID
Btrfs is supported on top of MD (multiple devices) and DM (device mapper) configurations. Please use the YaST partitioner to achieve a proper setup. Multivolume/RAID with btrfs is not supported yet and will be enabled with a future maintenance update.
Future Plans
We are planning to announce support for btrfs' built-in multi volume handling and RAID in a later version of SUSE Linux Enterprise.
Starting with SUSE Linux Enterprise 12, we are planning to implement bootloader support for /boot on btrfs.
Transparent compression is implemented and mature. We are planning to support this functionality in the YaST partitioner in a future release.
We are commited to actively work on the btrfs file system with the community, and we keep customers and partners informed about progress and experience in terms of scalability and performance. This may also apply to cloud and cloud storage infrastructures.
Online Check and Repair Functionality
Check and repair functionality ("scrub") is available as part of the btrfs command line tools. "Scrub" is aimed to verify data and metadata assuming the tree structures are fine. "Scrub" can (and should) be run periodically on a mounted file system: it runs as a background process during normal operation.
The tool "fsck.btrfs" tool will soon be available in the SUSE Linux Enterprise update repositories.
Capacity Planning
If you are planning to use btrfs with its snapshot capability, it is advisable to reserve twice as much disk space than the standard storage proposal. This is automatically done by the YaST2 partitioner for the root file system.
Hard Link Limitation
In order to provide a more robust file system, btrfs incorporates back references for all file names, eliminating the classic "lost+found" directory added during recovery. A temporary limitation of this approach affects the number of hard links in a single directory that link to the same file. The limitation is dynamic based on the length of the file names used. A realistic average is approximately 150 hard links. When using 255 character file names, the limit is 14 links. We intend to raise the limitation to a more usable limit of 65535 links in a future maintenance update.
Other Limitations
At the moment, btrfs is not supported as a seed device.
For More Information
For more information about btrfs, see the SUSE Linux Enterprise 11 documentation.
This section includes installation related information for this release.
With SUSE Linux Enterprise 11 SP2 we introduce Linux Kernel 3.0. This kernel is a direct successor of the Linux kernel 2.6 series, thus all applications run without change. However, some applications or installation programs are broken and may check for version "2.6" literally, thus failing to accept the compatibility of our kernel.
We provide two mechanisms to encourage applications to recognize the kernel 3.0 in SUSE Linux Enterprise 11 SP2 as a Linux kernel 2.6 compatible system:
Use the uname26 command line tool, to start a single application in a 2.6 context. Usage is as easy as typing uname26 [PROGRAM] . More information can be found in the manpage of "setarch".
Some database systems and enterprise business applications expect processes and tasks run under a specific user name (not root). The Pluggable Authentication Modules (PAM) stack in SUSE Linux Enterprise allows to put a user into a 2.6 context. To achieve this, please add the username to the file /etc/security/uname26.conf . For more information, see the manpage for "pam_unix2". Caveat: We do not support the "root" user to run in a 2.6 context.
If you are running SAP applications, have a look at SAP Note #1310037 for more information on running SAP applications within a Kernel 2.6 compatibility environment.
Known Issues
The current version of the LSI MegaCLI utility needs to be run with the uname26 personality using the "uname26" tool.
The current version of the IBM Online SAS/SATA Hard Disk Drive Update Program needs to be run with a uname26 personality.
This feature addresses the issue that eth0 does not map to em1 (as labeled on server chassis), when a server has multiple network adapters.
This issue is solved for Dell hardware, which has the corresponding BIOS support, by renaming onboard network interfaces to em[1234], which maps to Embedded NIC[1234] as labeled on server chassis. (em stands for ethernet-on-motherboard.)
The renaming will be done by using the biosdevname utility.
biosdevname is automatically installed and used if YaST2 detects hardware suitable to be used with biosdevname. biosdevname can be disabled during installation by using "biosdevname=0" on the kernel commandline. The usage of biosdevname can be enforced on every hardware with "biosdevname=1". If the BIOS has no support, no network interface names are renamed.
CJK (Chinese, Japanese, and Korean) languages do not work properly during text-mode installation if the framebuffer is not used (Text Mode selected in boot loader).
There are three alternatives to resolve this issue:
Use English or some other non-CJK language for installation then switch to the CJK language later on a running system using >>.
Use your CJK language during installation, but do not choose in the boot loader using . Select one of the other VGA modes instead. Select the CJK language of your choice using , add textmode=1 to the boot loader command-line and start the installation.
Use graphical installation (or install remotely via SSH or VNC).
During the installation YaST resp. SaX2 tries to detect displays and determine the display size and resolution. If you are installing on a notebook with a closed lid it is not be possible to detect the display. To avoid this problem you must keep the lid open during installation.
If the detection fails, start YaST and click >. Then configure the display manually.
As many development packages and sub-packages as possible have been moved to the SDK.
The installer uses persistent device names by default. If you plan to add storage devices to your system after the installation, we strongly recommend you use persistent device names for all storage devices.
To switch to persistent device names on a system that has already been installed, start the YaST2 partitioner. For each partition, select and go to the dialog. Any mount option except Device name provides you persistent device names. In addition, rerun the boot loader module in YaST to switch the bootloader to using the persistent device name. Start the module and select Finish to write the new proposed configuration to disk. This needs to be done before adding new storage devices.
For further information, visit http://en.opensuse.org/Persistant_Storage_Device_Names.
iSCSI devices cannot be used for Linux Software RAID. Using MD devices on top of iSCSI triggers a cyclic dependency that leads to a system crash.
To make NetworkManager send the hostname to the DHCP server, create a
new network profile (see the Administration Guide for more information). Modify
this profile with GNOME Configuration Editor (gconf-editor)
and add the key
/system/networking/connections/$number/ipv4/dhcp-hostname
(replace "$number" with the actual number) with a string value. NetworkManager
will send this value to the DHCP server. A special value
system-hostname can be used to send the current
hostname.
GNOME 2.28
GNOME was updated to version 2.28 with SP1, only selected packages got an update for SP2.
KDE 4.3
SUSE introduced KDE 4 with SUSE Linux Enterprise Desktop 11 as an innovative free software desktop and applications such as the Konqueror web browser, the Dolphin file manager, the Okular document reader, the System Settings control center and more.
KDE was updated to 4.3.4 version with SP1.
This new version of KDE is built on KDE Libraries which provide easy access to resources on the network by means of KIO and advanced visual capabilities through Qt4. Phonon and Solid. Customers migrating from SUSE Linux Enterprise Desktop 10 using KDE are getting a new user experience in version 11 Service Pack 1 and later. We recommend backing up your user home directory when upgrading from SUSE Linux Enterprise Desktop 10. (Partly based on http://www.kde.org/announcements/4.0/.)
X.org 7.4
The X server libraries were updated to version 1.6.5. The client libraries were kept the same, except for libgl.
In some scenarios, FreeRDP performs better than the rdesktop client, which is currently available as the Linux RDP client. Thus we added support for FreeRDP in SUSE Linux Enteprise Desktop 11 SP2.
To avoid the breakage of existing scenarios we will not uninstall rdesktop with the SP3 upgrade.
Banshee can now be synchronized with iPhone and iPod.
OpenOffice.org has been replaced with LibreOffice. If you perform an upgrade, manual interaction is needed, otherwise you will stay with the old OpenOffice.org packages. Future updates will only be prepared and published for LibreOffice. Some parts of the documentation packages still mention 'OpenOffice.org'.
The System Security Services Daemon (sssd) was added to SLE 11 SP2 to provide an alternative method to retrieve user and group information from LDAP directories and to perform authentication through LDAP or Kerberos. It is provided as an alternative to the nss_ldap and pam_ldap (or pam_krb5) Modules. Compared to those modules sssd offers some advantages:
due to it's daemon based architecture possible symbol conflicts between different implementations of LDAP client libraries can be avoided
offline authentication is supported (disabled by default)
builtin support for Kerberos Authentication (no separate PAM module needed)
With SLE 11 SP2 the YaST2 ldap-client module can be used to setup sssd for LDAP (and/or Kerberos) Authentication. The YaST to ldap-client module can also be used to switch from a nss_ldap/pam_ldap based setup to sssd and back.
Some additional notes:
sssd requires a Transport Layer Encryption to be in place when using LDAP based authentication (e.g., LDAPS or StartTLS),
sssd does currently only support the passwd, shadow and group NSS databases
openSSH now makes use of cryptographic hardware acceleration. As a result, the transfer of large quantities of data through a ssh connection is considerably faster. As an additional benefit, the CPU of the system with cryptographic hardware will see a significant reduction in load.
This feature addresses the issue that eth0 does not map to em1 (as labeled on server chassis), when a server has multiple network adapters.
This issue is solved for Dell hardware, which has the corresponding BIOS support, by renaming onboard network interfaces to em[1234], which maps to Embedded NIC[1234] as labeled on server chassis. (em stands for ethernet-on-motherboard.)
The renaming will be done by using the biosdevname utility.
biosdevname is automatically installed and used if YaST2 detects hardware suitable to be used with biosdevname. biosdevname can be disabled during installation by using "biosdevname=0" on the kernel commandline. The usage of biosdevname can be enforced on every hardware with "biosdevname=1". If the BIOS has no support, no network interface names are renamed.
With the changes in the printer market that have happened since SUSE Linux Enterprise 11 SP1 was released, it is highly probable that parts of HPLIP are outdated.
The version upgrade to HPLIP version 3.11.5 keeps SUSE Linux Enterprise 11 SP2 up-to-date regarding to HP printer and all-in-one devices.
Improved Update Stack
SUSE Linux Enterprise Desktop 11 comes with an improved update stack and the command line tool zypper to manage the install/update packages and repositories.
Enhanced YaST Partitioner
Extended Built-in Management Infrastructure
CIM enablement with SFCB CIMON.
EVMS2 Replaced with LVM2
Default Filesystem
The default file system in new installations was changed from ReiserFS to ext3 with SUSE Linux Enterprise Desktop 11. A public statement can be found at http://www.suse.com/products/server/technical-information/#FileSystem.
Samba 3.4.3
UEFI Enablement on AMD64
SWAP over NFS
Python 2.6.0
Perl 5.10
Ruby 1.87
This section includes update-related information for this release.
Oracle and IBM announced in October 2010 that they will collaborate in the OpenJDK Community to develop the leading open source Java SE implementation, and make the OpenJDK community the primary location for open source Java SE development. SUSE supports these efforts and includes openJDK with this and future releases.
Note 1: The java-1_6_0-sun package will be replaced by java-1_6_0-openjdk.
Note 2: Under certain conditions, when upgrading from SLED 11 SP1 to SP2, icedteaweb-plugin is not automatically installed.
With SUSE Linux Enterprise 11 SP2 we introduce Linux Kernel 3.0. This kernel is a direct successor of the Linux kernel 2.6 series, thus all applications run without change. However, some applications or installation programs are broken and may check for version "2.6" literally, thus failing to accept the compatibility of our kernel.
We provide two mechanisms to encourage applications to recognize the kernel 3.0 in SUSE Linux Enterprise 11 SP2 as a Linux kernel 2.6 compatible system:
Use the uname26 command line tool, to start a single application in a 2.6 context. Usage is as easy as typing uname26 [PROGRAM] . More information can be found in the manpage of "setarch".
Some database systems and enterprise business applications expect processes and tasks run under a specific user name (not root). The Pluggable Authentication Modules (PAM) stack in SUSE Linux Enterprise allows to put a user into a 2.6 context. To achieve this, please add the username to the file /etc/security/uname26.conf . For more information, see the manpage for "pam_unix2". Caveat: We do not support the "root" user to run in a 2.6 context.
If you are running SAP applications, have a look at SAP Note #1310037 for more information on running SAP applications within a Kernel 2.6 compatibility environment.
Known Issues
The current version of the LSI MegaCLI utility needs to be run with the uname26 personality using the "uname26" tool.
The current version of the IBM Online SAS/SATA Hard Disk Drive Update Program needs to be run with a uname26 personality.
To upgrade a PostgreSQL server installation from version 8.3 to 9.1, the database files need to be converted to the new version.
Newer versions of PostgreSQL come with the pg_upgrade tool that simplifies and speeds up the migration of a PostgreSQL installation to a new version. Formerly dump and restore was needed that was much slower.
pg_upgrade needs to have the server binaries of both versions available. To allow this, we had to change the way PostgreSQL is packaged as well as the naming of the packages, so that two or more versions of PostgreSQL can be installed in parallel.
Starting with version 9.1, PostgreSQL package names contain numbers indicating the major version. In PostgreSQL terms the major version consists of the first two components of the version number, i.e. 8.3, 8.4, 9.0, or 9.1. So, the packages for Postgresql 9.1 are named postgresql91, postgresql91-server, etc. Inside the packages the files were moved from their standard locations to a versioned location such as /usr/lib/postgresql83/bin or /usr/lib/postgresql91/bin to avoid file conflicts if packages are installed in parallel. The update-alternatives mechanism creates and maintains symbolic links that cause one version (by default the highest installed version) to re-appear in the standard locations. By default, database data are stored under /var/lib/pgsql/data on SUSE Linux.
The following preconditions have to be fulfilled before data migration can be started:
If not already done, the packages of the old PostgreSQL version must be upgraded to the new packaging scheme through a maintenance update. For SLE 11 this means to install the patch that upgrades PostgreSQL from version 8.3.14 to 8.3.19 or higher.
The packages of the new PostgreSQL major version need to be installed. For SLE11 this means to install postgresql91-server and all the packages it depends on. As pg_upgrade is contained in postgresql91-contrib, that one has to be installed as well, at least until the migration is done.
Unless pg_upgrade is used in link mode, the server must have enough free disk space to temporarily hold a copy of the database files. If the database instance was installed in the default location, the needed space in megabytes can be determined by running the follwing command as root: "du -hs /var/lib/pgsql/data". If space is tight, it might help to run the "VACUUM FULL" SQL command on each database in the instance to be migrated, but be aware that it might take very long.
Upstream documentation about pg_upgrade including step by step instructions for performing a database migration can be found under file:///usr/share/doc/packages/postgresql91/html/pgupgrade.html (if the postgresql91-docs package is installed), or online under http://www.postgresql.org/docs/9.1/static/pgupgrade.html . NOTE: The online documentation starts with explaining how you can install PostgreSQL from the upstream sources (which is not necessary on SLE) and also uses other directory names ( /usr/local instead of the update-alternatives based path as described above).
For background information about the inner workings of pg_admin and a performance comparison with the old dump and restore method, see http://momjian.us/main/writings/pgsql/pg_upgrade.pdf .
For an automated upgrade from SLES 10 SP4 or SLES 11 SP1 using AutoYaST see the Deployment Guide, Part "Automated Installations". The Deployment Guide is part of the system documentation that comes with the product.
To migrate the system to the Service Pack 2 level with zypper, proceed as follows:
Open a root shell.
Run zypper ref -s to refresh all services and repositories.
Run zypper up -t patch to install package management updates.
Now it is possible to install all available updates for SLES/SLED 11 SP1; run zypper up -t patch again.
Now the installed products contain information about distribution
upgrades and which migration products should be installed to perform
the migration. Read the migration product information from
/etc/products.d/*.prod and install them.
Enter the following command:
grep '<product' /etc/products.d/*.prod
A sample output could be as follows:
<product>sle-sdk-SP2-migration</product> <product>SUSE_SLED-SP2-migration</product>
Install these migration products (example):
zypper in -t product sle-sdk-SP2-migration SUSE_SLED-SP2-migration
Run suse_register -d 2 -L /root/.suse_register.log to register the products in order to get the corresponding SP2 Update repositories.
Run zypper ref -s to refresh services and repositores.
Check the repositories using zypper lr. Only if needed, disable repositories manually (note that the SP1-Pool and SP1-Updates repos need to stay enabled!) and enable the new SP2 (SP2-Core, SP2-Updates) repositories:
zypper mr --disable <repo-alias> zypper mr --enable <repo-alias>
Then perform a distribution upgrade by entering the following command:
zypper dup --from SLED11-SP2-Core --from SLED11-SP2-Updates \ --from SLE11-WebYaST-SP2-Pool --from SLE11-WebYaST-SP2-Updates
Add more SP2 catalogs here if needed, e.g. in case addon products are installed.
zypper will report that it will delete the migration product and update the main products. Confirm the message to continue updating the RPM packages.
To do a full update, run zypper patch.
After the upgrade is finished, register the new products again:
suse_register -d 2 -L /root/.suse_register.log
Reboot the system
Online migration from SP1 to SP2 is not supported, if debuginfo packages are installed.
Beginning with SLE11-SP1, we switched to use KMS (Kernel Mode Setting) for Intel graphics support. This means that mode setting is now done in kernel space instead of user space (X driver).
If—in rare cases—the new driver concept does not work for you, create an X.Org configuration manually:
Boot into failsafe mode without X (add
"3" to the failsafe mode options) and run
'sax2 -r -m 0=fbdev' to create an fbdev based
xorg.conf.
Then disable KMS permanently by setting the
NO_KMS_IN_INITRD sysconfig variable to
"yes" and run
mkinitrd.
Finally, reboot again (normal mode) to activate this new X.Org configuration.
You can update your previous KDE installation (SUSE Linux Enterprise Desktop 11 or earlier) during system upgrade as described in the manual or as a package update using YaST or zypper. Because of a huge amount of package renaming, it is not possible to update your previous KDE installation using plain rpm commands.
For more information about KDE 4.3, see Section 5.1, “Desktop”.
We ship the GroupWise 8 client with this release. If you want to keep the GroupWise 7 client, enter Software Manager and disable the GroupWise update.
The Groupwise 7 client is available in the
extras-repository which can be enabled
after registration.
With SUSE Linux Enterprise Desktop11 the kernel RPMs are split into different parts:
kernel-flavor-base
Very reduced hardware support, intended to be used in virtual machine images.
kernel-flavor
Extends the base package; contains all supported kernel modules.
kernel-flavor-extra
All other kernel modules which may be useful but are not supported. This package will not be installed by default.
The man command now asks which manual page the user wants to see if manual pages with the same name exist in different sections. The user is expected to type the section number to make this manual page visible.
If you want to get back the previous behavior, set
MAN_POSIXLY_CORRECT=1 in a shell initialization file
such as ~/.bashrc.
This release of SUSE Linux Enterprise Desktop ships with AppArmor. The AppArmor intrusion
prevention framework builds a firewall around your applications by
limiting the access to files, directories, and POSIX capabilities
to the minimum required for normal operation. AppArmor protection
can be enabled via the AppArmor control panel, located in YaST
under Security and Users. For detailed information about using
AppArmor, see the documentation in
/usr/share/doc/packages/apparmor-docs.
The AppArmor profiles included with SUSE Linux have been developed with our best efforts to reproduce how most users use their software. The profiles provided work unmodified for many users, but some users find our profiles too restrictive for their environments.
If you discover that some of your applications do not function as you expected, you may need to use the AppArmor Update Profile Wizard in YaST (or use the aa-logprof(8) command line utility) to update your AppArmor profiles. Place all your profiles into learning mode with the following: aa-complain /etc/apparmor.d/*
When a program generates a high number of complaints, the system's performance is degraded. To mitigate this, we recommend periodically running the Update Profile Wizard (or aa-logprof(8)) to update your profiles, even if you choose to leave them in learning mode. This reduces the number of learning events logged to disk, which improves the performance of the system.
SuSEfirewall2 is enabled by default. That means that by default you cannot log in from remote systems. It also interferes with network browsing and multicast applications, such as SLP and Samba ("Network Neighborhood"). You can fine-tune the firewall settings using YaST.
This new version of the e1000e driver adds support for the following devices: 82567LM Gigabit Network Connection 82574L Gigabit Network Connection 82567V-3 Gigabit Network Connection 82579LM Gigabit Network Connection 82579V Gigabit Network Connection 82583V Gigabit Network Connection 82567V-4 Gigabit Network Connection 82566DC-2 Gigabit Network Connection
This Service Pack adds support for the following Intel(R) Centrino(R) Wireless Adapters: - Intel(R) Centrino(R) Wireless-N 100 and Intel(R) Centrino(R) Wireless-N 130 (also referred to as Crane Peak WiFi and Crane Peak WiFi+BT, respectively). - Intel(R) Centrino(R) Wireless-N 6150, codename Kelsey Peak. - Intel(R) Centrino(R) Wireless-N 1030 and Intel(R) Centrino(R) Advanced-N 6230 (also referred to as Rainbow Peak 1 and 2, respectively). - Intel(R) Centrino(R) Advanced-N 6205, codename Taylor Peak
The Chelsio T4 adapter with the cxgb4, cxgb4i, and iw_cxgb4 drivers support 10Ge NIC, iSCSI, and iWARP functions respectively. IBM Power systems support Enhanced Error Handling (EEH) and Hotplug removal. When hotplug operations are performed on a running adapter, a crash, hang or failure to remove the adapter may occur.
A permanent solution in the device drivers is being investigated but may not be ready in time for GM. Until the maintenance driver is released, it is necessary to unload all of the cxgb4, cxgb4i, and iw_cxgb4 drivers prior to running any of the hotplug commands such as 'drmgr -r'.
Once the drivers are unloaded, the adapter can be hotplug moved to another partition or removed from the system as necessary.
The bna 3.0.2.2 driver supports all Brocade FC/FCOE adapters. Below is a list of adapter models with corresponding PCIIDs:
PCIID Model 1657:0014:1657:0014 1010 10Gbps single port CNA - LL 1657:0014:1657:0014 1020 10Gbps dual port CNA - LL 1657:0014:1657:0014 1007 10Gbps dual port CNA - LL 1657:0014:1657:0014 1741 10Gbps dual port CNA - LL 1657:0022:1657:0023 1860 10Gbps CNA - LL 1657:0022:1657:0023 1860 10Gbps NIC - LL
Firmware Download: The latest Firmware package for 3.0.2.2 bna driver can be found at: http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page and then click following respective util package link: Version Link v3.0.2.0 Linux Adapter Firmware package for RHEL 6.2, SLES 11SP2
Configuration and Management utility download: The latest driver configuration & management utility for 3.0.2.2 bna driver can be found at http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page and then click version v3.0.2.0, "Linux Adapter Util package for RHEL 6.2, SLES 11SP2".
Documentation: The latest Administration's Guide, Installation and Reference Manual, Troubleshooting Guide, and Release Notes for the corresponding out-of-box driver can be found at http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page and use the following inbox and out-of-box driver version mapping to find the corresponding documentation:
Inbox Version Out-of-box Version v3.0.2.2 v3.0.0.0
Support: For general product and support info, go to the Brocade website at http://www.brocade.com/services-support/index.page .
Open-iSCSI support is added to the QLogic iSCSI qla4xxx driver in SUSE Linux Enterprise Server 11 Service Pack 2. Using iscsiadm the features supported for qla4xxx are:
Network configuration
iSCSI Target management enabling Discovery, Login/Logout of iSCSI targets
For more details, see Open-iSCSI README at http://www.open-iscsi.org/docs/README .
Note: The IOCTL support in qla4xxx is dropped and hence QLogic Applications are not supported with this Inbox driver. This is being targeted for a future release. The qla4xxx driver compatible with QLogic Applications can also be obtained from the QLogic Web site.
Using bnx2fc driver for installation:
Broadcom's NetXtreme II 57712 device provides networking as well as storage functionality. Boot from SAN on this device is supported over FCoE network using bnx2fc driver. Add "withfcoe=1" to the boot option line. Since the DCBX protocol is offloaded and performed by the device firmware, 'dcb' feature should be turned off during installation when prompted.
Note that FCoE boot from SAN on Broadcom 10G devices is only supported using the bnx2fc driver. Boot from SAN using the software fcoe driver is not supported.
For detailed information, refer to "Broadcom NetXtreme II(tm) Network Adapter User Guide".
Using iSCSI Disks When Installing:
Note: The installer for SLES 11 SP2 now supports iscsi install using software iscsi method and native Broadcom offload method on Broadcom NetXtreme II devices.
To use Broadcom offload iSCSI during install, the iSCSI option ROM on the Broadcom device must be set to HBA mode. Refer to "iSCSI Boot Broadcom NetXtreme II(tm) Network Adapter User Guide" for detailed information on iSCSI install/boot for Broadcom devices.
To use software iSCSI install, disable HBA mode in the Broadcom iSCSI option ROM.
Storage Drivers:
Added bnx2i driver for Broadcom NetXtreme II in version 2.7.0.3
Added new bnx2fc driver for Broadcom NetXtreme II 57712
Bnx2fc is a FCoE offload driver, that uses open-fcoe's stack and fcoeutils. Note that SLES 11 SP2 only supports offload FCoE on NetXtreme II 57712. Refer to Documentation/scsi/bnx2fc.txt in linux kernel source for the driver usage information.
The bfa 3.0.2.2 driver supports all Brocade FC/FCOE adapters. Below is a list of adapter models with corresponding PCIIDs:
PCIID Model 1657:0013:1657:0014 425 4Gbps dual port FC HBA 1657:0013:1657:0014 825 8Gbps PCIe dual port FC HBA 1657:0013:103c:1742 HP 82B 8Gbps PCIedual port FC HBA 1657:0013:103c:1744 HP 42B 4Gbps dual port FC HBA 1657:0017:1657:0014 415 4Gbps single port FC HBA 1657:0017:1657:0014 815 8Gbps single port FC HBA 1657:0017:103c:1741 HP 41B 4Gbps single port FC HBA 1657:0017:103c 1743 HP 81B 8Gbps single port FC HBA 1657:0021:103c:1779 804 8Gbps FC HBA for HP Bladesystem c-class 1657:0014:1657:0014 1010 10Gbps single port CNA - FCOE 1657:0014:1657:0014 1020 10Gbps dual port CNA - FCOE 1657:0014:1657:0014 1007 10Gbps dual port CNA - FCOE 1657:0014:1657:0014 1741 10Gbps dual port CNA - FCOE 1657:0022:1657:0024 1860 16Gbps FC HBA 1657:0022:1657:0022 1860 10Gbps CNA - FCOE
Firmware Download: The latest Firmware package for the 3.0.2.2 bfa driver can be found at http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page , then click version v3.0.2.0, "Linux Adapter Firmware package for RHEL 6.2, SLES 11SP2".
Configuration and Management Utility Download: The latest driver configuration and management utility for 3.0.2.2 bfa driver can be found at http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page , then click version v3.0.2.0 "Linux Adapter Firmware package for RHEL 6.2, SLES 11SP2".
Documentation: The latest Administration's Guide, Installation and Reference Manual, Troubleshooting Guide, and Release Notes for the corresponding out-of-box driver can be found at http://www.brocade.com/services-support/drivers-downloads/adapters/Linux.page and use the following inbox and out-of-box driver version mapping to find the corresponding documentation:
Inbox Version Out-of-box Version v3.0.2.2 v3.0.0.0
Support: For general product and support info, go to the Brocade website at http://www.brocade.com/services-support/index.page .
USB 3.0 is the third major revision of the USB standard, which brings faster data transfer and increases power savings. More and more USB 3.0 consumer products are launched in market. Intel starts to support USB 3.0 in the Intel(R) 7 Series/C216 Chipset Family.
This SP introduces support for USB 3.0 by adding patches for xHCI (eXtensible Host Controller Interface), USB 3.0 hub support and USB 3.0 support for Intel(R) 7 Series/C216 Chipset Family.
The processor graphics is provided in the 2nd Generation Intel(R) Core™ i7/i5/i3 processor family.
This service pack adds support for the processor graphics in the 2nd Generation Intel(R) Core™ i7/i5/i3 processor family by updating the required kernel module, xserver, xf86-video-intel driver, Mesa and dri driver.
gawk as delivered in SUSE Linux Enterprise 11 SP1, has a low performance with respect to multibyte string operations.
Carefully considering the changes from 3.1.6 to 3.1.8 we decided that a version upgrade will significantly help in other areas as well. Find below the list of important changes:
The zero flag no longer applies to %c and %s.
Failure to open a socket is no longer a fatal error.
The ' flag (%'d) is now just ignored on systems that cannot support it.
Gawk now handles multibyte strings better in [s]printf with field widths and such.
A getline from a directory is no longer fatal; instead it returns -1.
Technology Preview features are either not supported or supported in a limited fashion. These features are mainly included for customer convenience and be functionally incomplete, unstable or in other ways not suitable for production use.
The eCryptfs kernel modules and the ecryptfs-utils package shipped with SUSE Linux Enterprise Desktop 11 are a preview of a stacked cryptographic filesystem for Linux.
SUSE Linux Enterprise Desktop 11 contains KVM as an additional virtualization solution. It is not supported by SUSE, but is an area of interest for future development and deliveries.
It is possible to run SUSE Linux Enterprise Desktop 11 on a read-only root filesystem. Due to the huge number of possible configurations, this is currently not a supported scenario.
The /tmp and /var
directories need to be on a separate partition and cannot be
mounted read-only.
After the installation has finished and all services are configured, login as root and do the following modifications:
Modify /etc/fstab and add "ro" to the mount
options of the root filesystem entry.
rm /etc/mtab ln -s /proc/mounts /etc/mtab mkdir /var/lib/hwclock mv /etc/adjtime /var/lib/hwclock ln -s /var/lib/hwclock/adjtime /etc/adjtime # the following two steps are only necessary if you use dhcp: mv /etc/resolv.conf /var/lib/misc/ ln -s /var/lib/misc/resolv.conf /etc/resolv.conf # Now mount root filesystem read-only and reboot mount -o remount,ro / reboot
Adobe has discontinued support for Adobe Reader 9 on Linux (http://www.adobe.com/support/products/enterprise/eol/eol_matrix.html#863), and thus no longer provides security updates.
In order not to lose functionality, Adobe Acrobat Reader will be kept on released products. But to avoid security issues with accessing PDFs online, the PDF viewer browser plugin will however be removed. In order to maintain functionality the latest Firefox ESR releases include a feature to display PDF documents, which receives maintenance and security updates via Firefox updates.
The acroread_ja package, a version of Acrobat Reader with Japanese localisation, has not been seeing any upstream security updates for a while and hence lacks a large and ever increasing number of critical security fixes.
To avoid exposing users to severe security risks, we are removing this package in favor of the general version of Acrobat Reader.
In SUSE Linux Enterprise (up version 11 SP2) we provided "rpcbind", which is compatible with portmap. "rpcbind" now provides full IPv6 support. Thus support for portmap ended with the release of SLE 11 SP3.
With SP2 we are switching from xpdf-tools to poppler-tools for PDF rendering. This is based on xpdf-tools, but more stable and better maintained and it is a seamless replacement.
L3 support for Openswan is scheduled to expire. This decision is driven by the fact that Openswan development stalled substantially and there are no tangible signs that this will change in the future.
In contrast to this the strongSwan project is vivid and able to deliver a complete implementation of current standards. Compared to Openswan all relevant features are available by the package strongSwan plus strongSwan is the only complete Open Source implementation of the RFC 5996 IKEv2 standard whereas Openswan only implements a small mandatory subset. For now and the expected future only strongSwan qualifies to be an enterprise-ready solution for encrypted TCP/IP connectivity.
Intel Active Management (IAMT) drivers have been removed from SUSE Linux Enterprise due to incompatibilities and no longer being maintained. Refer to the Intel documentation on how to access newer versions of IAMT drivers for SUSE Linux Enterprise.
In an effort to ensure long term maintainability and given how fast web technology is evolving and that Firefox features the richtest ecosystem (plug-ins, add-ons,...) among all web browers, we are focusing on Firefox as our recommended web browser and are obsoleting the Epiphany browser in favor it.
In some scenarios, FreeRDP performs better than the rdesktop client, which is currently available as the Linux RDP client. Thus we added support for FreeRDP in SUSE Linux Enteprise Desktop 11 SP2.
To avoid the breakage of existing scenarios we will not uninstall rdesktop with the SP3 upgrade.
To facilitate the migration of an ext4 file system to another, supported file system, the SLE 11 SP2 kernel now contains a fully supported ext4 file system module, which provides solely read-only access to the file system.
If read-write access to an ext4 file system is still required, you may install the ext4-writeable KMP (kernel module package). This package is available in the online repository "SLES11-Extras" and contains a kernel module that provides read-write access to an ext4 file system. Be aware, that this kernel module is unsupported.
ext4 is not supported for the installation of the SUSE Linux Enterprise operating system files
With SUSE Linux Enterprise 11 SP2 we support offline migration from ext4 to the supported btrfs filesystem.
The following list of current functionalities has been removed with this SUSE Linux Enterprise Desktop release.
amor
dante
powertweak
zmd
The following packages are deprecated and will be removed with SUSE Linux Enterprise Desktop 12:
lprng
sendmail
qt3
New Packages (compared with SLED11 SP1 GA):
banshee-1-backend-io-gio
banshee-1-client-classic
banshee-1-client-muinshee
banshee-1-core
banshee-1-dmp
banshee-1-dmp-apple-devices
banshee-1-dmp-mtp
biosdevname
celt
cft
cifs-utils
cpupower
crda
dirac
efibootmgr
enca
evolution-ews
evolution-ews-lang
ffado
ffado-mixer
flickrnet
freerdp
freerdp-plugins
gdata-sharp
gio-sharp
gkeyfile-sharp
glibmm2-32bit
gstreamer-0_10-fluendo-mp3
gstreamer-0_10-plugins-bad
gstreamer-0_10-plugins-bad-lang
gstreamer-0_10-plugins-v4l
gtk-sharp-beans
gudev-sharp
haveged
hp-drive-guard
icedtea-web
iscsitarget-kmp-pae
iscsitarget-kmp-trace
java-1_6_0-openjdk
java-1_6_0-openjdk-demo
java-1_6_0-openjdk-devel
kate-tools
kbluetooth
kernel-firmware
kernel-trace
kernel-trace-base
kernel-trace-devel
kernel-trace-extra
libass4
libblkid1-32bit
libboost_thread1_36_0
libcap-ng0
libcap-ng0-32bit
libcap-ng-utils
libcares2
libcares2-32bit
libcdaudio
libcelt0-2
libcelt0-2-32bit
libcollection2
libdhash1
libdirac_decoder0
libdirac_encoder0
libenca0
libffado2
libffado2-32bit
libfreerdp0
libftgl2
libgme0
libgnomecups-32bit
libgnomeprint-32bit
libgnomeprintui-32bit
libgpod4
libgpod-sharp
libgstbasecamerabinsrc-0_10-0
libgstbasecamerabinsrc-0_10-0-32bit
libgstbasevideo-0_10-0
libgstbasevideo-0_10-0-32bit
libgstphotography-0_10-0
libgstphotography-0_10-0-32bit
libgstsignalprocessor-0_10-0
libgstsignalprocessor-0_10-0-32bit
libgstvdp-0_10-0
libgstvdp-0_10-0-32bit
libgudev-1_0-0
libgudev-1_0-0-32bit
libiec61883
libiec61883-32bit
libimobiledevice2
libimobiledevice-tools
libini_config2
libkate1
libldb1
libldb1-32bit
liblzma5
liblzma5-32bit
libmodplug1
libnetcontrol0
libnetcontrol0-32bit
libnewt0_52
libnl-32bit
libnotify1-32bit
liboggkate1
liborc-0_4-0
liborc-0_4-0-32bit
libpath_utils1
libplist1
libplist++1
libraw1394-11
libraw1394-11-32bit
libref_array1
libreoffice
libreoffice-base
libreoffice-base-drivers-postgresql
libreoffice-base-extensions
libreoffice-branding-SLED
libreoffice-calc
libreoffice-calc-extensions
libreoffice-converter
libreoffice-draw
libreoffice-draw-extensions
libreoffice-filters-optional
libreoffice-gnome
libreoffice-help-cs
libreoffice-help-da
libreoffice-help-de
libreoffice-help-en-GB
libreoffice-help-en-US
libreoffice-help-es
libreoffice-help-fr
libreoffice-help-gu-IN
libreoffice-help-hi-IN
libreoffice-help-hu
libreoffice-help-it
libreoffice-help-ja
libreoffice-help-ko
libreoffice-help-nl
libreoffice-help-pl
libreoffice-help-pt
libreoffice-help-pt-BR
libreoffice-help-ru
libreoffice-help-sv
libreoffice-help-zh-CN
libreoffice-help-zh-TW
libreoffice-hyphen
libreoffice-icon-themes
libreoffice-impress
libreoffice-impress-extensions
libreoffice-kde
libreoffice-kde4
libreoffice-l10n-af
libreoffice-l10n-ar
libreoffice-l10n-ca
libreoffice-l10n-cs
libreoffice-l10n-da
libreoffice-l10n-de
libreoffice-l10n-en-GB
libreoffice-l10n-es
libreoffice-l10n-fi
libreoffice-l10n-fr
libreoffice-l10n-gu-IN
libreoffice-l10n-hi-IN
libreoffice-l10n-hu
libreoffice-l10n-it
libreoffice-l10n-ja
libreoffice-l10n-ko
libreoffice-l10n-nb
libreoffice-l10n-nl
libreoffice-l10n-nn
libreoffice-l10n-pl
libreoffice-l10n-pt
libreoffice-l10n-pt-BR
libreoffice-l10n-ru
libreoffice-l10n-sk
libreoffice-l10n-sv
libreoffice-l10n-xh
libreoffice-l10n-zh-CN
libreoffice-l10n-zh-TW
libreoffice-l10n-zu
libreoffice-languagetool
libreoffice-languagetool-de
libreoffice-languagetool-en
libreoffice-languagetool-es
libreoffice-languagetool-fr
libreoffice-languagetool-it
libreoffice-languagetool-nl
libreoffice-languagetool-pl
libreoffice-languagetool-sv
libreoffice-mailmerge
libreoffice-math
libreoffice-mono
libreoffice-officebean
libreoffice-openclipart
libreoffice-pyuno
libreoffice-templates-de
libreoffice-templates-en
libreoffice-templates-labels-a4
libreoffice-templates-labels-letter
libreoffice-templates-presentation-layouts
libreoffice-thesaurus-cs
libreoffice-thesaurus-de
libreoffice-thesaurus-en
libreoffice-thesaurus-es
libreoffice-thesaurus-fr
libreoffice-thesaurus-hu
libreoffice-thesaurus-nb
libreoffice-thesaurus-pl
libreoffice-thesaurus-pt
libreoffice-thesaurus-ru
libreoffice-thesaurus-sk
libreoffice-thesaurus-sv
libreoffice-writer
libreoffice-writer-extensions
libsnapper1
libSoundTouch0
libSoundTouch0-32bit
libstdc++46-32bit
libstdc++46
libtalloc2
libtalloc2-32bit
libtevent0
libtevent0-32bit
libtimidity-0_1-0
libtimidity-0_1-0-32bit
libudev0
libudev0-32bit
libusb-1_0-0
libusb-1_0-0-32bit
libusbmuxd1
libvdpau1
libvdpau1-32bit
libvirt-client
libvirt-client-32bit
libvpx0
libxml++
libxml++-32bit
libyajl1
libyajl1-32bit
lsscsi
media-player-info
mono-wcf
mozilla-kde4-integration
mozilla-xulrunner192
mozilla-xulrunner192-32bit
mozilla-xulrunner192-gnome
mozilla-xulrunner192-gnome-32bit
mozilla-xulrunner192-translations
mozilla-xulrunner192-translations-32bit
ndiswrapper-kmp-trace-1.57rc1_3.0.13_0.15
netcat-openbsd
NetworkManager-vpnc-kde4-0.9.svn1043876
newt
nfs4-acl-tools
novell-client-doc
novfs-kmp-default-1_3.0.13_0.15
novfs-kmp-pae-1_3.0.13_0.15
novfs-kmp-trace-1_3.0.13_0.15
novfs-kmp-xen-1_3.0.13_0.15
PackageKit-gstreamer-plugin
perl-apparmor-2.5.1.r1445
perl-Convert-BinHex
perl-HTML-TokeParser-Simple
perl-IO-Socket-INET6
perl-NetAddr-IP
perl-Socket6
perl-Sub-Override
perl-Sub-Uplevel
perl-Test-Exception
plutil
poppler-tools
python-argparse
python-curl
python-dmidecode
python-ethtool
python-newt
rhnlib
ruby-ffi
ruby-rb-inotify
ruby-rpm
sled-apps_pt_BR
sled-apps_pt_BR-pdf
sled-libreofficequick_en-pdf
sles-kvm_en-pdf
snapper
snapper-zypp-plugin
soundtouch
spacewalk-check
spacewalk-client-setup
spacewalk-client-tools
spacewalksd
squashfs
sssd
sssd-32bit
sssd-tools
subscription-tools
suseRegisterInfo
timezone-java-2011m
translation-update-ar
translation-update-fr
translation-update-hu
translation-update-it
translation-update-ko
translation-update-nb
translation-update-nl
translation-update-pt
translation-update-ru
translation-update-sv
translation-update-zh_CN
translation-update-zh_TW
usb_modeswitch-data
usbmuxd
vlan
vpx-tools
wireless-regdb
xen-doc-html
xen-doc-pdf
xen-kmp-trace
xen-libs-32bit
xorg-x11-doc
xz
xz-lang
yast2-kdump
yast2-snapper
zypper-log
zypp-plugin-python
zypp-plugin-spacewalk
Removed Packages (all architectures, compared with SLED 11 SP1 GA):
acroread_ja
amor
bluez-gnome
bluez-gnome-lang
btrfs-kmp-default
btrfs-kmp-pae
btrfs-kmp-xen
cifs-mount
digikamimageplugins-superimpose
epiphany
epiphany-branding-SLED
epiphany-extensions
epiphany-extensions-lang
epiphany-lang
gmime
gst-fluendo-mp3
gstreamer-0_10-schroedinger
hyper-v-kmp-default
hyper-v-kmp-pae
intel-iamt
intel-iamt-heci
intel-iamt-heci-kmp-default
intel-iamt-heci-kmp-pae
intel-iamt-heci-kmp-xen
ipod-sharp
iwl1000-ucode
iwl3945-ucode
iwl4965-ucode
iwl5000-ucode
iwl5150-ucode
iwl6000-ucode
java-1_6_0-sun
java-1_6_0-sun-alsa
java-1_6_0-sun-demo
java-1_6_0-sun-jdbc
java-1_6_0-sun-plugin
java-1_6_0-sun-src
kdebluetooth
kdebluetooth-lang
kernel-desktop-devel
kipi-plugins
kipi-plugins-lang
libflashsupport
libflashsupport-32bit
libgpod3
libstdc++43
libstdc++43-32bit
libtalloc1
libtalloc1-32bit
libvolume_id1
mozilla-xulrunner190
mozilla-xulrunner190-32bit
mozilla-xulrunner190-gnomevfs
mozilla-xulrunner190-gnomevfs-32bit
mozilla-xulrunner190-translations
mozilla-xulrunner190-translations-32bit
mozilla-xulrunner191
mozilla-xulrunner191-32bit
mozilla-xulrunner191-gnomevfs
mozilla-xulrunner191-gnomevfs-32bit
mozilla-xulrunner191-translations
mozilla-xulrunner191-translations-32bit
neon
NetworkManager-kde
OpenOffice_org
OpenOffice_org-base
OpenOffice_org-base-drivers-postgresql
OpenOffice_org-base-extensions
OpenOffice_org-branding-SLED
OpenOffice_org-calc
OpenOffice_org-calc-extensions
OpenOffice_org-components
OpenOffice_org-converter
OpenOffice_org-draw
OpenOffice_org-draw-extensions
OpenOffice_org-filters
OpenOffice_org-filters-optional
OpenOffice_org-gnome
OpenOffice_org-help-ar
OpenOffice_org-help-cs
OpenOffice_org-help-da
OpenOffice_org-help-de
OpenOffice_org-help-en-GB
OpenOffice_org-help-en-US
OpenOffice_org-help-es
OpenOffice_org-help-fr
OpenOffice_org-help-gu-IN
OpenOffice_org-help-hi-IN
OpenOffice_org-help-hu
OpenOffice_org-help-it
OpenOffice_org-help-ja
OpenOffice_org-help-ko
OpenOffice_org-help-nl
OpenOffice_org-help-pl
OpenOffice_org-help-pt
OpenOffice_org-help-pt-BR
OpenOffice_org-help-ru
OpenOffice_org-help-sv
OpenOffice_org-help-zh-CN
OpenOffice_org-help-zh-TW
OpenOffice_org-hyphen
OpenOffice_org-icon-themes
OpenOffice_org-impress
OpenOffice_org-impress-extensions
OpenOffice_org-kde
OpenOffice_org-l10n-af
OpenOffice_org-l10n-ar
OpenOffice_org-l10n-ca
OpenOffice_org-l10n-cs
OpenOffice_org-l10n-da
OpenOffice_org-l10n-de
OpenOffice_org-l10n-en-GB
OpenOffice_org-l10n-es
OpenOffice_org-l10n-extras
OpenOffice_org-l10n-fi
OpenOffice_org-l10n-fr
OpenOffice_org-l10n-gu-IN
OpenOffice_org-l10n-hi-IN
OpenOffice_org-l10n-hu
OpenOffice_org-l10n-it
OpenOffice_org-l10n-ja
OpenOffice_org-l10n-ko
OpenOffice_org-l10n-nb
OpenOffice_org-l10n-nl
OpenOffice_org-l10n-nn
OpenOffice_org-l10n-pl
OpenOffice_org-l10n-pt
OpenOffice_org-l10n-pt-BR
OpenOffice_org-l10n-ru
OpenOffice_org-l10n-sk
OpenOffice_org-l10n-sv
OpenOffice_org-l10n-xh
OpenOffice_org-l10n-zh-CN
OpenOffice_org-l10n-zh-TW
OpenOffice_org-l10n-zu
OpenOffice_org-LanguageTool
OpenOffice_org-LanguageTool-de
OpenOffice_org-LanguageTool-en
OpenOffice_org-LanguageTool-es
OpenOffice_org-LanguageTool-fr
OpenOffice_org-LanguageTool-it
OpenOffice_org-LanguageTool-nl
OpenOffice_org-LanguageTool-pl
OpenOffice_org-LanguageTool-sv
OpenOffice_org-libs-core
OpenOffice_org-libs-extern
OpenOffice_org-libs-gui
OpenOffice_org-mailmerge
OpenOffice_org-math
OpenOffice_org-mono
OpenOffice_org-officebean
OpenOffice_org-openclipart
OpenOffice_org-pyuno
OpenOffice_org-Quickstarter
OpenOffice_org-templates-de
OpenOffice_org-templates-en
OpenOffice_org-templates-labels-a4
OpenOffice_org-templates-labels-letter
OpenOffice_org-templates-presentation-layouts
OpenOffice_org-thesaurus-cs
OpenOffice_org-thesaurus-de
OpenOffice_org-thesaurus-en
OpenOffice_org-thesaurus-es
OpenOffice_org-thesaurus-fr
OpenOffice_org-thesaurus-hu
OpenOffice_org-thesaurus-nb
OpenOffice_org-thesaurus-pl
OpenOffice_org-thesaurus-pt
OpenOffice_org-thesaurus-ru
OpenOffice_org-thesaurus-sk
OpenOffice_org-thesaurus-sv
OpenOffice_org-ure
OpenOffice_org-writer
OpenOffice_org-writer-extensions
paman
pavumeter
perl-libapparmor
ralink-firmware
rt3090-config
sblim-testsuite
sled-manuals_en-pdf
sled-oofficequick_en-pdf
wacom-kmp-default
wacom-kmp-pae
xpdf-tools
Removed Packages (i586 architecture, compared with SLED 11 SP1 GA):
xen
xen-tools
The iSCSI being used in SLES 11 SP2 is 2.0.872. After discussion with the open-iscsi maintainer, it was determined that upgrading the SUSE version to 2.0.873, the latest stable version at the time this investigation began, was the best approach.
This also allows us to supported an updated iscsiuio package from Broadcom, which they have requested.
It was felt that this stable version, with SUSE patches added, was safe to use, partly based on the fact that it is present in SLES 11 SP3 already.
Open-iscsi was updated from version 2.0.872 to 2.0.873, which is the latest upstream stable version and fully supports IPv6. It has been successfully tested for IPv6 compliance as well as core functionality, and is backwards compatible with the previous version.
SUSE Linux Enterprise 11 (x86, x86_64 and IA64) is using the Myri10GE driver from mainline Linux kernel. The driver requires a firmware file to be present, which is not being delivered with SUSE Linux Enterprise 11.
Download the required firmware at http://www.myricom.com.
The next generation mainstream client and entry level server has a Platform Controller Hub (PCH) that requires some device ID patches to detect and drive. The enablement includes SATA, HD Audio, TCO Watchdog, etc.
The Intel 6 Series and C200 Series Chipset Platform Controller Hub (PCH) for mainstream clients and entry level servers are now properly detected and supported. The enablement includes SATA, HD Audio, TCO Watchdog, etc.
With SLE 11 SP2, we removed the 32-bit hypervisor as a virtualization host. 32-bit virtual guests are not affected and are fully supported with the provided 64-bit hypervisor.
If you had a boot entry for it when upgrading from SP1, you need to manually remove it.
This section contains a number of technical changes and enhancements for the experienced user.
Due to limitations of the legacy x86 and x86_64 BIOS implementations booting from devices larger than 2 TiB is technically not possible using legacy partition tables (DOS MBR).
With SUSE Linux Enterprise Desktop 11 Service Pack 1 we support installation and boot using uEFI on the x86_64 architecture and certified hardware.
For better sound functionality we strongly recommend that pulseaudio 0.9.14 or higher is installed. This version is available via maintenance channels for SUSE Linux Enterprise systems registered with SUSE.
The modify_resolvconf script is removed in favor of the more
versatile netconfig script. This new script handles specific
network settings from multiple sources more flexibly and transparently.
For more information, see the updated manuals and the
netconfig man-page.
Instead of the madwifi driver the ath5k/ath9k in-kernel replacement is now available. ath5k/ath9k does not support access point mode yet, but normal networks (infrastructure and ad-hoc) are well supported by the new driver.
Lenovo ThinkPad laptops have special code in the MBR (master boot record) because of the "Blue ThinkVantage button" functionality. If proper detection and preparation fails, it might be necessary to restore the boot sector.
If you have a ThinkPad, ensure that the bootloader is not installed into the MBR (verify it in the installation proposal!) and the MBR is not rewritten by generic code (in installation proposel select Bootloader -> Boot Loader Installation -> Boot Loader Options -> Write Generic Boot Code to MBR -- should be unchecked).
If your MBR gets rewritten, the ThinkVantage button will not work
anymore. The back-up of the MBR is stored in
/var/lib/YaST2/backup_boot_sectors/.
To avoid the mail-flood caused by cron status messages, the default
value of SEND_MAIL_ON_NO_ERROR in
/etc/sysconfig/cron is now set to
"no" for new installations. Even with this setting
to "no", cron data output will still be send to the
MAILTO address, as documented in the cron manpage.
In the update case it is recommended to set these values according to your needs.
Btrfs is a copy-on-write (CoW) general purpose file system. Based on the CoW functionality, btrfs provides snapshoting. Beyond that data and metadata checksums improve the reliability of the file system. btrfs is highly scalable, but also supports online shrinking to adopt to real-life environments. On appropriate storage devices btrfs also supports the TRIM command.
Support
With SUSE Linux Enterprise 11 SP2, the btrfs file system joins ext3, reiserfs, xfs and ocfs2 as commercially supported file systems. Each file system offers disctinct advantages. While the installation default is ext3, we recommend xfs when maximizing data performance is desired, and btrfs as a root file system when snapshotting and rollback capabilities are required. Btrfs is supported as a root file system (i.e. the file system for the operating system) across all architectures of SUSE Linux Enterprise 11 SP2. Customers are advised to use the YaST partitioner (or AutoYaST) to build their systems: YaST will prepare the btrfs file system for use with subvolumes and snapshots. Snapshots will be automatically enabled for the root file system using SUSE's snapper infrastructure. For more information about snapper, its integration into ZYpp and YaST, and the YaST snapper module, see the SUSE Linux Enterprise documentation.
Migration from "ext" File Systems to btrfs
Migration from existing "ext" file systems (ext2, ext3, ext4) is supported "offline" and "in place". Calling "btrfs-convert [device]" will convert the file system. This is an offline process, which needs at least 15% free space on the device, but is applied in place. Roll back: calling "btrfs-convert -r [device]" will roll back. Caveat: when rolling back, all data will be lost that has been added after the conversion into btrfs; in other words: the roll back is complete, not partial.
RAID
Btrfs is supported on top of MD (multiple devices) and DM (device mapper) configurations. Please use the YaST partitioner to achieve a proper setup. Multivolume/RAID with btrfs is not supported yet and will be enabled with a future maintenance update.
Future Plans
We are planning to announce support for btrfs' built-in multi volume handling and RAID in a later version of SUSE Linux Enterprise.
Starting with SUSE Linux Enterprise 12, we are planning to implement bootloader support for /boot on btrfs.
Transparent compression is implemented and mature. We are planning to support this functionality in the YaST partitioner in a future release.
We are commited to actively work on the btrfs file system with the community, and we keep customers and partners informed about progress and experience in terms of scalability and performance. This may also apply to cloud and cloud storage infrastructures.
Online Check and Repair Functionality
Check and repair functionality ("scrub") is available as part of the btrfs command line tools. "Scrub" is aimed to verify data and metadata assuming the tree structures are fine. "Scrub" can (and should) be run periodically on a mounted file system: it runs as a background process during normal operation.
The tool "fsck.btrfs" tool will soon be available in the SUSE Linux Enterprise update repositories.
Capacity Planning
If you are planning to use btrfs with its snapshot capability, it is advisable to reserve twice as much disk space than the standard storage proposal. This is automatically done by the YaST2 partitioner for the root file system.
Hard Link Limitation
In order to provide a more robust file system, btrfs incorporates back references for all file names, eliminating the classic "lost+found" directory added during recovery. A temporary limitation of this approach affects the number of hard links in a single directory that link to the same file. The limitation is dynamic based on the length of the file names used. A realistic average is approximately 150 hard links. When using 255 character file names, the limit is 14 links. We intend to raise the limitation to a more usable limit of 65535 links in a future maintenance update.
Other Limitations
At the moment, btrfs is not supported as a seed device.
For More Information
For more information about btrfs, see the SUSE Linux Enterprise 11 documentation.
Locale Settings in ~/.i18n
If you are not satisfied with locale system defaults, change
the settings in ~/.i18n. Entries in
~/.i18n override system defaults from
/etc/sysconfig/language. Use the same
variable names but without the RC_ namespace
prefixes. For example, use LANG instead of
RC_LANG. For information about locales in
general, see "Language and Country-Specific Settings" in the
Administration Guide.
Configuration of kdump
The kernel is crashing or otherwise not behaving normally and a kernel core dump needs to be captured for analysis.
A description on how to setup kdump can be found at http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=3374462&sliceId=SAL_Public.
Realtime Applications
When running real-time applications on larger systems, lower
maximum latencies can be achieved by employing the new
disable_buffer_lru kernel command-line option.
This disables the per-CPU LRU in the buffer cache, and may thus
decrease overall filesystem performance.
JPackage Standard for Java Packages
Java packages are changed to follow the JPackage Standard
(http://www.jpackage.org/). Read the
documentation in
/usr/share/doc/packages/jpackage-utils/
for information.
Loading Unsupported Kernel Drivers
Every kernel module has a 'supported' flag. If this flag is not set, then loading this module will taint the kernel. Kernels which are tainted are not supported. To avoid this, unsupported Kernel modules are part of an extra RPM (kernel-<flavor>-extra). Since this would a problem for most desktops, the loading of those drivers is allowed by default.
To prevent the loading of unsupported kernel drivers automatically during
boot, change the line
allow_unsupported_modules 1 in
/etc/modprobe.d/unsupported-modules to
allow_unsupported_modules 0.
Nonexecutable Stack
Already introduced for SUSE Linux Enterprise Desktop 9 on the x86-64 (AMD64) architecture with 64-bit kernels, the Linux kernel in SUSE Linux Enterprise Desktop also supports nonexecutable stack (NX) on x86 for CPUs that support it (Intel Prescott and AMD64) with 32-bit kernels. For this to work, the kernel with PAE support, kernel-pae, must be installed. Go into YaST and install that kernel instead of your default kernel. For 64-bit kernels, all kernels support NX.
The nonexecutable stack improves the security of your system. Many security vulnerabilities are stack overflows, where an attacker overwrites the stack of your program by feeding oversized data to the application that fails to properly check the length. Depending on the details of the program (with a nonexecutable stack), these vulnerabilities may either not be exploitable (and only crash the program, resulting in a Denial of Service) or at least be significantly harder to exploit.
Some applications do require executable stacks. The compiler detects this during compilation and marks the binaries accordingly. The kernel enables an executable stack to allow them to work.
To provide a higher level of security on x86-64, the user can
pass noexec=on on the kernel command line.
The kernel then uses a nonexecutable stack unconditionally and
also marks the data section of a program as nonexecutable. This
provides a higher protection level than just the nonexecutable
stack, but potentially causes problems for some applications.
SUSE has not found any problems during testing the most commonly
used applications and services. Because it is not the default,
this has not been tested as extensively as the stack protection
alone, so SUSE only recommends this setup for servers after the
administrator has verified that all needed services continue
to function properly.
Ensure all your logs go through permanent local storage or the
network. For example, putting /var/log on a tmpfs file system means
that they will not survive a system boot. This limits your ability,
and the one of SUSE, to analyze log files in case of a support
request.
Exceptions are configurations where you save log files via syslog on a remote log server and permanently store the log files on the log server. Note: Not all log files can be redirected to a remote log server (e.g. yast-logs, boot logs and others); if these files are not available, support may be very hard to effectively diagnose issues and support the system.
For the latest version of SUSE Linux Enterprise Desktop 11 Release Notes, see http://www.novell.com/linux/releasenotes/i586/SUSE-SLED/11/.
If you were using a static IP with NetworkManager, you will lose this configuration while updating from SLED 10 SP4 to SLED 11. You must re-enter this information. The traditional networking method with ifup is not affected by this issue.
Name server lookup information of resolv.conf
configured with the traditional networking method with
ifup is missing after updating.
Kopete as shipped with KDE4 does not support the IRC protocol. Install and use xchat, if you want to participate in IRC messaging.
There is only limited graphics support on IBM SurePOS 700 4800-7X3 systems with 4820-2GN monitors. During a graphical installation you can encounter an error message from the monitor (OSD = On Screen Display) such as:
OUT OF RANGE H: -48.4 KHz V: -60.1 Hz.
To work around this issue try a different resolution, VESA or
text-mode for installation. Another option is to choose the native driver by
specifying acceleratedx=1 on the boot prompt. It might also
help to update the BIOS.
After system installation the problem no longer occurs and the graphics system is fully supported.
On the FIC GE2 platform (when using 24 BPP color depth and resolutions >= 1280x1024 on the DVI interface) stripes are displayed on the X server. This distorts all windows.
Changing to 16 BPP color depth seems to solve this problem.
For SUSE Linux Enterprise Desktop 11 documentation, see http://www.suse.com/documentation/sled11/, where you can download PDF documents. For installation with YaST software management or with zypper, packages are available on the installation media. Some of these packages are installed by default. These are the package names:
sled-installquick_en-pdf: SLED 11
Installation Quick Start
sled-gnomequick_en-pdf: SLED 11 GNOME Quick
Start
sled-kdequick_en-pdf: SLED 11 KDE Quick
Start
sled-gnomeuser_en-pdf: SLED 11 GNOME User
Guide
sled-kdeuser_en-pdf: SLED 11 KDE User
Guide
sled-apps_en-pdf: SLED 11 Application
Guide
sled-admin_en-pdf: SLED 11 Administration
Guide
sled-deployment_en-pdf: SLED 11 Deployment
Guide
sled-security_en-pdf: SLED 11 Security
Guide
sle-apparmor-quick_en-pdf : AppArmor 2.3.1
Quick Start
sle-audit-quick_en-pdf: Linux Audit Quick
Start
sled-xen_en-pdf: SLED 11 Virtualization
Guide
sled-tuning_en-pdf: SLED 11 Tuning
Guide
sled-manuals_en: the set of all SLED books
in HTML format
By default, Firefox does not honor settings made with the GConf
system. In order to make the GConf lockdown keys effective, edit
/usr/lib/firefox/local-configuration.js and set
config.use_system_prefs to
true. This file allows the administrator to set and lock
preferences that will apply to every Firefox user.
Read the READMEs on the CDs.
Get the detailed changelog information about a particular package from the RPM:
rpm --changelog -qp <FILENAME>.rpm
<FILENAME>. is the name of the RPM.
Check the ChangeLog file in the top level of CD1 for
a chronological log of all changes made to the updated packages.
Find more information in the docu directory
of CD1 of the SUSE Linux Enterprise Desktop 11 CDs. This directory includes PDF versions
of the SUSE Linux Enterprise Desktop 11 Installation Quick Start and Deployment Guides.
http://www.suse.com/documentation/sled11/ contains additional or updated documentation for SUSE Linux Enterprise Desktop 11.
Visit http://www.suse.com/products/ for the latest product news from SUSE and http://www.suse.com/download-linux/source-code.html for additional information on the source code of SUSE Linux Enterprise products.
SUSE 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, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE 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, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses. Please refer to http://www.novell.com/info/exports/ for more information on exporting SUSE software. SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright (c) 2010, 2011, 2012 SUSE. 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.
SUSE 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 other countries.
For SUSE trademarks, see Novell Trademark ad Service Mark list (http://www.novell.com/company/legal/trademarks/tmlist.html). All third-party trademarks are the property of their respective owners.