跳到内容跳到页面导航:上一页 [access key p]/下一页 [access key n]
documentation.suse.com / SUSE Linux Enterprise Server 文档 / 快速入门指南 / 模块和扩展快速入门
SUSE Linux Enterprise Server 15 SP3

模块和扩展快速入门

SUSE Linux Enterprise Server 15SP3

出版日期: 2024 年 9 月 29 日

本快速入门提供了 SUSE Linux Enterprise 系列可用模块和扩展的概述。您可以了解它们的用途和功能,以及如何管理它们。

1 模块和扩展简介

SUSE Linux Enterprise Server 15 开始,安装媒体仅包含统一安装程序:一个用于部署、更新和注册 SUSE Linux Enterprise 的精简系统。在部署期间,您可以通过选择要在统一安装程序的基础上安装的模块和扩展来添加功能。

从技术上讲,模块和扩展非常类似。它们都可以使用 YaST 或命令行工具 SUSEConnect 进行管理。模块和扩展都会添加一组包含所有必要软件包的联机储存库(mainupdatesourcedebug)。此外,它们都可添加可以在部署期间选择的分区建议和系统角色。

不过,模块和扩展之间也存在一些重大差异:

模块

模块可让您根据需要定制产品功能。每个模块都有明确定义的范围,从用于进行 Web 开发和编写脚本的工具到公共云、再到 SUSE Package Hub(提供由社区管理的软件包)。

利用模块,您可以仅提供满足计算机用途所需的一组软件包,从而精简系统、加快其运行速度,并提高其安全性。这种模块化方法还可让您轻松提供专为容器和云环境定制的映像。

您可以在系统的整个生命周期内随时添加或去除模块。这样您便可轻松调整系统以满足不断变化的要求。

模块属于您的 SUSE Linux Enterprise Server 订阅的一部分,因此可免费使用。模块与 SUSE Linux Enterprise Server 基础系统的唯一不同就是生命周期。SUSE 为模块所提供的几乎所有软件包都提供 L3 支持(SUSE Package Hub 模块除外)。有关 SUSE Linux Enterprise Server 支持声明的详细信息,请参见发行说明

扩展

扩展为 SUSE Linux Enterprise Server 的在线增补和高可用性群集组建等任务提供高级功能。它们以订阅的形式提供,需要注册密钥,因此需付费才能使用。https://www.suse.com/releasenotes 上通常会提供各扩展的发行说明。

2 SUSE Linux Enterprise 产品系列的模块

SUSE Linux Enterprise 产品系列中提供下列模块。请注意,模块的可用性取决于产品(请参考可用性这列)。有关生命周期、发布频率和覆盖支持期的详细信息,请参见 https://www.suse.com/lifecycle

注意
注意:L3 支持

对于模块中的软件包,一般提供 L3 支持,但 PackageHub 和第三方模块例外。使用 zypper info PACKAGE 命令可检查针对特定软件包的支持级别。

名称

依赖的模块

可用性

支持

内容

Basesystem

默认所有产品上均提供

生命周期:10 年
延长期:3 年 LTSS1

在安装程序上添加一个基本系统。其他所有模块和扩展都需要此模块。只包含基础系统的安装范围相当于旧版 SUSE Linux Enterprise Server精简系统安装模式。系统默认已选择安装此模块,不应将其取消选择。

Certifications

Basesystem

除 SLED 以外的所有产品

生命周期:持续到下一个 SP 发布
延长期:3 年 LTSS1

包含 FIPS 140-2 认证软件包。

您的 SUSE Linux Enterprise 订阅中已包含对 Certifications 模块的访问权限。

Containers

Basesystem

SLES、SLES-SAP、SLE-HPC

生命周期:10 年
延长期:

包含容器的支持、工具和映像。

Desktop Applications

Basesystem

SLED(默认)、SLE-WE(默认)、SLES、SLES-SAP、SLE-RT(默认)、SLE-HPC

生命周期:10 年
延长期:

向系统添加图形用户界面和最基本的桌面应用程序。

Development Tools

Basesystem、Desktop Applications

SLES、SLES-SAP、SLED、SLE-RT(默认)、SLE-HPC

生命周期:10 年
延长期:3 年 LTSS1

包含编译器(包括 gcc)以及编译和调试应用程序所需的库。取代了以前的 Software Development Kit (SDK)。

High Availability

Basesystem

SLES、SLES-SAP(已包含)、SLE-HPC

生命周期:10 年
延长期:3 年 LTSS1

添加了针对任务关键型设置的群集支持。随附的工具包括 Hawk、crm、Pacemaker 和 Corosync。SLES-SAP 的订阅中包含高可用性支持,因此 High Availability 可作为这些产品上的模块使用。它还可用作 SLES 和 SLE-HPC 的扩展(参见下文)。

High Performance Computing

Basesystem

SLE-HPC(已包含)

生命周期:10 年
延长期:3 年 LTSS1、1 年 ESPOS2

包含与高性能计算 (HPC) 相关的工具和库。

Legacy

Basesystem、Server Applications

SLES、SLES-SAP、SLE-HPC

通过提供 SUSE Linux Enterprise 中已停产的软件包,帮助您将应用程序从 SUSE Linux Enterprise Server 早期版本和其他系统迁移到 SLES 15 SP3。根据迁移要求和配置的复杂性级别选择此模块中的软件包。

从旧版产品迁移时,建议使用此模块。

NVIDIA Compute

Basesystem

AMD64/Intel 64 和 AArch64 上的 SLES 与 SLE-HPC

此模块中的软件由 NVIDIA 提供,SUSE 并不提供相关支持

包含 NVIDIA CUDA(Compute Unified Device Architecture,统一计算设备架构)驱动程序。

此模块中的软件由 NVIDIA 根据 CUDA 最终用户许可协议提供,不受 SUSE 支持。

重要
重要:不要使用 SUSEConnect 来添加此模块

不要尝试使用 SUSEConnect CLI 工具添加此模块。SUSEConnect 无法处理第三方储存库。

在安装期间,请从扩展和模块选择屏幕中选择该模块。在已安装的系统中运行 yast registration,依次选择选择扩展NVIDIA Compute 模块,然后选择下一步继续。校验并接受 NVIDIA 储存库 GPG 密钥。

重要
重要:不支持将 Workstation ExtensionNVIDIA Compute 模块结合使用

Workstation Extension 为 NVIDIA 显卡提供驱动程序。这些驱动程序与 CUDA 共用某些软件包,但它们的版本可能不同。因此,既不建议也不支持同时启用 NVIDIA Compute 模块Workstation Extension

Public Cloud

Basesystem、Server Applications

SLES、SLES-SAP、SLE-HPC

包含为在云环境中部署 SUSE Linux Enterprise Server 而创建映像所需的全部工具。例如:Amazon Web Services (AWS)、Microsoft Azure、Google Compute Platform 或 SUSE OpenStack Cloud。

Python 2

Basesystem

SLES、SLES-SAP、SLE-HPC、SLED

SUSE Linux Enterprise Server 15 SP3 使用 Python 版本 3。此模块包含 Python 2 运行时与模块。

您的 SUSE Linux Enterprise 订阅中已包含对 Python 2 模块的访问权限。

Real Time

Basesystem、Desktop Applications、Development Tools、Server Applications

SLE-RT(已包含)

旨在降低延迟并提高对时间敏感的任务关键型应用程序的可预测性和可靠性。

对此模块中的软件包的支持一般会持续到有更新版本的软件包发布或软件包从此模块中删除时为止。

SAP Applications

Basesystem

SLES-SAP(已包含)

生命周期:10 年
延长期:3.5 年 LTSS1、1.5 年 ESPOS2

包含特定于 SLES-SAP 的软件包。

Server Applications

Basesystem

SLES(默认)、SLES-SAP、SLE-RT(默认)、SLE-HPC

生命周期:10 年
延长期:3 年 LTSS1

通过提供 DHCP 服务器、名称服务器或 Web 服务器等网络服务来添加服务器功能。系统默认已选择安装此模块;不建议将其取消选择。

SUSE Cloud Application Platform Tools

Basesystem

SLED、SLES、SLES-SAP

添加用来与 SUSE Cloud Application Platform 产品交互的工具。

SUSE Package Hub

Basesystem

所有产品

生命周期:
延长期:
级别:

用于访问 openSUSE 社区维护的各个 SUSE Linux Enterprise Server 软件包。对于这些软件包不提供 L3 支持,但这不影响对 SUSE Linux Enterprise Server 的支持。有关详细信息,请参见https://packagehub.suse.com/

Transactional Server

Basesystem

SLES

事务更新通过以“原子”方式整体更新操作系统及其软件包的方法来提供 SUSE Linux Enterprise 系统。更新将以单个事务的形式统一应用到系统,或者全部都不应用。这种方式不会影响正在运行的系统。如果更新失败,或者如果成功更新被视为不兼容或不正确,您可以立即将其丢弃。这样会使系统回到先前的正常运行状态。

您的 SUSE Linux Enterprise Server 订阅中已包含对 Transactional Server 模块的访问权限。

Web and Scripting

Basesystem、Server Applications

SLES、SLES-SAP、SLE-HPC

包含用于运行中 Web 服务器的软件包。

1 LTSS:长期服务包支持
2 ESPOS:延期的服务包覆盖支持

3 SUSE Linux Enterprise 产品系列的扩展

SUSE Linux Enterprise 产品系列中提供下列扩展。请注意,扩展的可用性取决于产品(请参考可用性这列)。

名称和内容

模块依赖项

可用性

SUSE Linux Enterprise High Availability Extension

Basesystem、Server Applications

SLES

SUSE Linux Enterprise Live Patching

Basesystem

SLES

SUSE Linux Enterprise Workstation Extension

Basesystem、Desktop Applications

SLES、SLED(默认)

4 安装和管理

在初始设置系统时以及在现有的 SUSE Linux Enterprise Server 安装上可安装模块和扩展。

4.1 在初始系统设置期间安装模块和扩展

在设置系统时可轻松安装模块和扩展。相应步骤属于安装例程的一部分。如果使用默认安装路径,您需要拥有网络访问权限以访问提供相应储存库的 SUSE Customer Center 或本地注册服务器(SUSE Manager 或 Repository Mirroring Tool)。您也可以采用脱机安装方式。脱机安装需要额外的安装媒体。有关详细信息,请参见第 8.8 节 “扩展和模块选择”

4.2 从正在运行的系统上安装和管理模块与扩展

要从正在运行的系统安装模块和扩展,您需要确保系统已在 SUSE Customer Center 或本地注册服务器中注册。如果您在安装期间未注册系统,请参考第 9.3 节 “从安装的系统注册”中的相关说明。

注册系统后,便可添加或去除模块。有关细节,请参考第 9.4 节 “在正在运行的系统中管理模块和扩展”

5 软件包的模块成员资格

默认情况下,用于搜索软件包的工具(YaST 软件管理或 zypper search)被限制为仅可在已激活的储存库中搜索。要将搜索范围扩展到尚未激活的远程储存库,您可以运行 zypper search-packages。要了解某个软件包所属的模块,请运行

zypper search-packages PACKAGE

如果 search-packages 子命令在您的系统上不可用,请安装软件包 zypper-search-packages-plugin

提示
提示:在 SUSE Customer Center 中搜索软件包

为防止 Zypper 的软件包搜索命令在您的系统上不可用,您还可以使用 SUSE Customer Center Web 界面(软件包搜索)来检查软件包及其相应模块的可用性。要执行此操作,请访问 https://scc.suse.com/packages。此服务需要登录 SUSE。

zypper search-packages 提供了以下选项供您调整搜索结果:

-x--match-exact

搜索完全匹配项。

-g--group-by-module

按模块而非软件包名称对搜索结果分组。

-d--details

同时列出版本号和包含该软件包的储存库。

--xmlout

生成 XML 输出。

下面是如何使用 zypper search-packages 的一些示例。

例 1︰ 简单搜索

下面的命令会搜索软件包 nodejshawk。第一个软件包在 Web and Scripting 模块中提供,第二个软件包属于 SUSE Linux Enterprise High Availability Extension 的一部分。这两个软件包都尚未安装:

tux > zypper search-packages openjdk nodejs
Following packages were found in following modules:

Package          Module or Repository
---------------  --------------------------------------------------------------------
java-10-openjdk  Legacy Module (sle-module-legacy/15.2/x86_64)          
                    SUSEConnect --product sle-module-legacy/15.2/x86_64
java-11-openjdk  Basesystem Module (sle-module-basesystem/15.2/x86_64)  
                    SUSEConnect --product sle-module-basesystem/15.2/x86_64                 
nodejs10         Web and Scripting Module (sle-module-web-scripting/15.2/x86_64)                         
                    SUSEConnect --product sle-module-web-scripting/15.2/x86_64    
nodejs12         Web and Scripting Module (sle-module-web-scripting/15.2/x86_64)                         
                    SUSEConnect --product sle-module-web-scripting/15.2/x86_64 
[...]
例 2︰ 搜索完全匹配项

如果您知道确切的软件包名称,则可以使用选项 -x 将搜索结果缩小到完全匹配的软件包:

tux > zypper search-packages -x java-11-openjdk nodejs12
Following packages were found in following modules:

Package          Module or Repository
---------------  -----------------------------------------------------------------
java-11-openjdk  Basesystem Module (sle-module-basesystem/15.2/x86_64)                                          
                   SUSEConnect --product sle-module-basesystem/15.2/x86_64
nodejs12         Web and Scripting Module (sle-module-web-scripting/15.2/x86_64)                         
                   SUSEConnect --product sle-module-web-scripting/15.2/x86_64    
[...]
例 3︰ 搜索已安装或提供的软件包

如果您要搜索的软件包已安装或在您系统上可用的某个模块中提供,搜索结果会有所不同。在下面的示例中,软件包 vim 已安装。软件包 emacs 未安装,但不必添加模块就可进行安装。

tux > zypper search-packages -x vim
Following packages were found in following modules:

Package  Module or Repository
-------  ---------------------------------------------------
vim      Basesystem Module (sle-module-basesystem/15/x86_64)
vim      Installed
vim      Available

tux > zypper search-packages -x emacs
Following packages were found in following modules:

Package  Module or Repository
-------  ---------------------------------------------------
emacs    Basesystem Module (sle-module-basesystem/15/x86_64)
emacs    Available

如果不搜索软件包,您还可以查看属于某个模块或扩展的软件包列表。启动 YaST 软件管理模块,然后单击查看 › 服务。选择一项以显示属于此模块或扩展的软件包列表。

6 法律声明

版权所有 © 2006–2024 SUSE LLC 和贡献者。保留所有权利。

根据 GNU 自由文档许可 (GNU Free Documentation License) 版本 1.2 或(根据您的选择)版本 1.3 中的条款,在此授予您复制、分发和/或修改本文档的权限;本版权声明和许可附带不可变部分。许可版本 1.2 的副本包含在题为GNU Free Documentation License的部分。

有关 SUSE 商标,请参见 https://www.suse.com/company/legal/。所有其他第三方商标分别为相应所有者的财产。商标符号(®、™ 等)代表 SUSE 及其关联公司的商标。星号 (*) 代表第三方商标。

本指南力求涵盖所有细节,但这不能确保本指南准确无误。SUSE LLC 及其关联公司、作者和译者对于可能出现的错误或由此造成的后果皆不承担责任。

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

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.

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 sub-unit 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.

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.

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.

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:

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

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

  3. State on the Title page the name of the publisher of the Modified Version, as the publisher.

  4. Preserve all the copyright notices of the Document.

  5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

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

  7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.

  8. Include an unaltered copy of this License.

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

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

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

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

  13. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.

  14. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.

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

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

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.

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.

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.

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.

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 http://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.

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.