Copyright © 2009 Novell, Inc.
在符合 GNU 自由文档许可证协议 (由自由软件基金会版本 1.2 及之后版本) 的条件下，您有权对此文档进行复制、传播和修改；不包含不变章节、封面文本、底面文本。一份许可证拷贝在文件 fdl.txt。
The release notes are under constant development. Download the newest version as part of the Internet test or refer to http://www.suse.com/relnotes/i386/openSUSE/11.1/RELEASE-NOTES.en.html. We update the English release notes whenever need arises. This means that translations might temporarily be incomplete. The translations are updated to match later.
这些发行说明包括以下领域：
常规：任何人都应当阅读的信息。
更新：《参考手册》第 5 章中没有提到的更改。
技术：此部分包含一系列针有经验用户的技术更改和增强内容。
In the Start-Up Manual, find information about installation and basic system configuration. In the Reference Guide, the system configuration is explained in detail. Find basic information on GNOME and KDE in the QuickStart Guides. Detailed information on using AppArmor is provided by the AppArmor Administration Guide.
During the installation YaST resp. SaX2 are trying to detect displays and determine the display size and resolution. If you are installing on a notebook with the lid closed it is not be possible to detect the display. To avoid this problem it is highly recommended to keep the lid open during the installation.
If the detection failed, start YaST and click "Hardware" -> "Graphics Card and Monitor". Then configure the display manually.
Lenovo ThinkPad laptops have special code in the MBR (master boot record) because of the "Blue ThinkVantage button" functionality. If detecting and preparing it properly 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 proposal 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/.
Updating from openSUSE 11.0 to openSUSE 11.1 with the Xen Hypervisor may have an incorrect network configuration, because the update does not configure the bridged setup automatically.
Start the "YaST Control Center", choose "Virtualization" and then "Install Hypervisor and Tools" to start the bridge proposal for networking. Alternatively you can call "yast2 xen" on the commandline.
Note, if you install openSUSE 11.1 and configure Xen, you get a bridged setup through YaST automatically.
The man command now asks which man-page the user wants to see if man-pages with the same name exist in different sections. The user is expected to type the section number to make this man-page visible.
If you want to get back the previous behavior, set MAN_POSIXLY_CORRECT=1 in a shell initialization file such as ~/.bashrc.
The YaST LDAP Server module does not store the LDAP Server configuration in /etc/openldap/slapd.conf any longer. The module now uses OpenLDAP's dynamic configuration backend, which stores the configuration in an LDAP database itself. That database consists of a set of .ldif files in /etc/openldap/slapd.d. To access the configuration either use the yast2-ldap-server module or an LDAP client such as ldapmodify or ldapsearch.
For details on the dymanic configuration of OpenLDAP, see the OpenLDAP Administration Guide.
By default, Network Manager is enabled and manages network connections. If you want configure it, you must use a Network Manager applet to change the settings. As long as Network Manager is running, YaST refuses to configure the network settings, because YaST and Network Manager have different sets of configuration options.
The modify_resolvconf script is removed in favor of the more versatile netconfig script. The new script handles specific network settings from multiple sources more flexible and transparent. For more informations, see the updated manuals and the netconfig man-page.
In the shipped manuals, modify_resolvconf is erroneously referenced. We will correct it in the next release.
By default, the WLAN channels 12, 13, and 14 are disabled because it is not allowed to use these channels everywhere. If you want to use them in your region, see http://en.opensuse.org/Tracking_down_wireless_problems for more information.
On the command line, if you enter a command that could not be found, bash and zsh call the /usr/bin/command-not-found handler. command-not-found then searches a package database and proposes how to proceed.
If you want to disable this behavior, either remove the command-not-found package or unset command_not_found_handle in your shell initialization file. For example, add to ~/.bashrc:
unset command_not_found_handle