Migrating to SUSE Linux 16: Key Technical Differences from SLE 15
- WHAT?
Key changes in the SUSE Linux 16 migration include replacing YaST with Agama, shifting from Service Packs to annual releases and adopting Wayland over X11. This version mandates 64-bit architectures while fully removing legacy support for Xen (PV),
wickedand SysV init scripts.- WHY?
Use this guide to plan your transition from SLE 15 to SUSE Linux 16 by understanding these foundational technical shifts.
- EFFORT
It takes approximately 20 minutes to read the article.
- GOAL
Assess migration impact and adapt your infrastructure to the new SUSE Linux 16 standards.
1 What is the release cycle and lifecycle for SUSE Linux 16? #
SUSE Linux 16 changes both how releases are named and how long they are supported.
1.1 New versioning scheme #
SLE 15 used Service Packs (SP1 through SP7) for annual updates. SUSE Linux 16 replaces this model with minor releases (for example, 16.0, 16.1), scheduled annually in November.
1.2 Extended support windows #
Each SLE 15 service pack carried 18 months of general support with a 6-month overlap to the next SP. SUSE Linux 16 doubles the overlap:
Each minor release has 24 months of general support with a 12-month overlap to the next release.
The final minor release, 16.6, carries 48 months of general support to complete a 10-year lifecycle (general support expected to end November 2035).
Additional Long-Term Support (LTS) and Extreme LTS options extend coverage beyond 2040.
SUSE Linux Enterprise Server for SAP applications 16 has 2 years of general support plus 3 years of extended support.
SUSE Linux 16 is ready for the post-2038 era (the Year 2038 problem does not affect it).
2 Hardware and system requirements #
SUSE Linux 16.0 introduces updated platform support requirements, including the transition to UEFI as the default boot mode and higher minimum CPU architecture levels on most platforms. Legacy BIOS remains available only for compatibility with selected migration, cloud and upgrade scenarios.
2.1 What are the BIOS and UEFI support requirements? #
UEFI is the default for fresh installations of SUSE Linux 16.0. Legacy BIOS support is deprecated and will be removed in a future release. It is retained for backward compatibility in:
migration of VMs using Legacy BIOS
certain public-cloud instances
systems upgraded from SLE 15
Note that some features—such as full disk encryption with TPM—are not available with Legacy BIOS.
2.2 Minimum CPU architecture requirements #
The minimum supported microarchitecture levels for SUSE Linux 16 have been raised for most platforms.
|
Architecture |
SUSE Linux 16 Minimum |
Notes for Version 16 |
|---|---|---|
|
AMD64/Intel 64 (x86-64) |
x86-64-v2 |
Optimized v3 shared libraries are auto-installed where supported. Package names
include |
|
IBM POWER (ppc64le) |
POWER10 |
While SUSE Linux 16 can run on POWER9, this configuration is not supported. |
|
IBM Z (s390x) |
z15 |
While SUSE Linux 16 can run on z14, this configuration is not supported. |
|
Arm (AArch64) |
ARMv8.0-A |
This requirement remains unchanged from SLE 15. |
|
Intel 32-bit |
Not supported |
32-bit system calls are available via grub2-compat-ia32 from SUSE Package Hub. |
3 How to install and deploy SUSE Linux 16 with Agama #
SUSE Linux 16 transitions from YaST to the Agama installer, introducing a purpose-built deployment model centered on modern hardware and improved automation. This chapter details these installer changes alongside updated procedures for accessing the recovery shell and registering systems against RMT infrastructure.
3.1 From YaST to Agama #
SLE 15 used YaST for both installation and ongoing system configuration, with AutoYaST for unattended deployments. SUSE Linux 16 replaces this with Agama—a purpose-built installer that is not a general management tool.
Agama is available in three extractable image flavors:
minimal—network-based installation
full—complete copy of package repositories for all product variants
remote installation—PXE client deployment
Agama provides a Web-based front-end, a command-line interface, and an HTTP API. It supports unattended installation and offers a high degree of compatibility with AutoYaST's file format and data schema. However, Agama is not a drop-in replacement for AutoYaST: some profile adjustments are expected. A new, more powerful profile schema based on JSON/Jsonnet is also available.
Unlike AutoYaST, Agama supports repeated configuration import. It is useful for iterative deployment workflows.
The installer medium now uses a standard live medium with dracut, systemd and NetworkManager, and
provides a backward-compatibility layer with selected linuxrc options.
3.2 How to access the rescue system and recovery shell #
Agama installation images no longer ship with a separate rescue system. Until a dedicated rescue image is provided in a future release, you can access a recovery shell by:
Booting the installation image, switching to another virtual console, and logging in as
rootBooting the installation image and opening a terminal window
Appending 3 to the kernel command line before booting to start in
runlevel 3, bypassing the graphical installer
3.3 Is the RMT server supported in SUSE Linux 16? #
Yes, SUSE Linux 16 instances can register against an RMT server for updates. However, the RMT service itself must currently run on a SLE 15 instance, as RMT 15 is fully supported as an installation source for SUSE Linux 16. RMT server support running directly on SUSE Linux 16 is expected to be released with SUSE Linux 16.1.
4 How to migrate from SLE 15 to SUSE Linux 16 #
Migration from SLE 15 to SUSE Linux 16 uses a new approach based on SUSE Migration Services, a bootable medium that performs migration in stages:
Pre-migration: the medium boots and analyses the existing installation. Problematic settings that cannot be converted automatically (such as AppArmor profiles) are flagged. You can choose to accept an incomplete migration or cancel.
Migration: the system boots into a special medium that performs the actual migration.
Post-migration: the migrated system boots and runs optional finalization tasks.
While SUSE Linux 16.0 featured a limited migration scope, SUSE Linux 16.1 provides full migration support, including additional source releases. This enables migrations from SLE 15 SP5 and later.
To maintain architectural integrity and predictability, live migration of a running system is no longer supported.
5 Base system and boot process changes #
Several foundational aspects of the operating system have changed in SUSE Linux 16, affecting the boot process, configuration file layout, temporary storage behavior and service management. Review this section carefully before migrating, as some changes require adjustments to existing scripts and applications.
5.1 Supported boot loaders #
SUSE Linux 16 ships GRUB 2 version 2.12. BLS and systemd-boot are
not used in 16.0 but may be added in future releases. On AMD64/Intel 64, full disk
encryption is supported using PCR to unlock the disk, provided the system has a TPM v2.1 or
later chip.
5.2 How to manage configuration files with the /usr/etc transition #
SUSE Linux 16 continues the ongoing migration of vendor-supplied default configuration
from /etc to /usr/etc. This separation allows
administrator customization in /etc to survive maintenance updates
without being overwritten.
To customize the configuration of a service, you have three options (using a hypothetical
tool frobnicator as an example):
Place a full copy of the configuration file in
/etc/frob.conf. This takes precedence over the vendor default in/usr/etc/frob.conf.Place drop-in files in
/etc/frob.d. The tool loads/usr/etc/frob.conffirst, then applies the drop-ins.Do not modify
/usr/etc/frob.confdirectly maintenance updates may overwrite it.
/etc
Tools that blindly create or overwrite files in /etc can produce
unexpected results. For example, creating an empty
/etc/ssh/sshd_config file may lock you out of SSH access. Review the
full list of affected packages at
https://en.opensuse.org/openSUSE:Packaging_UsrEtc.
5.3 How is the /tmp directory managed in SUSE Linux 16? #
In SLE 15, /tmp was a regular directory or Btrfs subvolume. In
SUSE Linux 16, /tmp uses tmpfs, which stores
data in RAM and/or swap space.
/tmp is not persistent across reboots
Any data written to /tmp is lost on reboot. Adapt applications that
write persistent data to /tmp to use a different location such as
/var/cache.
tmpfs
Setting tmpfs beyond the sum of physical RAM and swap can cause deadlock
situations. Size /tmp accordingly.
5.4 Are SysV init scripts supported in SUSE Linux 16? #
SLE 15 used systemd as the default but retained compatibility for third-party SysV
init scripts. SUSE Linux 16 completes the transition: SysV init scripts are removed.
All services must use standard systemd units.
5.5 Are transactional updates supported in SUSE Linux 16? #
Yes. While unsupported in SUSE Linux 16.0, transactional updates are introduced in SUSE Linux 16.1 via its immutable version. This transition provides atomic, rollback-capable updates that ensure system resilience and business continuity.
6 Supported file systems and storage configurations #
SUSE Linux 16.1 ships with kernel 6.12 and removes several legacy subsystems and file
systems. If your environment relies on deprecated kernel features or file systems such as
quota v1, cgroups v1 or
reiserfs, plan your migration accordingly before upgrading.
6.1 What is the default kernel version and which subsystems were removed? #
SUSE Linux 16.1 ships with kernel version 6.12. The following kernel subsystems have been removed:
quota v1cgroups v1 interface
6.2 Which file systems are supported? #
The following table provides an overview of the file system status in SUSE Linux 16:
| File system | Status in SUSE Linux 16 |
|---|---|
| btrfs | Supported—default file system |
| xfs | Supported |
| ext2/3/4 | Supported |
| gfs2 | Supported—both read and write operations. Available on SLE HA only. |
| ocfs2 | Dropped. Use gfs2 instead (available only on SLE HA). |
| reiserfs | Dropped |
| hfsplus | Dropped |
| UFS | Dropped |
| quota v1 | Dropped |
6.3 How to configure Kdump using the command line #
In SLE 15, Kdump was configured through YaST. With YaST no longer available, use
the kdumptool command-line tool. Configure Kdump via the following
variables in /etc/sysconfig/kdump:
KDUMP_CRASHKERNEL
KDUMP_UPDATE_BOOTLOADER
The kdumptool utility can check whether the running kernel has the
expected crashkernel settings, update the boot loader configuration, and disable kdump by
removing crashkernel settings from the boot loader.
7 What are the new security features and sudo policies? #
SUSE Linux 16 tightens security at every level replacing AppArmor with a fully enforced SELinux policy, restricting remote root access, and hardening privilege escalation defaults.
7.1 SELinux replaces AppArmor #
SLE 15 used AppArmor by default and shipped SELinux without policies. SUSE Linux 16 makes a definitive switch:
AppArmor is removed.
SELinux is enabled and set to enforcing mode by default, with policies covering more than 400 modules confining nearly the entire system.
Parts of the system can run unconfined if required.
On SUSE Linux Enterprise Server for SAP applications 16, SELinux provides workload isolation for data, data flows and containers. When configuring SUSE Linux or SUSE Linux Enterprise Server for SAP applications to run SAP, SELinux is automatically set to permissive mode.
For full details, see Understanding SELinux Basics.
7.2 How to manage remote root login via SSH #
Physical console login as root is unchanged. For SSH access, password-based root login is
disabled by default. To re-enable it, install the
openssh-server-config-rootlogin package. Key-based root login (via
/root/.ssh/authorized_keys) continues to work.
7.3 What are the new sudo password policies? #
In SLE 15, sudo prompted for the target user's password. SUSE Linux 16
tightens this:
The first user created during installation is added to the wheel group.
Users in the wheel group are prompted for their own password when using
sudo -i,kexecorpolkit.Users not in the wheel group are prompted for the
rootpassword.
This policy is implemented by the sudo-policy-wheel-auth-self package,
which is installed by default on new SUSE Linux 16 systems.
8 How is networking managed in SUSE Linux 16? #
SLE 15 supported both wicked and NetworkManager. SUSE Linux 16 consolidates on a single stack:
wicked is removed. NetworkManager is the only supported network management tool.
NIS (Network Information Service, also known as Yellow Pages) is removed. Use LDAP instead.
ISC DHCP server is removed. Use the more modern Kea DHCP server instead.
nscd(name service caching daemon) is removed.
9 How to manage systems and packages in SUSE Linux 16 #
SUSE Linux 16 replaces YaST with a combination of Cockpit for interactive management and Ansible or SUSE Multi-Linux Manager for automation, while also simplifying the package and update stack.
9.1 Cockpit replaces YaST for 1:1 management #
YaST is not shipped in SUSE Linux 16. For interactive 1:1 management tasks, Cockpit provides a Web-based front-end. Note that Cockpit does not fully replace YaST some modules present in YaST are not yet available in Cockpit.
9.2 Ansible and SUSE Multi-Linux Manager for automation #
SUSE Linux 16 supports Ansible for automation. SUSE Multi-Linux Manager, which uses Salt internally, is also available for managing SUSE Linux 16 installations. Note that SUSE Linux 16 itself does not include Salt packages.
WBEM support (previously provided by SBLIM packages in SLE 15) has been dropped.
9.3 How has package management and the update stack changed? #
SUSE Linux 16 removes the module concept used in SLE 15 (base system, server applications, development packages, and so on). Separate pool and update channels are also gone. These changes, combined with Zypper improvements, deliver better update performance.
Minor releases (16.1, 16.2, and so on) continue to use separate repositories.
10 Desktop environment in SUSE Linux 16 #
SLE 15 included GNOME as a full desktop with SUSE Linux Enterprise Desktop and SUSE Linux Enterprise Workstation Extension providing productivity tools. SUSE Linux 16 takes a minimal approach:
SUSE Linux Enterprise Desktop is not planned for 16.0.
A minimal GNOME desktop is included, with essential applications such as Firefox, a file browser and viewers for PDFs and images.
X11 is no longer shipped. Desktop sessions use Wayland exclusively.
The VNC server is removed. Remote desktop and screen sharing are provided via RDP.
The GTK2, Qt5 and wxWidgets widget libraries have been dropped.
Removing the full desktop product reduces the security attack surface of the base system.
11 Supported virtualization and hypervisor technologies #
KVM continues to be fully supported. Xen support has been removed:
SUSE Linux 16 cannot function as a Xen host or as a paravirtualized Xen guest (PV).
Running SUSE Linux 16 as a fully virtualized Xen guest (HVM) or using hardware virtualization features (PVH) is still possible.
Windows Subsystem for Linux: WSL1 support is removed in favor of WSL2, which provides a full Linux kernel with complete system call compatibility.
12 High Availability stack components #
The SUSE Linux Enterprise High Availability stack has been modernized:
| Component | SLE HA 15 | SLE HA 16 |
|---|---|---|
| Pacemaker | Version 2 | Version 3 |
| Corosync | Version 2 | Version 3 |
| Distributed file system | OCFS2, GFS2 (read-only) | GFS2 (full read/write support) |
| Fence agents | All agents in a single package | Agents packaged separately |
13 Which technologies were removed or replaced in SUSE Linux 16? #
The following technologies are removed in SUSE Linux 16:
| Area | Removed | Replacement |
|---|---|---|
| Architecture | 32-bit application support | grub2-compat-ia32 (SUSE Package Hub) for 32-bit kernel syscalls only |
| Architecture | Intel 32-bit and IBM POWER 32-bit libraries | No replacement—use 64-bit builds |
| Init system | SysV init scripts | systemd units |
| Installer | YaST / AutoYaST | Agama (Web, CLI, API) |
| Management | YaST (system management) | Cockpit (1:1), Ansible / SUSE Multi-Linux Manager (automation) |
| Management | WBEM / SBLIM | No direct replacement |
| Network | wicked
| NetworkManager |
| Network | NIS / Yellow Pages | LDAP |
| Network | ISC DHCP server | Kea DHCP |
| Network | nscd
| No replacement (use system resolver) |
| Security | AppArmor | SELinux with policies for 400+ modules |
| File systems | reiserfs, hfsplus,
UFS, OCFS2, quota v1
| btrfs (default), xfs,
ext, gfs2 (High Availability only) |
| Virtualization | Xen host and PV guest | KVM |
| Desktop | X11 | Wayland |
| Desktop | VNC server | RDP |
| Desktop | GTK2, Qt5, wxWidgets | GTK4, Qt6 |
| WSL | WSL1 | WSL2 |
14 For more information #
For more information on the topics covered in this article, refer to the following resources:
15 Legal Notice #
Copyright© 2006– 2026 SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”.
For SUSE trademarks, see https://www.suse.com/company/legal/. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.
All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors, nor the translators shall be held liable for possible errors or the consequences thereof.
GNU Free Documentation License
Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
0. PREAMBLE #
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
1. APPLICABILITY AND DEFINITIONS #
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
2. VERBATIM COPYING #
You may copy and distribute the Document in any medium, either commercially or non-commercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
3. COPYING IN QUANTITY #
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
4. MODIFICATIONS #
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
State on the Title page the name of the publisher of the Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
Include an unaltered copy of this License.
Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
5. COMBINING DOCUMENTS #
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".
6. COLLECTIONS OF DOCUMENTS #
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
7. AGGREGATION WITH INDEPENDENT WORKS #
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
8. TRANSLATION #
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
9. TERMINATION #
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
10. FUTURE REVISIONS OF THIS LICENSE #
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See https://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.
ADDENDUM: How to use this License for your documents #
Copyright (c) YEAR YOUR NAME. 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 in the section entitled “GNU Free Documentation License”.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this:
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.