SUSE Linux Enterprise Desktop 15 SP1
SUSE Linux Enterprise Desktop 15 SP1
This Quick Start guides you step-by-step through the installation of SUSE®
Linux Enterprise Desktop 15 SP1.
Contents
1 Welcome to SUSE Linux Enterprise Desktop 2
2 Legal Notice 29
1 SLED 15 SP1
1 Welcome to SUSE Linux Enterprise Desktop
Use the following procedures to install the product on all supported hardware platforms. They
assume you have successfully booted into the installation system. For more detailed installation
instructions and deployment strategies, refer to the Book “Deployment Guide”. For preparations
required to boot into the installation system, refer to Book “Deployment Guide”, Chapter 2 “Instal-
lation on AMD64 and Intel 64”.
The Language and Keyboard Layout settings are initialized with the language you chose on the
boot screen. If you did not change the default, it will be English (US). Change the settings here,
if necessary. Use the Keyboard Test text box to test the layout.
With the Unified Installer you can install all SUSE Linux Enterprise base products:
Select a product for installation. You need to have a registration code for the respective product.
In the course of this document it is assumed you have chosen SUSE Linux Enterprise Desktop.
Proceed with Next.
A system analysis is performed, where the installer probes for storage devices, and tries to nd
other installed systems. If the network was automatically configured via DHCP during the start
of the installation, you will be taken to the registration step.
If the network is not yet configured, the Network Settings dialog opens. Choose a network inter-
face from the list and configure it with Edit. Alternatively, Add an interface manually. See Book
“Deployment Guide”, Chapter 4 “Installation Steps”, Section 4.5 “Network Settings” and Book “Admin-
1.1.4 Registration
To get technical support and product updates, you need to register and activate your product
with the SUSE Customer Center or a local registration server. Registering SUSE Linux Enterprise
Desktop at this stage also grants you immediate access to the update repository. This enables
you to install the system with the latest updates and patches available.
When registering, repositories and dependencies for the modules and extensions, which you
may install with the next step, are loaded from the registration server.
If you are offline or want to skip registration, activate Skip Registration. Proceed with the instal-
lation by following the instructions in Section 1.2, “Installing without Registration”.
After the system is successfully registered, the installer lists modules and extensions that are
available for SUSE Linux Enterprise Desktop. Modules are components which allow you to shape
the product according to your needs. They are free of charge. Extensions add functionality to
your product. They are offered as subscriptions and require a registration key that is liable for
costs.
The availability of certain modules or extensions depends on the product you have chosen in
the rst step of this installation. For a description of the modules and their lifecycles, select a
module to see the accompanying text. More detailed information is available in the Modules and
Extensions Quick Start (https://documentation.suse.com/sles/html/SLES-all/art-modules.html) and
the Release Notes (https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/#Intro.Module) .
The selection of modules indirectly affects the scope of the installation, because it defines which
software sources (repositories) are available for installation and in the running system.
Basesystem Module
This module adds a basic system on top of the Unified Installer. It is required by all other
modules and extensions. The scope of an installation that only contains the base system is
comparable to the installation pattern minimal system of previous SUSE Linux Enterprise
Desktop versions. This module is selected for installation by default and should not be
deselected.
Dependencies: None
Python 2 Module
SUSE Linux Enterprise 15 SP1 uses Python version 3. This module contains the Python
2 runtime and modules. It is selected for installation by default; deselecting it is not rec-
ommended.
Dependencies: Basesystem
Some modules depend on the installation of other modules. Therefore, when selecting a module,
other modules may be selected automatically to fulfill dependencies.
Depending on the product, the registration server can mark modules and extensions as recom-
mended. Recommended modules and extensions are preselected for registration and installation.
To avoid installing these recommendations, deselect them manually.
Select the modules and extension you would like to install and proceed with Next. In case you
have chosen one or more extensions, you will be prompted to provide the respective registra-
tion codes. Depending on your choice, it may also be necessary to accept additional license
agreements.
The Add-On Product dialog allows you to add additional software sources (so-called “reposito-
ries”) to SUSE Linux Enterprise Desktop, that are not provided by the SUSE Customer Center.
Such add-on products may include third-party products and drivers or additional software for
your system.
If you want to skip this step, proceed with Next. Otherwise activate I would like to Install an Add-
on Product. Specify a media type, a local path, or a network resource hosting the repository and
follow the on-screen instructions.
The availability of system roles depends on your selection of modules and extensions. System
roles define, for example, the set of software patterns that is going to be preselected for the
installation. Refer to the description on screen to make your choice. Select a role and proceed
with Next. If from the enabled modules only one role or no role is suitable for the respective
base product, the System Role dialog is omitted.
Review the partition setup proposed by the system. If necessary, change it. You have the fol-
lowing options:
Guided Setup
Starts a wizard which lets you refine the partitioning proposal. Options available here
depend on your system setup. In case it contains more than a single hard disk, you may
choose which disk(s) to use and where to place the root partition. If the disk(s) already
contain partitions, decide whether to remove or resize them.
Expert Partitioner
Opens the Expert Partitioner described in Book “Deployment Guide”, Chapter 6 “Expert Parti-
tioner”, Section 6.1 “Using the Expert Partitioner”. This gives you full control over the partition-
ing setup and lets you create a custom setup. This option is intended for experts.
To accept the proposed setup without any changes, choose Next to proceed.
Select the clock and time zone to use in your system. To manually adjust the time or to configure
an NTP server for time synchronization, choose Other Settings. See Book “Deployment Guide”,
Chapter 4 “Installation Steps”, Section 4.11 “Clock and Time Zone” for detailed information. Proceed
with Next.
To create a local user, type the rst and last name in the User’s Full Name eld, the login name
in the Username eld, and the password in the Password eld.
The password should be at least eight characters long and should contain both uppercase and
lowercase letters and numbers. The maximum length for passwords is 72 characters, and pass-
words are case-sensitive.
For security reasons it is also strongly recommended not to enable the Automatic Login. You
should also not Use this Password for the System Administrator but rather provide a separate root
password in the next installation step.
If you install on a system where a previous Linux installation was found, you may Import User
Data from a Previous Installation. Click Choose User for a list of available user accounts. Select
one or more user.
In an environment where users are centrally managed (for example by NIS or LDAP) you may
want to skip the creation of local users. Select Skip User Creation in this case.
Type a password for the system administrator (called the root user) or provide a public SSH
key. If you want, you can use both.
Because the root user is equipped with extensive permissions, the password should be chosen
carefully. You should never forget the root password! After you entered it here, the password
cannot be retrieved.
Use the Installation Settings screen to review and—if necessary—change several proposed instal-
lation settings. The current configuration is listed for each setting. To change it, click the head-
line. Some settings, such as firewall or SSH can directly be changed by clicking the respective
links.
Software
The scope of the installation is defined by the modules and extensions you have chosen
for this installation. However, depending on your selection, not all packages available in
a module are selected for installation.
Clicking Software opens the Software Selection and System Tasks screen, where you can
change the software selection by selecting or deselecting patterns. Each pattern contains
several software packages needed for specific functions (for example, KVM Host Server). For
a more detailed selection based on software packages to install, select Details to switch to
the YaST Software Manager. See Book “Deployment Guide”, Chapter 15 “Installing or Removing
Software” for more information.
Booting
This section shows the boot loader configuration. Changing the defaults is only recom-
mended if really needed. Refer to Book “Administration Guide”, Chapter 14 “The Boot Loader
GRUB 2” for details.
Security
The CPU Mitigations refer to kernel boot command line parameters for software mitigations
that have been deployed to prevent CPU side-channel attacks. Click the highlighted entry
to choose a different option. For details, see Book “Administration Guide”, Chapter 14 “The
Boot Loader GRUB 2” CPU Mitigations.
By default, the Firewall is enabled with all network interfaces configured for the public
zone. See Book “Security Guide”, Chapter 17 “Masquerading and Firewalls”, Section 17.4 “fire-
walld” for configuration details.
The SSH service is enabled by default, its port (22) is open. Click enable and open to toggle
these settings. Note that if SSH is disabled, logging in from remote will not be possible.
Network Configuration
Displays the current network configuration. Click Network Configuration to change the set-
tings. For details, see Book “Administration Guide”, Chapter 19 “Basic Networking”, Section 19.4
“Configuring a Network Connection with YaST”.
System
View detailed hardware information by clicking System. In the resulting screen you can
also change Kernel Settings—see Book “Deployment Guide”, Chapter 4 “Installation Steps”, Sec-
tion 4.14.7 “System” for more information.
After you have finalized the system configuration on the Installation Settings screen, click Install.
Depending on your software selection you may need to agree to license agreements before the
installation confirmation screen pops up. Up to this point no changes have been made to your
system. After you click Install a second time, the installation process starts.
During the installation, the progress is shown in detail on the Details tab. The SUSE Linux Enter-
prise Desktop Release Notes tab shows important information; reading them is recommended.
After the installation routine has finished, the computer is rebooted into the installed system. Log
in and start YaST to ne-tune the system. If you are not using a graphical desktop or are working
from remote, refer to Book “Administration Guide”, Chapter 5 “YaST in Text Mode” for information
on using YaST from a terminal.
To perform the installation without registration, make sure the contents of the SLE-15-SP1-Pack-
ages- ARCH -GM-DVD1.iso image can be accessed during the installation. This can be achieved
by copying it to a local hard disk or a removable ash disk or by making it available in the local
network. Choose a method that is supported by your hardware.
PATH_TO_IMAGE needs to be replaced with the relative or absolute path to this image
le. FLASH_STORAGE_PARTITION needs to be replaced with the path to a partition on the
ash device (usually there is just one). To identify the device, and its partition(s), insert
it and use the commands shown in the example below:
dd if=/tmp/SLE-15-SP1-Packages-ARCH-GM-DVD1.iso \
of=/dev/sdc1 bs=4M && sync
Make sure a partition with sufficient size (8 GB or more) exists on the device. It also must
not be mounted when running the dd command. Note that all data on the partition will
be erased!
The installation follows the same workflow as outlined in Section 1.1, “The Default Installation
Procedure”, only the steps for registering the system and adding modules/extensions differ. To
start the installation, perform the steps Section 1.1.1, “Language, Keyboard, and Product Selection” to
Section 1.1.3, “Network Settings” from Section 1.1, “The Default Installation Procedure”.
On the Registration screen activate Skip Registration. Accept the warning with OK and proceed
with Next.
On the Add On Product dialog, activate I would like to install an additional Add On Product and spec-
ify the source for the SLE-15-SP1-Packages- ARCH -GM-DVD1.iso image. Check Download repos-
itory description les to download the les describing the repository now. If deactivated, they
will be downloaded after the installation starts. Proceed with Next. If you chose DVD as the data
source, you will be prompted to insert the media.
On the Extension and Module Selection dialog you need to select a product, at least one module,
and optionally, one or more extensions.
The SLE-15-SP1-Packages- ARCH -GM-DVD1.iso images contain extensions and modules for all
SUSE Linux Enterprise products. Make sure to only select modules and extensions listed below,
otherwise you will end up with a system that may fail to install and is not covered by SUSE
support.
Product
Selecting a product is mandatory. Choose SLED15-SP1 15.1-0.
Modules
Modules extend the functionality of SUSE Linux Enterprise Desktop and are free of charge.
Installing the Basesystem-Module 15.1-0 is required. It is also recommended to install the
Desktop-Applications-Module 15.1-0.
Basesystem-Module 15.1-0. This module adds a basic system on top of the Unified Installer.
It is required by all other modules and extensions. The scope of an installation that only
contains the base system is comparable to the installation pattern minimal system of previ-
ous SUSE Linux Enterprise Desktop versions. Dependencies: None
Python 2 Module 15.1-0. SUSE Linux Enterprise 15SP 1 uses Python version 3. This module
contains the Python 2 runtime and modules. Dependencies: Basesystem
Containers-Module 15.1-0
HPC-Module 15.1-0
Legacy-Module 15.1-0
Live-Patching 15.1-0
Public-Cloud-Module 15.1-0
SAP-Applications-Module 15.1-0
SLE-15-1-HPC 15.1-0
SLE-15-1-RT 15.1-0
SLE-15-1-SAP 15.1-0
SLEHA15-1 15.1-0
When you have finished selecting modules and extensions, proceed with Next.
All modules selected for installation are listed on the Add-On Product Installation dialog. To
change the list, use the Add or Delete options. Using Add you may optionally add other add-on
products. Proceed with the installation with Next.
From this point on, the installation follows the same path as the default installation. Proceed
with the step>Section 1.1.7, “System Role” from Section 1.1, “The Default Installation Procedure”.
2 Legal Notice
Copyright© 2006– 2020 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 trade-
marks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trade-
marks 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.
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.
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 t 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.
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 t legibly, you should put the rst ones listed (as many as t 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:
A. 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.
B. 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 ve of the principal
authors of the Document (all of its principal authors, if it has fewer than ve), unless they release you from this requirement.
C. State on the Title page the name of the publisher of the Modified Version, as the publisher.
E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
F. 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.
G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
I. 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.
J. 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.
K. 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.
L. 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.
N. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
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 ve 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 "Acknowl-
edgements", 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.
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.
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.
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.