|||
Download:
https://www.suse.com/products/desktop/download/
SUSE Linux Enterprise Desktop is the market's onlyenterprise-quality Linux desktop ready for routine business use.Developed and backed by SUSE, SUSE Linux Enterprise Desktop provides market-leadingusability, seamless interoperability with existing IT systems, anddozens of essential applications—all at a fraction of the price ofproprietary operating systems. It comes bundled with the latestversions of leading applications such as LibreOffice officeproductivity suite, Mozilla Firefox web browser, and Evolutionemail and calendar suite. In addition, it integrates with MicrosoftSharePoint and Novell Teaming for group collaboration and supports awide range of multimedia file formats, wireless and networkingstandards, and plug-and-play devices.
Through the latest enhancements in power management and security, SUSE Linux Enterprise Desktopalso provides an environmentally friendly IT experience (Green IT) andan error-proof desktop. Finally, SUSE Linux Enterprise Desktop offers unparalleled flexibility. Youcan deploy it on a wide range of thick client devices (includingdesktops, notebooks, netbooks, and workstations), on thin clientdevices, or as a virtual desktop. By leveraging the power of SUSE Linux Enterprise Desktop,your business can dramatically reduce costs, improve end-usersecurity and increase workforce productivity.
GNOME 2.28
GNOME was updated to version 2.28 with SP1, only selected packages got an update for SP2 or SP3.
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.
SaX2 offers to change the resolution even for the fbdev driver.Because this is controlled via a VGA kernel option, rebooting isneeded after resolution changes. In other words: Modificationswill take effect the next time the graphics system is restarted;in some cases a reboot of the machine is needed.
Since SUSE Linux Enterprise Desktop 11 SP1, 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 update repository integrity used by SUSE is ensured by a GPG signature and the checksums of the YUM repomd XML metadata.
SUSE Linux Enterprise 11 so far used sha1 as intermediate checksum, which should no longer be used.
With SUSE Linux Enterprise 12 and SUSE Linux Enterprise 11 SP4 we start to use sha256 for the XML integrity handling and so get rid of the old sha1 hashing methods.
If you have tools parsing the XML metadata yourself, please verify they can handle also the newer sha256 hashes.
The common PAM configuration files (/etc/pam.d/common-*) are now created and managed with pam-config.
numactl and libnuma have been updated to the latest version.
This update comes with many bug fixes and some new features that are especially important for large NUMA systems, e.g.:
IO affinity support
New option to memhog to disable transparent huge pages
Show distances on machines without a node 0
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.
GCC 4.3.4
glibc 2.11
Linux kernel 3.0
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
In addition to the /etc/SuSE-release file the file /etc/os-release is now available.
/etc/os-release is a cross-distribution standard to identify a Linux system. For more information about the syntax, see the os-release man page ( man os-release ).
When upgrading from SUSE Linux Enterprise Server or Desktop 11 SP3 to version 11 SP4, you may encounter a version downgrade of specific software packages, including the Linux Kernel.
SLE 11 SP4 has all its software packages and updates in the SLE 11 SP4 repositories. No packages from SLE 11 SP3 repositories are needed for installation or upgrade, not even from the SLE 11 SP3 update repositories.
Note
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 SLE 11 SP3 update repositories, be aware of one characteristic of the repository concept: Version numbers in the SP3 update repository can be higher than those in the SP4 repository. Thus, if you update with the SP3 repositories enabled, you may get the SP3 version of a package instead of the SP4 version. This is admittedly unfortunate.
It is recommended to avoid using the version from a lower product or SP, because using the SLE 11 SP3 package instead of the SP4 package can result in unexpected side effects. Thus we advise to switch off all the SLE 11 SP3 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 product or SP though, and thus have SLE 11 SP3 repositories enabled, make sure that the packages you intended to upgrade have actually been upgraded.
Summarizing: If you have an SLE 11 SP3 installation with all patches and updates applied, and then migrate off-line to SLE 11 SP4, you will see a downgrade of some packages. This is expected behavior.
To migrate the system to the Service Pack 4 level with zypper, proceed as follows:
Open a root shell.
To refresh all services and repositories, run:
To install package management updates, run:
Now it is possible to install all available updates for SLES/SLED 11 SP3; run 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:
A sample output could be as follows:
Install these migration products (example):
Run suse_register -d 2 -L /root/.suse_register.log toregister the products in order to get the corresponding SP4 Updaterepositories.
To avoid a dependency conflict enable the SLED11-Extras repository with:
On SLES this extra step is not needed.
Run zypper ref -s to refresh services and repositores.
Check the repositories using zypper lr. Disable SP1, SP2, and SP3 repositories after the registration and enable the new SP4 repositories (such as SP4-Pool, SP4-Updates):
Also disable repositories you do not want to update from.
Then perform a distribution upgrade by entering the following command:
Add more SP4 repositories here if needed, e.g. in case add-on products are installed. For WebYaST, it is actually SLE11-SP2-*, because there is one WebYaST release that runs on two SP code bases.
If you make sure that only repositories, which you migrate from, are enabled, you can omit the --from parameters.
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:
Run zypper patch after re-registering. Some products do not use the update repositories during the migration and they are not active at this point of time.
Reboot the system.
Archiver|手机版|科学网 ( 京ICP备07017567号-12 )
GMT+8, 2024-9-1 07:29
Powered by ScienceNet.cn
Copyright © 2007- 中国科学报社