Novell suse linux enterprise server

SUSE Linux Enterprise Server

SUSE Linux Enterprise Server (SLES) is an adaptable and easy-to-manage platform that allows developers and administrators to deploy business-critical workloads on-premises, in the cloud and at the edge.

Quick Links

Modernize your Kubernetes with SUSE Rancher 2.6 — Learn more >

Why SUSE Linux Enterprise Server?

SUSE Linux Enterprise Server is an operating system that is adaptable to any environment – optimized for performance, security and reliability.

The SUSE Linux Enterprise “common code base” platform bridges traditional and software-defined infrastructure. Simplify workload migration, protect your traditional infrastructure, and ease the adoption of containers.

Modernize your IT infrastructure with SUSE Linux Enterprise Server’s multimodal architecture. With its cloud-agnostic design, SLES can easily transition to public cloud—Alibaba, Azure, AWS, Google, IBM, Oracle.

Connect to our developer community at SUSE Package Hub. Once you are ready to move to from development to production you can seamlessly transition from our community Linux distribution -openSUSE Leap — to SUSE Linux Enterprise with just a few clicks.

Trusted by the world’s leading enterprises

Adaptability

Includes APIs and services that make it possible to write applications that can work with the widest range of architectures, servers, storage and network options available. This approach allows SLES to adapt to any operating environment and enables smooth workload migrations between them.

Security and Compliance

SUSE engineers promptly react to security incidents, and deliver premium quality security updates. The configuration, auditing and automation features of SUSE Manager make it easy to ensure compliance with internal security policies and external regulations.

Business Continuity

SUSE Linux Enterprise High Availability Extension, geo-clustering, and SUSE Linux Enterprise Live Patching improves business continuity and saves costs by reducing downtime, increasing service availability and enhancing security and compliance.

Virtualization

Each SUSE Linux Enterprise Server subscription includes support for the leading hypervisor technologies and cloud platforms. Maximize your flexibility and lower costs without sacrificing performance, security or reliability.

Источник

Release Notes for SUSE Linux Enterprise Server 11

Version 11.0.0.32, 2009-11-06

These release notes are generic for all products that are part of our SUSE Linux Enterprise Server 11 product line. Some parts may not apply to a particular architecture or product. Where this is not obvious, the specific architectures or products are explicitly listed.

Startup and Deployment Guides can be found in the docu directory on the media. Documentation (if installed) can also be found below the /usr/share/doc/ directoy in an installed system.

This Novell product includes materials licensed to Novell under the GNU General Public License (GPL). The GPL requires that Novell makes available certain source code that corresponds to the GPL-licensed material. The source code is available for download at http://www.novell.com/linux/source/. Also, for up to three years from Novell’s distribution of the Novell product, upon request Novell will mail a copy of the source code. Requests should be sent by e-mail to sle_source_request@novell.com or as otherwise instructed at http://www.novell.com/linux/source/. Novell may charge a fee to recover its reasonable costs of distribution.

Chapter 1. SUSE Linux Enterprise Server

SUSE Linux Enterprise Server is a highly reliable, scalable, and secure server operating system, built to power mission-critical workloads in both physical and virtual environments. It is an affordable, interoperable, and manageable open source foundation. With it, enterprises can cost-effectively deliver core business services, enable secure networks, and simplify the management of their heterogeneous IT infrastructure, maximizing efficiency and value.

The only enterprise Linux recommended by Microsoft and SAP, SUSE Linux Enterprise Server is optimized to deliver high-performance mission-critical services, as well as edge of network, and web infrastructure workloads.

Designed for interoperability, SUSE Linux Enterprise Server supports open standard CIM interfaces and can be managed by any management solution utilizing CIM.

This modular, general purpose operating system runs on five processor architectures and is available with optional extensions that provide advanced capabilities for real time computing, high availability clustering, and running .NET applications on Linux.

SUSE Linux Enterprise Server is optimized to run as a high performance guest on leading hypervisors and supports an unlimited number of virtual machines per physical system with a single subscription, making it the perfect guest operating system for virtual computing.

SUSE Linux Enterprise Server is backed by award-winning support from Novell, an established technology leader with a proven history of delivering enterprise-quality support services.

Chapter 2. Installation

SUSE Linux Enterprise Server can be deployed in three ways:

Virtual Machine in paravirtualized environments

CJK Languages Support in Text-Mode Installation

CJK (Chinese, Japanese, and Korean) languages do not work properly during text-mode installation if framebuffer is not used (TextMode selected in boot loader).

There are three alternatives to resolve this issue:

Use English or some other non-CJK language for installation and then switch to the CJK language later on a running system using YaST -> System -> Language.

Use your CJK language during installation, but do not choose TextMode in 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 Installation.

Use graphical installation (or install over SSH or VNC).

Installation using Persistent Device names

The installer uses persistent device names by default. If you plan to add additional storage devices to your system after the OS 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, , use the YaST2 partitioner. For each partition, select «Edit» and go to the «FStab Options» 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. Just start the module and select «Finish» to write the new proposed configuration to disk. This needs to be done before adding new storage devices.

Using qla3xxx and qla4xxx drivers at the same time

QLogic iSCSI Expansion Card for IBM BladeCenter provides both Ethernet and iSCSI functions. Some parts on the card are shared by both functions. The current qla3xxx (Ethernet) and qla4xxx (iSCSI) drivers support Ethernet and iSCSI function individually. They do not support using both functions at the same time. Using both Ethernet and iSCSI functions at the same time may hang the device and cause data loss and filesystem corruptions on iSCSI devices, or network disruptions on Ethernet.

Boot the installation with brokenmodules=qla3xxx or brokenmodules=qla4xxx to prevent one of the drivers from loading.

Using iSCSI Disks When Installing

To use iSCSI disks during installation it is necessary to add the following parameter to the boot option line: withiscsi=1

During installation an additional screen appears that provides the option to attach iSCSI disks to the system and use them in the installation process.

Booting from an iSCSI server on i386, x86_64 and ppc64 is supported, when iSCSI enabled firmware is used.

Using EDD Information for Storage Device Identification

EDD information ( /sys/firmware/edd/ ) to identify your storage devices are used by default. To disable this, change the installer default settings using an additional kernel parameter.

BIOS provides full EDD information (found in /sys/firmware/edd/ )

Disks are signed with a unique MBR signature (found in /sys/firmware/edd/ /mbr_signature )

Add parameter edd=off to the kernel parameters to disable EDD.

Automatic installation with AutoYaST in an LPAR (System z)

For automatic installation with AutoYaST in an LPAR,it is required that the parmfile used for such an installation has blank characters at the beginning and at the end of each line (the first line need not start with a blank). The number of characters in one line should not exceed 80 characters.

Adding DASD or zFCP disks during installation (System z)

Adding of DASD or zFCP disks is not only possible during the installation workflow, but also when the installation proposal is shown. To add disks at this stage, please click on the «Expert» tab and scroll down. There the DASD and/or zFCP entry is shown. These added disks are not shown in the partitioner automatically. To make the disks visible in the partitioner, you have to click on the expert label and select «reread partition table». This may reset any previously entered information.

Network installation via eHEA on POWER

If network installation via the IBM eHEA Ethernet Adapter on POWER systems is desired, no huge (16GB) pages may be assigned to the partition during installation.

For more «Infrastructure, Package and Architecture specific Information», please see the respective chapter below.

Chapter 3. Features and Versions

3.1. Linux Kernel and Toolchain

Linux kernel 2.6.27

3.2. Server

Note: version numbers do not necessarily give the final patch- and security-status of an application, as Novell may have added additional patches to the specific version of an application.

Apache 2.2.10 — Webserver

Bind 9.5.0P2 — The Bind Domain Name Server

3.3. Desktop

GNOME was updated to the latest version and uses PulseAudio for sound.

KDE was updated to the latest 4.1.3 version.

3.4. Security

The common PAM configuration files ( /etc/pam.d/common-* ) are now created and managed with pam-config .

Basic SELinux enablement

In addition to AppArmor, SELinux capabilities were added to SUSE Linux Enterprise Server. While it is not enabled by default, and not supported, this will allow customers to enable and run SELinux with SUSE Linux Enterprise Server if they want to do so.

What does SELinux basic enablement mean?

The kernel will ship with SELinux support.

We will apply SELinux patches to all “common” userland packages.

The libraries required for SELinux (libselinux, libsepol, libsemanage, etc.) were added to openSUSE and SUSE Linux Enterprise.

However, we are not offering enterprise class support for SELinux at this time; thus we will run QA with SELinux disabled – to make sure that SELinux patches don’t break the default delivery and the majority of packages.

The SELinux specific tools are shipped as part of the default distribution delivery. However, packages such as checkpolicy, policycoreutils, selinux-doc are not supported.

We will not be shipping any SELinux policies in the distribution. (Reference and minimal policies may be available from the repositories at some future point.)

By enabling SELinux in our codebase, we add missing pieces of code that exist in the community already, and we allow those who wish to use SELinux to do so conveniently without having to replace a big portion of the distribution.

Enablement for TPM/Trusted Computing

SUSE Linux Enterprise Server 11 comes with support for Trusted Computing technology. To enable your system’s TPM chip, make sure that the «security chip» option in your BIOS is selected. TPM support is entirely passive, meaning that measurements are being performed, but no action is taken based on any TPM-related activity. TPM chips manufactured by Infineon, NSC and Atmel are supported, in addition to the virtual TPM device for Xen.

The corresponding kernel drivers are not loaded automatically — please enter: find /lib/modules -type f -name «tpm*.ko» and load the kernel modules for your system manually or via MODULES_LOADED_ON_BOOT in /etc/sysconfig/kernel.

If your TPM chip with taken ownership is configured in Linux and available for use, you may read PCRs from /sys/devices/*/*/pcrs .

The tpm-tools package contains utilities to administer your TPM chip, and the trousers package provides «tcsd» — the daemon that allows userland programs to communicate with the TPM driver in the Linux kernel. Tcsd can be enabled as a service for the runlevels of your choice.

To implement a trusted («measured») boot path, please use the package trustedgrub instead of the grub package as your bootloader. The trustedgrub bootloader does not display any graphical representation of a boot menu for informational reasons.

3.5. Network

SUSE Linux Enterprise Server can be installed in an IPv6 environment and run IPv6 applications. When installing via network, don’t forget to boot with «ipv6=1» (accept v4 and v6) or «ipv6only=1» (only v6) on the kernel command line. Please see the Deployment Guide for additional details. See also «IPv6 Implementation and Compliance» below.

10G networking capabilities

Support for traceroute over TCP

Open-FCoE is an implementation of the Fibre Channel over Ethernet working draft. Fibre Channel over Ethernet is the encapsulation of Fibre Channel frames in Ethernet packets. It allows users with a FCF (Fibre Channel over Ethernet Forwarder) to access their existing Fibre Channel storage using an Ethernet adapter. When leveraging DCB’s PFC technology to provide a loss-less environment, Open-FCoE can run SAN and LAN traffic over the same link.

Data Center Bridging (DCB)

Data Center Bridging (DCB) is a collection of Ethernet enhancements designed to allow network traffic with differing requirements (e.g., highly reliable, no drops vs. best effort vs. low latency) to operate and co-exist on Ethernet. Current DCB features are:

Enhanced Transmission Selection (aka Priority Grouping ) to provide a framework for assigning bandwidth guarantees to traffic classes.

Priority-based Flow Control (PFC) provides a flow control mechanism which can work independently for each 802.1p priority.

Congestion Notification provides a mechanism for end-to-end congestion control for protocols which do not have built-in congestion management.

3.6. Systems Management

Improved update stack

SUSE Linux Enterprise Server 11 comes with an improved update stack and a new command line tool — zypper — to manage the repositories and install/update packages.

Enhanced YaST partitioner

Extended built-in management infrastructure

CIM enablement with SFCB CIMOM.

Support for Web Services for Management (WS-Management)

The WS-Management protocol is supported via the openwsman project, providing client (package: openwsman-client) and server (package: openwsman-server) implementations. This allows for interoperable management with Windows winrm stack.

3.7. Resource Management

Kernel Resource Management

cgroups (Control groups, replaces and enhances CKRM from SUSE Linux Enterprise Server 9), with fine-grained control of CPU, Memory and Devices.

Added Novell developed, open source ‘cpuset’ command-line tool.

3.8. Other

EVMS2 was replaced by LVM2

The default file system in new installations has been changed from ReiserFS to ext3. A public statement can be found at http://www.novell.com/linux/techspecs.html?tab=0 and in our FAQ at: http://www.novell.com/linux/filesystems/faq.html

UEFI enablement on AMD64/Intel64

3.9. System z

Improved handling dynamic subchannel mapping

Multipath IPL (IPL through IFCC)

Decimal Floating Point and z10 instructions support

Standby CPU activation/deactivation

Vertical CPU Management

Standby memory add via sclp

Dynamic memory attach/detach (req. z/VM 5.4)

Exploitation of DCSS above 2G (req. z/VM 5.4)

Extra kernel parameter via VMPARM

Provide CMS script for initial SUSE Linux Enterprise Server 11 intallation under z/VM

FICON Hyper PAV exploitation

FCP Automatic port discovery

FCP LUN discovery tool

Updated FCP HBA API

Installation support on 2nd Ports with OSA Express-3 (with 2 port per CHPID=4 Ports)

HiperSocket Layer3 support for Ipv6 (for z/OS communication)

CTCMPC merge into CTC driver: ctcm

Exploitation of Long Random Numbers

New HW Crypto Cards enablement

Call Home Data support (sclp cpi sysfs interface and service)

Kernel Message Catalog

Shutdown actions interface and tools

Large image dump on DASD

FCP enhanced trace facility

FCP Performance Data Collection

Web 2.0 Open Source Stack in SUSE Linux Enterprise Software Development Kit

Functionality implemented in SUSE Linux Enterprise Server 11 (and SUSE Linux Enterprise Server 10 Service Pack 2.)

Provide Linux filesystem data into z/VM monitor stream

Provide Linux process data into z/VM monitor stream

System z support for processor degradation

In-Kernel crypto exploitation of new CP Assist functions

Linux CPU Node Affinity

Support for OSA 2 Ports per CHPID

cpuplugd to automatic adapt CPU and/or memory

Dynamic CHPID reconfiguration via SCLP — tools

skb scatter-gather support for large incoming messages — QETH Exploitation

Support for HiperSockets in Layer 2 mode (with IPv4 and IPv6)

Chapter 4. Support Statement for SUSE Linux Enterprise Server

To receive support, customers need an appropriate subscription with Novell; for more information, please see: http://www.novell.com/products/server/services_support.html.

4.1. General Support Statement

The following definitions apply:

L1: Installation and problem determination, which means technical support designed to provide compatibility information, installation configuration assistance, usage support, on-going maintenance and basic troubleshooting. Level 1 Support is not intended to correct product defect errors.

L2: Reproduction of problem isolation, which means technical support designed to duplicate customer problems, isolate problem area and potential issues, and provide resolution for problems not resolved by Level 1 Support.

L3: Code debugging and problem resolution, which means technical support designed to resolve complex problems by engaging engineering in patch provision, and resolution of product defects which have been identified by Level 2 Support.

For contracted customers and partners, SUSE Linux Enterprise Server 11 will be delivered with L3 support for all packages, except the following:

Technology Previews and SELinux Basic Enablement

Sounds, Graphics, Fonts and Artwork

Packages, which require an additional customer contract

Packages on the Software Development Kit (SDK)

Novell will only support the usage of original (e.g., unchanged or un-recompiled) packages.

4.2. Software which needs specific contracts

The following packages require additional support contracts to be obtained by the customer, in order to receive full support.

BEA Java (Itanium only)

WebSphere CE Application Server

4.3. Technology Previews

Technology Previews are not supported or only supported minimally. These features are mainly included for customer convenience. They may be functionally incomplete, instable or in other ways not suitable for production use.

Hot-Add of Memory

Hot-Add-memory is currently only supported on the following hardware:

IBM eServer xSeries x260, single node x460, x3800, x3850, single node x3950

certified systems based on recent Intel Xeon Architecture

certified systems based on recent Intel IPF Architecture

all IBM System p servers with POWER5 or POWER6 processor and recent firmware

If your specific machine is not listed, please call Novell support to confirm whether or not your machine has been successfully tested. Also, please regulary check our maintenance update information, which will explicitly mention the general availability of this feature.

Restriction on using IBM eHCA InfiniBand adapters in conjunction with Hot-Add of Memory on IBM System p:

The current eHCA Device Driver will prevent dynamic memory operations on a partition as long as the driver is loaded. If the driver is unloaded prior to the operation and then loaded again afterwards, adapter initialization may fail. A Partition Shutdown / Activate sequence on the HMC may be needed to recover from this situation.

Internet Storage Naming Service (iSNS)

The Internet Storage Naming Service (iSNS) package is by design suitable for secure internal networks only. Novell will continue to work with the community on improving security on this.

Linux Filesystem Capabilities

Our kernel is compiled with support for Linux Filesystem Capabilities. This is disabled per default and can be enabled by adding file_caps=1 as kernel boot option.

The eCryptfs kernel modules and the ecryptfs-utils package shipped with SUSE Linux Enterprise Server 11 are a preview of a stacked cryptographic filesystem for Linux.

The Ext4 kernel modules and userland tools shipped with SUSE Linux Enterprise Server 11 are a preview of a new filesystem for Linux.

The PerfMon2 kernel modules and userland tools shipped with SUSE Linux Enterprise Server 11 are a preview of a performance monitoring tool for Linux. It will be replaced with a successor if accepted and integrated into the official Kernel.

SUSE Linux Enterprise Server 11 contains KVM as an additional virtualization solution. It is not supported by Novell, but an area of interest for future development and deliveries.

The puppet tools shipped with SUSE Linux Enterprise Server 11 are a Technology Preview.

biosdevname in its simplest form takes a kernel name as an argument, and returns the BIOS-given name it «should» be. This is necessary on systems where the BIOS name for a given device (e.g., the label on the chassis is «Gb1») doesn’t map directly and obviously to the kernel name (e.g., eth0).

Read-Only Root Filesystem

It is possible to run SUSE Linux Enterprise Server 11 on a read-only root filesystem. Due to the large number of possible configurations, this is currently not a supported scenario.

The /tmp and /var/tmp 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.

Chapter 5. Software Development Kit

Novell provides a Software Development Kit (SDK) for SUSE Linux Enterprise 11. This SDK contains libraries, development-environments and tools along the following patterns:

Linux Kernel Development

Qt 4 Development

Ruby on Rails Development

Version Control Systems

Chapter 6. Update-Related Notes

This section includes update-related information for this release:

Migration is supported from SUSE Linux Enterprise Server 10 SP2 via bootable media (incl. PXE boot).

Kernel split in different packages

With SUSE Linux Enterprise Server 11 the kernel RPMs are split in different parts:

Very reduced hardware support, intended to be used in virtual machine images.

Extends the base package; contains all supported kernel modules.

All other kernel modules which may be useful, but which are not supported. This package will not be installed by default.

SUSE Linux Enterprise Server uses tickless timers. This can be disabled by adding nohz=off as a boot option.

SUSE Linux Enterprise Server will no longer contain any development packages, with the exception of some core development packages necessary to compile kernel modules. Development packages are available in the SUSE Linux Enterprise Software Development Kit.

Displaying manual pages with the same name

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 revert back to the previously used method, please set MAN_POSIXLY_CORRECT=1 in a shell initialization file such as

YaST LDAP Server no longer using /etc/openldap/slapd.conf

The YaST LDAP Server module no longer stores the configuration of the LDAP Server in the file /etc/openldap/slapd.conf . It uses OpenLDAP’s dynamic configuration backend, which stores the configuration in an LDAP database it self. That database consists of a set of .ldif files in the directory /etc/openldap/slapd.d . You should — usually — not need to access those files directly. To access the configuration you can either use the yast2-ldap-server module or any capable LDAP client (e.g., ldapmodify, ldapsearch, etc.). For details on the dynamic configuration of OpenLDAP, please look at the OpenLDAP Administration Guide.

This release of SUSE Linux Enterprise Server ships with Novell 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 Novell AppArmor. For detailed information about using Novell 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 may 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 many 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.

Updates with alternative Bootloader Programs (non-Linux)

Updating from SUSE Linux Enterprise Server 10 SP2 in a system where alternative bootloaders (not grub) are installed in the MBR (Master Boot Record) might override the MBR and place grub as the primary bootloader into the system.

We propose doing a fresh installation in this case. Don’t forget to backup your data!

It is always a good plan to keep data separated from the system software. In other words, /home, /srv, . and other volumes containing data should be on a separate partition, volume group or logical volume. The YaST partitioning module will propose doing this.

Upgrading MySQL to SUSE Linux Enterprise Server 11

During the upgrade to SUSE Linux Enterprise Server 11 MySQL is also upgraded to the latest version. To complete this migration you may have to upgrade your data as described in the MySQL documentation.

Fine-Tuning Firewall Settings

SuSEfirewall2 is enabled by default. That means that by default you cannot log in from remote systems. This also interferes with network browsing and multicast applications, such as SLP and Samba («Network Neighborhood»). You can fine-tune the firewall settings using YaST.

Upgrading from SUSE Linux Enterprise Server 10 SP2 to SUSE Linux Enterprise Server 11 with the Xen Hypervisor may have incorrect network configuration

We have improved the network configuration from SUSE Linux Enterprise Server 10 to SUSE Linux Enterprise Server 11: If you install SUSE Linux Enterprise Server 11 and configure Xen, you get a bridged setup through YaST. However, if you upgrade from SUSE Linux Enterprise Server 10 SP2 to SUSE Linux Enterprise Server 11, the upgrade does not configure the bridged setup automatically.

Please start the «YaST Control Center», choose «Virtualization» and then «Install Hypervisor and Tools» to start the bridge proposal for networking. Alternatively you can call

on the commandline.

Upgrading from SUSE Linux Enterprise Server 10 SP2 to SUSE Linux Enterprise Server 11 with the Xen Hypervisor does not preserve xen configuration options

Due to changes in default settings, the Xen Management Daemon (xend) configuration file is replaced during upgrade. Customizations are saved to /etc/xen/xend-config.sxp.rpmsave for merging with the new configuration file.

SGI Altix and SGI Altix XE systems using SGI REACT for Linux and SUSE Linux Enterprise Server 10 cannot upgrade to SUSE Linux Enterprise Server 11 at this time. For more information, please contact SGI Technical Support at support@sgi.com or http://www.sgi.com/support/supportcenters.html.

LILO configuration via YaST/AutoYaST

he configuration of the LILO bootloader via YaST/AutoYaST is still possible, but not supported on the x86/x86_64 architecture any more. For further information please consult Novell TID 7003226 http://www.novell.com/support/documentLink.do?externalID=7003226.

Chapter 7. Deprecated Functionality

The following list item were removed with this major release of SUSE Linux Enterprise Server.

The JFS filesystem is no longer supported and the utilities were removed from the distribution.

For the future strategy and development with respect to volume- and storage-management on SUSE Linux Enterprise, please see: http://www.novell.com/linux/volumemanagement/strategy.html

The mapped-base functionality, which is used by 32-Bit applications that need a larger dynamic data space (such as database management systems), was replaced with flexmap.

The following list of current functionality is deprecated and will be removed with the next Service Pack or major release of SUSE Linux Enterprise Server.

The reiserfs filesystem is fully supported for the lifetime of SUSE Linux Enterprise Server 11 specifically for migration purposes. We will however remove support for creating new reiserfs filesystems starting with SUSE Linux Enterprise Server 12.

The sendmail package is deprecated and might be removed with SUSE Linux Enterprise Server 12.

The lprng package is deprecated and will be removed with SUSE Linux Enterprise Server 12.

The dhcp-client package is deprecated and will be removed with SUSE Linux Enterprise Server 12.

The qt3 package is deprecated and will be removed with SUSE Linux Enterprise Server 12.

openswan and strongswan packages will be consolidated.

syslog-ng will be replaced with rsyslog

The smpppd package is deprecated and will be removed with one of the next Service Packs or SUSE Linux Enterprise Server 12.

The RAW devices are deprecated and will be removed with one of the next Service Packs or SUSE Linux Enterprise Server 12.

IBM Java 1.4.2 is supported with SUSE Linux Enterprise Server 11 specifically for migration purposes. We will however remove support for this specific Java version with SUSE Linux Enterprise Server 12 latest.

The use of a 32-bit hypervisor as a virtualization host is deprecated but provided for migration purposes. Novell may remove this functionality with a future service pack. 32-bit virtual guests are not affected and are fully supported with the provided 64-bit hypervisor.

Chapter 8. Infrastructure, Package and Architecture specific Information

8.1. Systems Management

Modified operation against Novell Customer Center

Effective on 2009-01-13, provisional registrations will be disabled in the Novell Customer Center. Registering an instance of SUSE Linux Enterprise Server or Open Enterprise Server (OES) products now requires a valid, entitled activation code. Evaluation codes for reviews or proofs of concept can be obtained from the product pages and from the download pages on novell.com. If a device is registered without a code at setup time, a provisional code is assigned by Novell Customer Center (NCC) to the device, and an entry for it is made in your NCC list of devices. No update repositories are assigned to the device at this time. Once you are ready to assign a code to the device, starting the YaST Novell Customer Center registration module and putting in the appropriate code (replacing the un-entitled provisional code that NCC generated) will fully entitle the device and activate the appropriate update repositories.

Operation against Subscription management Tool

Operation under the Subscription Management Tool (SMT) package and registration proxy is not affected. Registration against SMT will assign codes automatically from your default pool in NCC until all entitlements have been assigned. Registering additional devices once the pool is depleted will result in the new device being assigned a provisional code (with local access to updates), and the SMT server will provide appropriate notification to the administrator that these new devices need to be entitled.

The minimal pattern provided in YaST’s Software Selection Dialog targets experienced customers and should be used as a base for your own specific software selections.

Please do not expect that an unchanged / not-extended minimal pattern provides a useful basis for your business needs.

This pattern does not include any dump- or logging-tools. To fully support your configuration, Novell Technical Services (NTS) will request the installation of all the tools which are needed for further analysis, in case of a support request.

SPident is a tool to identify the Service Pack level of the current installation. This tool is not delivered with SUSE Linux Enterprise Server 11 GA, but is replaced by the new SAM tool (package «suse-sam»).

Источник