openSUSE 12.3 Versionshinweise

Version: 12.3.6 (2013-03-13)

Copyright © 2013 Novell, Inc.

Sie können dieses Dokument unter den Bedingungen der GNU-Free-Documentation-Lizenz (Version 1.2 oder jede später durch die Free-Software-Foundation veröffentlichte Version) kopieren, verteilen und/oder bearbeiten; mit keinen invarianten Abschnitten, Deckblatt- und Rückseitentexten. Eine Kopie der Lizenz ist als Datei fdl.txt enthalten.


1. Verschiedenes
2. Installation
2.1. Für detaillierte Installationshinweise
2.2. No Network after Installation
3. Allgemeines
3.1. openSUSE-Dokumentation
3.2. UEFI—Unified Extensible Firmware Interface
3.3. Enable Secure Boot in YaST Not Enabled by Default When in Secure Boot Mode
3.4. Wrong Bootloader When Installing from a Live Medium in a UEFI Environment
3.5. openSUSE 12.3 Medium May Not Boot on Future Secure Boot Enabled Hardware
3.6. Crypted LVM in UEFI Mode Needs /boot Partition
4. System Aktualisierung
4.1. systemd: Activating NetworkManager with a network.service Alias Link
4.2. SYSLOG_DAEMON-Variable entfernt
5. Technisch
5.1. Initialisierung der Grafik mit KMS (Kernel Mode Setting)
5.2. systemd: Verzeichnisse aufräumen (/tmp und /var/tmp)
5.3. Postfix einrichten
5.4. GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for Input Source Selection

Wenn Sie von einer älteren Version auf diese openSUSE-Veröffentlichung aktualisieren, schauen Sie bitte in die hier http://de.opensuse.org/openSUSE:Release_Notes aufgeführten Versionshinweise.

Diese Versionshinweise decken die folgenden Bereiche ab:

1. Verschiedenes

N/A

2. Installation

2.1. Für detaillierte Installationshinweise

Detaillierte Informationen finden Sie unter Abschnitt 3.1, „openSUSE-Dokumentation“.

2.2. No Network after Installation

Directly after installation, NetworkManager is not started automatically and thus WiFi cannot be configured. To enable networking (WiFi), reboot the machine once manually.

3. Allgemeines

3.1. openSUSE-Dokumentation

  • In Start-Up finden Sie Schritt-für-Schritt-Anleitungen, sowie Einführungen in die KDE- und Gnome-Desktops und die LibreOffice-Suite. Ebenfalls enthalten sind grundlegende Administrationsthemen, wie Einsatz- und Software-Management und eine Einführung in die bash-Shell.

  • Das Referenz-Handbuch behandelt Einsatz, Verwaltung und Systemkonfiguration ausführlich und erklärt, wie die verschiedenen Netzwerkdienste eingerichtet werden.

  • Das Sicherheits-Handbuch stellt grundlegende Konzepte der Systemsicherheit vor und behandelt sowohl lokale als auch Netzwerk-Sicherheitsaspekte.

  • Der System-Analyse- und Tuning-Guide hilft bei der Problemerkennung, -lösung und -optimierung

  • Virtualisierung mit KVM bietet eine Einführung in die Einrichtung und Verwaltung von Virtualisierungstechniken mit KVM, libvirt und QEMU-Tools.

Find the documentation in /usr/share/doc/manual/opensuse-manuals_$LANG after installing the package opensuse-manuals_$LANG, or online on http://doc.opensuse.org.

3.2. UEFI—Unified Extensible Firmware Interface

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.

3.3. Enable Secure Boot in YaST Not Enabled by Default When in Secure Boot Mode

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.

3.4. Wrong Bootloader When Installing from a Live Medium in a UEFI Environment

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.

3.5. openSUSE 12.3 Medium May Not Boot on Future Secure Boot Enabled Hardware

This only affects machines in UEFI mode.

Our double signed shim on openSUSE 12.3 medium may be rejected by future firmwares.

If the openSUSE 12.3 medium does not boot on future secure boot enabled hardware, temporarily disable secure boot, install openSUSE and apply all online updates to get an updated shim.

After installing all updates secure boot can be turned on again.

3.6. Crypted LVM in UEFI Mode Needs /boot Partition

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.

4. System Aktualisierung

4.1. systemd: Activating NetworkManager with a network.service Alias Link

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.

Um den NetworkManager zu aktivieren, benutzen Sie:

  • First, stop the running service:

    systemctl     is-active network.service && \
     systemctl     stop      network.service
  • Den NetworkManager-Dienst aktivieren:

    systemctl --force        enable NetworkManager.service
  • Start the NetworkManager service (via alias link):

    systemctl     start     network.service

Um den NetworkManager zu deaktivieren, benutzen Sie:

  • Den Laufenden Dienst anhalten:

    systemctl     is-active network.service && \
    systemctl     stop      network.service
  • Den NetworkManager-Dienst deaktivieren:

    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.

4.2. SYSLOG_DAEMON-Variable entfernt

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.

5. Technisch

5.1. Initialisierung der Grafik mit KMS (Kernel Mode Setting)

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 den seltenen Fällen kann das Laden des DRM-Modul von initrd ein generelles Problem darstellen. Dazu kann dann die Variable NO_KMS_IN_INITRD via YaST → System → 'Editor für /etc/sysconfig' im Menü/Reiter: 'Kernel' dauerhaft von Standardwert: no auf yes abgeändert werden. Beim Beenden wird initrd neu eingelesen und die geänderte Einstellung beim System-Neustart aktiv.

Auf Intel Hardware ohne KMS (Kernel-Kode-Setting), fällt X.org auf den fbdev Treiber (die Intel-Treiber unterstützt nur KMS) zurück. Alternativ dazu steht für ältere GPUs von Intel, der "intellegacy" Treiber (xorg-x11-driver-video-intel-legacy Paket) zur Verfügung. Um diesen benutzen zu können, muss /etc/X11/xorg.conf.d/50-device.conf editiert werden. Dazu den Eintrag des Treibers nun auf: intellegacy abändern.

Auf ATI Hardware für aktuelle GPUs fällt das System wieder auf radeonhd zurück um mit NVIDIA Hardware ohne KMS den nvTreiber zu verwenden (der Nouveau-Treiber unterstfbdev Treiber nur verwenden, wenn nomodeset als Kernel-Boot-Paramente gesetzt wird.

5.2. systemd: Verzeichnisse aufräumen (/tmp und /var/tmp)

By default, systemd cleans tmp directories daily as configured in /usr/lib/tmpfiles.d/tmp.conf. Users can change it by copying /usr/lib/tmpfiles.d/tmp.conf to /etc/tmpfiles.d/tmp.conf and modifying the copied file. It will override /usr/lib/tmpfiles.d/tmp.conf.

Hinweis: systemd schenkt den veralteten (obsolete) sysconfig Variablen in /etc/sysconfig/cron keine Beachtung. Dies Betrifft z.B. TMP_DIRS_TO_CLEAR.

5.3. Postfix einrichten

The 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.

5.4. GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for Input Source Selection

In Gnome 3.6 use the following workaround to set Shift or Ctrl+Shift as shortcut keys for input source selection:

  1. Install gnome-tweak-tool.

  2. Start gnome-tweak-tool ('Activities'>'advanced settings').

  3. Via the left menu, select 'Typing', 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.