Version: 13.1.4 (2013-10-17)
Copyright © 2013 SUSE LLC
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included as the fdl.txt file.
If you upgrade from an older version to this openSUSE release, see previous release notes listed here: http://en.opensuse.org/openSUSE:Release_Notes
These release notes cover the following areas:
Section 1, “Miscellaneous”: These entries are automatically included from openFATE, the Feature- and Requirements Management System (http://features.opensuse.org).
N/A
Section 2, “Installation”: Read this if you want to install the system from scratch.
Section 3, “General”: Information that everybody should read.
Section 4, “System Upgrade”: Issues related to the process if you run a system upgrade from the previous release to this openSUSE version.
Section 5, “Technical”: This section contains a number of technical changes and enhancements for the experienced user.
For detailed installation information, see Section 3.1, “openSUSE Documentation”.
CHECKIT:12.3
Directly after installation, NetworkManager is not started automatically and thus WiFi cannot be configured. To enable networking (WiFi), reboot the machine once manually.
CHECKIT:12.3
Default and new users are no longer added to the video group automatically. But the proprietary NVIDIA driver requires users to have access to /dev/nvidia* devices.
Because the NVIDIA driver does not use the usual kernel methods that allow to install ACLs on the device nodes, users have to be added manually to the video group; as root call (replace $USER with the actual username):
usermod -a -G video $USER
In Start-Up, find step-by-step installation instructions, as well as introductions to the KDE and Gnome desktops and to the LibreOffice suite. Also covered are basic administration topics such as deployment and software management and an introduction to the bash shell.
Find the documentation in /usr/share/doc/manual/opensuse-manuals_$LANG after installing the package opensuse-startup_$LANG, or online on http://doc.opensuse.org.
The following YaST modules were obsolete and rarely used these days:
yast2-autofs
yast2-dbus-client
yast2-dirinstall
yast2-fingerprint-reader
yast2-irda
yast2-mouse
yast2-phone-services
yast2-power-management
yast2-profile-manager
yast2-sshd
yast2-tv
The main reason for dropping was to decrease the maintenance effort and better focus on other more used modules.
CHECKIT:12.3
Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface) you are urgently advised to check for any firmware updates the hardware vendor recommends and, if available, to install such an update. A pre-installed Windows 8 is a strong indication that your system boots using UEFI.
Background: Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. Nobody really knows how much "too much" is, though. openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux Kernel features that use the UEFI storage area for storing boot and crash information (pstore) have been disabled by default. Nevertheless it is recommended to install any firmware updates the hardware vendor recommends.
CHECKIT:12.3
This only affects machines in UEFI mode with secure boot enabled.
YaST does not automatically detect if the machine has secure boot enabled and will therefore install an unsigned bootloader by default. But the unsigned bootloader will not be accepted by the firmware. To have a signed bootloader installed the option "Enable Secure Boot" has to be manually enabled.
CHECKIT:12.3
This only affects machines in UEFI mode.
When using the installer on the live medium, YaST does not detect UEFI mode and therefore installs the legacy bootloader. This results in a not bootable system. The bootloader has to be switched from grub2 to grub2-efi manually.
CHECKIT:12.3
This only affects installations in UEFI mode.
In the partitioning proposal when checking the option to use LVM (which is required for full disk encryption) YaST does not create a separate /boot partition. That means kernel and initrd end up in the (potentially encrypted) LVM container, inaccessible to the boot loader. To get full disk encryption when using UEFI, partitioning has to be done manually.
CHECKIT:12.3
By default, you use the YaST Network Settings dialog (yast2 network) to activate NetworkManager. If you want to activate NetworkManager, proceed as follows.
The NETWORKMANAGER sysconfig variable in /etc/sysconfig/network/config to activate NetworkManager has been replaced with a systemd network.service alias link, which will be created with the
systemctl enable NetworkManager.service
command. It causes the creation of a network.service alias link pointing to the NetworkManager.service, and thus deactivates the /etc/init.d/network script. The command
systemctl -p Id show network.service
allows to query the currently selected network service.
To enable NetworkManager, use:
First, stop the running service:
systemctl is-active network.service && \ systemctl stop network.service
Enable the NetworkManager service:
systemctl --force enable NetworkManager.service
Start the NetworkManager service (via alias link):
systemctl start network.service
To disable NetworkManager, use:
Stop the running service:
systemctl is-active network.service && \ systemctl stop network.service
Disable the NetworkManager service:
systemctl disable NetworkManager.service
Start the /etc/init.d/network service:
systemctl start network.service
To query the currently selected service, use:
systemctl -p Id show network.service
It returns "Id=NetworkManager.service" if the NetworkManager service is enabled, otherwise "Id=network.service" and /etc/init.d/network is acting as the network service.
CHECKIT:12.3
The SYSLOG_DAEMON variable has been removed. Previously, it was used to select the syslog daemon. Starting with openSUSE 12.3, only one syslog implementation can be installed at a time on a system and will be selected automatically for usage.
For details, see the syslog(8) manpage.
CHECKIT:12.3
With openSUSE 11.3 we switched to KMS (Kernel Mode Setting) for Intel, ATI and NVIDIA graphics, which now is our default. If you encounter problems with the KMS driver support (intel, radeon, nouveau), disable KMS by adding nomodeset to the kernel boot command line. To set this permanently using Grub 2, the default boot loader, add it to the GRUB_CMDLINE_LINUX_DEFAULT kernel default load options line in your /etc/default/grub text file as root and running the terminal command
sudo /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg
for the changes to take effect. Else, for Grub Legacy, add it to the kernel command line in /boot/grub/menu.lst, also done as root. This option makes sure the appropriate kernel module (intel, radeon, nouveau) is loaded with modeset=0 in initrd, i.e. KMS is disabled.
In the rare cases when loading the DRM module from initrd is a general problem and unrelated to KMS, it is even possible to disable loading of the DRM module in initrd completely. For this set the NO_KMS_IN_INITRD sysconfig variable to yes via YaST, which then recreates initrd afterwards. Reboot your machine.
On Intel without KMS the Xserver falls back to the fbdev driver (the intel driver only supports KMS); alternatively, for legacy GPUs from Intel the "intellegacy" driver (xorg-x11-driver-video-intel-legacy package) is available, which still supports UMS (User Mode Setting). To use it, edit /etc/X11/xorg.conf.d/50-device.conf and change the driver entry to intellegacy.
On ATI for current GPUs it falls back to radeonhd. On NVIDIA without KMS the nv driver is used (the nouveau driver supports only KMS). Note, newer ATI and NVIDIA GPUs are falling back to fbdev, if you specify the nomodeset kernel boot parameter.
CHECKIT:12.3
With openSUSE 12.3, SuSEconfig.postfix was renamed as /usr/sbin/config.postfix. If you set sysconfig variables in /etc/sysconfig/postfix or /etc/sysconfig/mail, you must manually run /usr/sbin/config.postfix as root.
CHECKIT:12.3
In Gnome 3.6 use the following workaround to set Shift or Ctrl+Shift as shortcut keys for input source selection:
Install gnome-tweak-tool.
Start gnome-tweak-tool (>).
Via the left menu, select , in the right window, change the settings.
This is also being tracked in the upstream bug report https://bugzilla.gnome.org/show_bug.cgi?id=689839.
The new default for xinetd changes the default target for logging from /var/log/xinetd.log to the system log. This means all messages from xinetd will appear in a system log as a facility daemon and log level info.
If you want to switch back the the old way, find a proper snippet in /etc/xinetd.conf. The template for the logrotate script for xinetd.log can be found in /usr/share/doc/packages/xinetd/logrotate.
Apache 2.4 features various changes in the configuration files. For more information about upgrading from a previous version, see http://httpd.apache.org/docs/2.4/upgrading.html.
The tomcat startup scripts doe no longer write the output to /var/log/tomcat/catalina.out. All messages are now redirected to the system log via tomcat.service (tomcat-jsvc.service) and log level info.