Notas da versão #

In order to avoid some big recommended packages from being installed, the pattern for minimal installations uses another pattern that creates conflicts with undesired packages. This pattern, patterns-openSUSE-minimal_base-conflicts, can be removed after installation.

Atente que uma instalação minimal não possui Firewall por defeito. Se necessita de uma Firewall, proceda à instalação de SuSEfirewall2.

Antes de proceder à instalação do openSUSE num sistema que utiliza a UEFI para o arranque, é desde mais aconselhado a verificar se existem atualização de Firmware por parte do fabricante e instalar essas mesmas atualizações. Se já possuía o Windows 8 ou superior pré-instalado, é um forte indicador que o seu sistema utiliza a UEFI para o arranque.

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.

Em conjunto com a especificação EFI/UEFI, um novo estilo de particionamento chega: GPT (Tabela de Partição Guid). Este novo esquema usa identificadores globais únicos (valores de 128bits exibidos em 32 dígitos hexadecimais) para identificar dispositivos e tipos de partições.

Additionally, the UEFI specification also allows legacy MBR (MS-DOS) partitions. The Linux boot loaders (ELILO or GRUB2) try to automatically generate a GUID for those legacy partitions, and write them to the firmware. Such a GUID can change frequently, causing a rewrite in the firmware. A rewrite consist of two different operation: removing the old entry and creating a new entry that replaces the first one.

Modern firmware has a garbage collector that collects deleted entries and frees the memory reserved for old entries. A problem arises when faulty firmware does not collect and free those entries; this may end up with a non-bootable system.

The workaround is simple: convert the legacy MBR partition to the new GPT to avoid this problem completely.

Quando atualiza uma máquina remota a partir do openSUSE 13.2, certifique-se de que as interfaces de rede apresentam o nome correto.

O openSUSE 13.2 utilizou os chamados nomes de interface de rede previsíveis (por exemplo: enp5s0), enquanto que o openSUSE Leap 42.1 utiliza nomes de interface persistentes (eth0). Após a atualizar e reiniciar, os nomes da interface de rede podem ser alterados. Isto poderá bloquear o seu acesso ao sistema. Para evitar que as interfaces sejam renomeadas, execute o seguinte comando para cada uma das interfaces de rede antes de reiniciar o sistema:

/usr/lib/udev/udev-generate-persistent-rule -v -c enp5s0 -n enp5s0 -o /etc/udev/rules.d/70-persistent-net.rules

Substitua enp5s0 pelo nome da sua interface de rede.

By default, openSUSE 13.2 used a Btrfs partition layout that allowed for disk space to become permanently occupied with stale, inaccessible contents after the first system rollback was executed. This layout issue was fixed in openSUSE Leap 42.1. However, the fix can only be applied to newly installed systems.

If you are upgrading from openSUSE 13.2, you cannot convert the file system to the new layout, but you can reclaim the lost disk space.

AtençãoData Loss with Non-Standard Settings or No Rollbacks

The following procedure will only work properly on installations set up using the default proposal created by the openSUSE 13.2 installer.

Additionally, you must have previously made a system rollback.

If you have set up your Btrfs file system with a non-standard configuration or have not previously made a system rollback, executing the following procedure can incur data loss.

After the installation, the non-oss repository is disabled.

Enable the openSUSE-Leap-42.1-Non-Oss repository using YaST or on the command line using zypper:

zypper mr -e repo-non-oss

CUPS Atualizado para a versão 1.7

The new CUPS version introduced some major changes compared to 1.5 that may require manual configuration adjustments.

When using the KDE display manager SDDM with an authentication method that provides a high number of users, SDDM becomes unusable. Additionally, if the automounter is used, SDDM may block for a long time on startup trying to mount every user's home.

Modify /etc/sddm.conf to contain the following entries:

[Theme]
Current=maldives

[Users]
MaximumUid=1002

See https://bugzilla.suse.com/show_bug.cgi?id=953778 (https://bugzilla.suse.com/show_bug.cgi?id=953778) for details.

KDE Plasma does not support screensavers by default. If you prefer to have a screensaver, install the package xscreensaver.

Set xscreensaver to start with the desktop session by selecting K › Settings › Configure Desktop, then choose Startup and Shutdown › Autostart. Click Add Program, type xscreensaver and click OK.

To configure the screensaver, use xscreensaver-demo.