Success Stories. Investor Relations. Social Impact. Merchandise Store. Communications Preferences. SUSE Linux Enterprise Server Improve uptime, increase efficiency, and accelerate innovation with best-of-breed performance and reduced risk. Thank you! Please wait while we send you to your download.
Thank you for your interest in SUSE. Have an account? Log In. Success Please see steps below Your account has been created. An email will be sent to the address provided for account verification. 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[], which maps to Embedded NIC[] as labeled on server chassis.
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. Select one of the other VGA modes instead.
Use a 4k sector harddisk in 4k mode in this case, the 2 TiB limit will become a 16 TiB limit. This partition must be one of the first 3 partitions and end below the 2 TiB limit. 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 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 and select Propose New Config to switch the boot loader to using the persistent device name, or manually adjust all boot loader sections.
Then select Finish to write the new proposed configuration to disk. To use iSCSI disks during installation, passing the withiscsi boot parameter is no longer needed. During installation, an additional screen provides the option to attach iSCSI disks to the system and use them in the installation process.
Some parts on the card are shared by both functions. In contrast to previous SLES releases, using both functions at the same time is now supported. For automatic installation with AutoYaST in an LPAR, the parmfile used for such an installation must have blank characters at the beginning and at the end of each line the first line does not need to start with a blank.
The number of characters in one line should not exceed To add disks at this stage, please click on the Expert tab and scroll down. These added disks are not displayed in the partitioner automatically.
To make the disks visible in the partitioner, you have to click on Expert and select reread partition table. This may reset any previously entered information. In the past modules without proper cryptographic signature loaded into kernel caused the kernel's "forced module load" flag to be set. As a result, tracing was disabled for such modules.
A flag has been introduced to indicate modules with invalid signature. Previous implementations of vDSO for getcpu and gettimeofday are costly in terms of processor cycles. The new functions of vDSO for getcpu and gettimeofday mitigate this issues and allow applications to run with improved performance.
Lustre 2. To allow the build of kernel modules for Lustre 2. The default and recommended settings for kdump have changed in SP3 to provide faster dumping on machines with a large amount of RAM.
This includes changing the default dump level to 31 filter out as much as possible and using the LZO compression algorithm. This mode allows users to temporarily disable packet inspection and maintain connectivity under heavy network traffic. QEMU guests spawned by libvirt are exposed to a large number of system calls that go unused for the entire lifetime of the process.
This allows execution of QEMU guests with reduced exposure to kernel system calls. Enhances the current makedumpfile filtering to eliminate complex data structures and cryptographic keys. This is possible thanks to support for eppic language. This feature enables us to specify rules to scrub data in a dumpfile with eppic macro instead of the current configuration file makedumpfile. Note: in the following text version numbers do not necessarily give the final patch- and security-status of an application, as SUSE may have added additional patches to the specific version of an application.
This upgrade involves a change of the database format and the database needs to be converted before MySQL can run again. Therefore MySQL is not running directly after the upgrade.
This version in SP3 unlike the one in SP2 , ignores. The libraries required for SELinux libselinux, libsepol, libsemanage , etc. Quality Assurance is performed with SELinux disabled—to make sure that SELinux patches do not break the default delivery and the majority of packages.
The SELinux specific tools are shipped as part of the default distribution delivery. Reference and minimal policies may be available from the repositories at some future point. By enabling SELinux in our codebase, we add community code to offer customers the option to use SELinux without replacing significant parts of the distribution. TPM support is entirely passive, meaning that measurements are being performed, but no action is taken based on any TPM-related activity. 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.
To implement a trusted "measured" boot path, 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.
Our kernel is compiled with support for Linux File System Capabilities. This is disabled by default. For more information, see the Deployment Guide and also Section Data Center Bridging DCB is a collection of Ethernet enhancements designed to allow network traffic with differing requirements e. 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 Congestion Notification provides a mechanism for end-to-end congestion control for protocols, which do not have built-in congestion management. The load balancer has been enhanced to fully support IPv6 fragmented extension headers and is now RFC compliant.
This allows access to NFS in a scalable way. Seccomp filters are expressed as a Berkeley Packet Filter BPF program, which is not a well understood interface for most developers. The libseccomp library provides an easy to use interface to the Linux Kernel's syscall filtering mechanism, seccomp. The libseccomp API allows an application to specify which syscalls, and optionally which syscall arguments, the application is allowed to execute, all of which are enforced by the Linux Kernel.
See the btrfs 8 manual page for more information. LXC now comes with support for network gateway detection. This feature will prevent a container from starting, if the network configuration setup of the container is incorrect. For instance, you must make sure that the network address of the container is within the host ip range, if it was set up as brigded on host.
You might need to specify the netmask of the container network address using the syntax " lxc. When using DHCP to assign a container network address, ensure " lxc. Previously a container would have been started but the network would not have been working properly. Now a container will refuse to start, and print an error message stating that the gateway could not be set up.
For containers created before this update we recommend running rcnetwork restart to reestablish a container network connection. For containers created before the update, we recommend to install the packages "supportconfig", "sysconfig", and "iputils" using zypper.
SUSE Linux Enterprise Server 11 provides an improved update stack and the new command line tool zypper to manage the repositories and install or update packages. The WS-Management protocol is supported via Openwsman, providing client package: openwsman-client and server package: openwsman-server implementations. WebYaST is an easy to use, web-based administration tool targeted at casual Linux administrators.
WebYaST is an add-on product. After installation, follow these steps:. For information about migrating to SP3, see Section Hot-add memory and CPU is supported and tested for both bit and bit systems when running vSphere 4. Org driver combo is used instead of the "mga" X. Org driver if machine is running in UEFI secure boot mode.
The driver does not load in other cases and a warning message is written into the kernel log. The Transparent Inter-Process Communication protocol TIPC allows applications in a cluster environment to communicate quickly and reliably with each other, regardless of their location within the cluster. TIPC includes a network topology service that lets applications track both functional and physical changes in the network, helping to synchronize startup of distributed applications and their responses to failure conditions.
A socket API is used to interact with the topology service and other applications. Address assignment and bearer configuration is managed from a userspace application called tipc-config. Emulex 10Gb E Virtual Fabric adapter firmware version 4. This issue occurs due to limitations of the virtual Ethernet bridge in the adapter.
The driver also includes the latest bug fixes to the driver available at the time of the driver update cutoff date. The enic driver was updated to version 1. Scientific support will install all the MPIs and related tests.
Verify the following package versions or greater are installed: infinipath-psm Install the libipathverbs package. This is part of installation source but does not get installed in first step. At this time we did not send FCoE capable again since we already sent it in step 2. Kiosk style systems cash registers, vending machines, etc. Virtually all UI toolkits wait for a button relase to happen to accept a 'click' and to record the location to determine the widget element 'clicked'.
This behavior is undesirable for kiosk style systems. At the same time kiosk style systems use a fixed window placement: the user should not be able to 'drag' windows around. Use of a special UI toolkits developed for this purpose. However this would limit the choice of toolkits. Use of touchscreens which syntesize a 'button release' event right after a 'button press' regardless if the finger is still touching the screen or not.
Such touch screens exist. A customized input driver which is able to emulate this feature: This provides the greatest flexibility as it will work with all touch screens and toolkits.
For this the 'klick-on-touch' and 'klick-on-release' feature has been added to the updated evdev input driver xfinput-evdev. The feature can be enabled either statically using a config file or 'on-the'fly' at run time by changing the approriate properties on the input device. Please refer to the evdev man page man 4 evdev.
Device properties can be set by an X application for instance a cash register software or generically using the tool 'xinput' refer to 'man 1 xinput'. The Gnome desktop provides a tool to do this and save the settings persistently across sessions. If you select an unsupported mode, it will be ignored and a monitor preferred default mode will be used instead.
The key update in version 2. To match vendor specific data structures and avoid missleading interpretation, SMARTmon tools include the new data structures. The upstream end-of-life for version 9. Customers need to switch to a newer supported version until then.
PostgreSQL was updated to version 9. Thus there is enough time for switching. This update introduced several stability bugfixes and support for handling IPv6. Python 2. Whenever possible, Python 2. In case of conflict, Python 2. Some significant new packages have been added to the standard library, such as the multiprocessing and json modules.
This SDK contains libraries, development environments and tools along the following patterns:. To upgrade a PostgreSQL server installation from version 8. Formerly dump and restore was needed that was much slower. 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. In PostgreSQL terms the major version consists of the first two components of the version number, i. So, the packages for Postgresql 9. 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.
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.
The packages of the new PostgreSQL major version need to be installed. For SLE11 this means to install postgresqlserver and all the packages it depends on. No packages from SP2 repositories are needed for installation or upgrade, not even from the SP2 update repositories. It is important to remember that the version number is not sufficient to determine which bugfixes are applied to a software package. In case you add SP2 update repositories, be aware of one characteristic of the repository concept: Version numbers in the SP2 update repository can be higher than those in the SP3 repository.
Thus, if you update with the SP2 repositories enabled, you may get the SP2 version of a package instead of the SP3 version. This is admittedly unfortunate. It is recommended to avoid using the version from a lower SP, because using the SP2 package instead of the SP3 package can result in unexpected side effects. Thus we advise to switch off all the SP2 repositories, if you do not really need them. Keep old repositories only, if your system depends on a specific older package version.
If you need a package from a lower SP though, and thus have SP2 repositories enabled, make sure that the packages you intended to upgrade have actually been upgraded. Summarizing: If you have an SP2 installation with all patches and updates applied, and then migrate off-line to SP3 GA, you will see a downgrade of some packages. This is expected behavior.
To migrate the system to the Service Pack 3 level with zypper , proceed as follows:. Run zypper ref -s to refresh all services and repositories. Run zypper patch to install package management updates. Now the installed products contain information about distribution upgrades and which migration products should be installed to perform the migration.
Run zypper ref -s to refresh services and repositores. Check the repositories using zypper lr. Add more SP3 repositories here if needed, e. If you make sure that only repositories, which you migrate from, are enabled, you can omit the --from parameters.
Confirm the message to continue updating the RPM packages. Run zypper patch after re-registering. Some products donot use the update repositories during the migration and they are not active at this point of time. PXE boot. Online migration from SP2 to SP3 is not supported if debuginfo packages are installed. There are two approaches to solve it, if you are using AutoYaST adjust IP addresses and hostnames according to your environment!
All other kernel modules which may be useful but are not supported. This package will not be installed by default. SUSE Linux Enterprise Server will no longer contain any development packages, with the exception of some core development packages necessary to compile kernel modules. 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.
That database consists of a set of. 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.
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. 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.
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. Before updating, check the configuration of your boot loader to assure that it is not configured to modify any system areas MBR, settings active partition or similar.
A hostname and domain are proposed by default. If your system is part of a network, the hostname has to be unique in this network, whereas the domain name has to be common to all hosts on the network. Also enter the IP Address and Netmask for this host. The IP address must be unique and the netmask has to be common to all hosts on the network. The next dialog continues with the network configuration; see Figure 2. To get technical support and product updates, you need to register and activate your product with the Novell Customer Center; see Figure 2.
This dialog provides assistance for doing so. If you provide the registration code now, operating system updates will be installed automatically during the installation of the system. After confirming the registration data, the system will be configured with the supplied settings. This wizard-based installation scenario disables the firewall SuSEfirewall2 completely. If needed, you can activate the firewall after the installation. If you activate the firewall after the installation, you must open all required ports manually.
For more information about required ports, see Section 5. You can change them according to your needs. Otherwise, it is possible to just prepare the SAP product installation with Only create SAP Business One file systems, do not install SAP products now , or completely interrupt the installation process at this point with Finish wizard and proceed to OS login and resume it after a system restart.
Otherwise, this option will not create a new file system and the installation workflow ends at this point. The functionality is the same, but the layout of the dialogs is different; the left progress pane is only displayed when continuing with the installation without a restart. The following screen shots document the installation with the SAP Product Installer that runs after a restart of the system.
The location can either be a local source or a remotely provided installation source. If you want to install from an NFS source, you must enter the name of the server and the complete path to the media data.
For more information about setting up a remote installation server, see Chapter 4, Remote Installation from a Network Server. See Figure 2. Click Help for information. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed as many as fit reasonably on the actual cover, and continue the rest onto adjacent pages. If you publish or distribute Opaque copies of the Document numbering more than , you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy directly or through your agents or retailers of that edition to the public. It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it.
In addition, you must do these things in the Modified Version:. Use in the Title Page and on the covers, if any a title distinct from that of the Document, and from those of previous versions which should, if there were any, be listed in the History section of the Document. You may use the same title as a previous version if the original publisher of that version gives permission. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document all of its principal authors, if it has fewer than five , unless they release you from this requirement.
State on the Title page the name of the publisher of the Modified Version, as the publisher. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page.
If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by or through arrangements made by any one entity.
If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
0コメント