OpenSUSE Leap 16.1 Release Notes: Difference between revisions

Removed heading numbers
Added colours to blockquotes
Line 36: Line 36:
== openSUSE Leap Immutable replaces Leap Micro ==
== openSUSE Leap Immutable replaces Leap Micro ==


<blockquote>'''Important:''' openSUSE Leap 16.1 installed in immutable mode is the direct successor of Leap Micro 6.2. There will be no Leap Micro 6.3.</blockquote>
<blockquote style="border-left-color: #0000ff">'''Important:''' openSUSE Leap 16.1 installed in immutable mode is the direct successor of Leap Micro 6.2. There will be no Leap Micro 6.3.</blockquote>


openSUSE Leap Immutable is a transactionally updated variant of openSUSE Leap with a read-only root file system. You can configure it on first boot using either Ignition or Combustion.
openSUSE Leap Immutable is a transactionally updated variant of openSUSE Leap with a read-only root file system. You can configure it on first boot using either Ignition or Combustion.
Line 119: Line 119:
=== AppArmor not available by default on new installations ===
=== AppArmor not available by default on new installations ===


<blockquote>'''Warning:''' AppArmor is no longer available in SUSE Linux Enterprise 16.0. Leap users cannot select AppArmor as the Linux Security Module (LSM) during a new installation. AppArmor can still be enabled post-installation. For instructions, refer to [https://en.opensuse.org/SDB:AppArmor#Switching_from_SELinux_to_AppArmor_for_Leap_16.0_and_Tumbleweed AppArmor wiki page].</blockquote>
<blockquote style="border-left-colour: #ff0000">'''Warning:''' AppArmor is no longer available in SUSE Linux Enterprise 16.0. Leap users cannot select AppArmor as the Linux Security Module (LSM) during a new installation. AppArmor can still be enabled post-installation. For instructions, refer to [https://en.opensuse.org/SDB:AppArmor#Switching_from_SELinux_to_AppArmor_for_Leap_16.0_and_Tumbleweed AppArmor wiki page].</blockquote>


Users migrating manually from 15.6 will retain AppArmor by default. Users migrating with [https://github.com/openSUSE/opensuse-migration-tool openSUSE migration tool] will be prompted to either switch to SELinux or preserve AppArmor during post-migration.
Users migrating manually from 15.6 will retain AppArmor by default. Users migrating with [https://github.com/openSUSE/opensuse-migration-tool openSUSE migration tool] will be prompted to either switch to SELinux or preserve AppArmor during post-migration.
Line 125: Line 125:
== Steam ==
== Steam ==


<blockquote>'''Warning:''' The <code>Steam</code> package has been removed from the [https://en.opensuse.org/Package_repositories#Non-OSS Non-OSS repository] due to limited 32-bit library support. Users are advised to install it via [https://en.opensuse.org/Steam#Flatpak Flatpak].</blockquote>
<blockquote style="border-left-colour: #ff0000">'''Warning:''' The <code>Steam</code> package has been removed from the [https://en.opensuse.org/Package_repositories#Non-OSS Non-OSS repository] due to limited 32-bit library support. Users are advised to install it via [https://en.opensuse.org/Steam#Flatpak Flatpak].</blockquote>


* 32-bit execution requires installing <code>grub2-compat-ia32</code> and rebooting.
* 32-bit execution requires installing <code>grub2-compat-ia32</code> and rebooting.
Line 146: Line 146:
=== Broken libvirt networking when using Docker ===
=== Broken libvirt networking when using Docker ===


<blockquote>'''Warning:''' If networking inside libvirt-managed virtual machines fails while Docker is running, it is likely due to Docker not supporting <code>nftables</code>.</blockquote>
<blockquote style="border-left-colour: #ff0000">'''Warning:''' If networking inside libvirt-managed virtual machines fails while Docker is running, it is likely due to Docker not supporting <code>nftables</code>.</blockquote>


To fix the issue:
To fix the issue: