openSUSE 13.1 Release Notes

Version: 13.1.4 (2013-10-17)

Copyright © 2013 SUSE LLC

Aveți permisiunea de a copia, distribui și/sau modifica acest document în
condițiile GNU Free Documentation License, versiunea 1.2 sau orice versiune
ulterioară publicată de Free Software Foundation; fără Secțiuni Invariante,
fără Texte pentru Coperta I (Front-Cover) și fără Texte pentru Coperta II
(Back-Cover). O copie a acestei licențe este inclusă în fișierul fdl.txt.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. Diverse
2. Instalare

    2.1. For Detailed Installation Information
    2.2. No Network after Installation
    2.3. The proprietary NVIDIA driver requires users to have access to /
        dev/nvidia* devices

3. General

    3.1. Documentația openSUSE
    3.2. Dropped YaST Modules
    3.3. UEFI—Unified Extensible Firmware Interface
    3.4. Enable Secure Boot in YaST Not Enabled by Default When in Secure
        Boot Mode
    3.5. Wrong Bootloader When Installing from a Live Medium in a UEFI
        Environment
    3.6. Crypted LVM in UEFI Mode Needs /boot Partition

4. Actualizare sistem

    4.1. systemd: Activating NetworkManager with a network.service Alias
        Link
    4.2. SYSLOG_DAEMON Variable Removed

5. Detalii tehnice

    5.1. Inițializarea graficii cu KMS (Kernel Mode Setting)
    5.2. Configuring Postfix
    5.3. GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for
        Input Source Selection
    5.4. xinetd: Logging to the System Log
    5.5. Apache Version 2.4
    5.6. tomcat: Logging to the System Log
    5.7. Darktable: Refreshing Cache Files Needed

Dacă actualizați o versiune mai veche la această versiune openSUSE,
consultați aici notele de lansare anterioare: http://en.opensuse.org/
openSUSE:Release_Notes

Aceste informații despre produs acoperă următoarele aspecte:

  • Secțiune 1, „Diverse”: These entries are automatically included from
    openFATE, the Feature- and Requirements Management System (http://
    features.opensuse.org).

    Indisponibil

  • Secțiune 2, „Instalare”: Citiți acestea dacă doriți să instalați
    sistemul din bucăți.

  • Secțiune 3, „General”: Informație pe care fiecare ar trebui să o
    citească.

  • Secțiune 4, „Actualizare sistem”: Issues related to the process if you
    run a system upgrade from the previous release to this openSUSE
    version.

  • Secțiune 5, „Detalii tehnice”: Această secțiune conține un număr de
    schimbări tehnice și și îmbunătățiri pentru utilizatorul experimentat.

1. Diverse

Indisponibil

2. Instalare

2.1. For Detailed Installation Information

For detailed installation information, see Secțiune 3.1, „Documentația
openSUSE”.

2.2. No Network after Installation

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.

2.3. The proprietary NVIDIA driver requires users to have access to /dev/
nvidia* devices

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

3. General

3.1. Documentația openSUSE

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

3.2. Dropped YaST Modules

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.

3.3. UEFI—Unified Extensible Firmware Interface

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.

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

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.

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

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.

3.6. Crypted LVM in UEFI Mode Needs /boot Partition

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.

4. Actualizare sistem

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

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.

4.2. SYSLOG_DAEMON Variable Removed

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.

5. Detalii tehnice

5.1. Inițializarea graficii cu KMS (Kernel Mode Setting)

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.

5.2. Configuring Postfix

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.

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

CHECKIT:12.3

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.

5.4. xinetd: Logging to the System Log

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.

5.5. Apache Version 2.4

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.

5.6. tomcat: Logging to the System Log

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.

5.7. Darktable: Refreshing Cache Files Needed

If upgrading from a previous release to openSUSE 13.1 old cache files may
no longer work. In this case removing ~/.cache/darktable/mipmaps is
necessary.

