SUSE Best Practices

How to Set Up a Multi-PXE Installation

Server

SUSE Linux Enterprise Server

David Byte, Senior Technology Strategist, SUSE

1 How to Set Up a Multi-PXE Installation Server

 This SUSE Best Practices document explains how to set up a multi-architec-
ture PXE environment for the installation of the SUSE Linux Enterprise Serv-
er operating system on x86_64 and ARMv8 platforms with both BIOS and
EFI.
Components that usually should be hosted on the installation server are also
included. This helps improving deployment times in multi-architecture envi-
ronments.

Publication Date: September 25, 2018

Contents
1 System Requirements 3

2 Installing the Operating System 3

3 Setting Up NTP Server 4

4 Setting Up DHCP Services 4

5 Setting Up Repositories 5

6 Setting Up TFTP 5

7 Setting Up PXE Boot 5

8 Setting Up SMT 8

9 Installation Server Completed 8

10 Legal Notice 8

11 GNU Free Documentation License 9

2 How to Set Up a Multi-PXE Installation Server

1 System Requirements
For a reasonable install server, you need:

200 GB drive space

5 GB RAM

Two network connections

The relatively huge drive space is needed if your installation server should also serve as your
Subscription Management (SMT) server. Your deployment will use the SMT server in an ongo-
ing manner for mirroring updates for the architectures in question in addition to hosting the
installation repositories.

2 Installing the Operating System

First, install SUSE Linux Enterprise Server 12 SP2 on a virtual or a physical system.
On the registration screen, click the “Network Configuration” button at the upper right and
configure the network. You can use two different interfaces: one for the public network with
access to the Internet, and one for the cluster network. Deploying using the cluster network has
several advantages:

It is a private network for the storage systems only and thus there will be no conflict with
other DHCP servers or PXE servers

Generally it is faster than the public network

Use the Installation Settings screen to review and change several proposed installation settings.
Clicking Software opens the Software Selection and System Tasks screen, where you can
change the software selection by selecting or deselecting patterns.
The default scope of software includes the base system and X Window with the GNOME desktop.
Deselect “X Window with the GNOME desktop”. For this, you are also safe deselecting 32-bit
compatibility libraries.

3 How to Set Up a Multi-PXE Installation Server

3 Setting Up NTP Server
The NTP server is used to act as an authoritative time source. Start YaST, select NTP Server
and configure it to start at boot time. Under security settings, select Open Port in Firewall and
click OK. When you use the install server, you can point the systems being deployed back to
it for time synchronization.

4 Setting Up DHCP Services

Go into YaST and select DHCP Server from network services. Configure the IP range you want
to use. After that, it is your choice on whether you use YaST or edit the configuration le ( /etc/
dhcpd.conf ) manually. As with the other services, be sure to open the ports in the firewall. The
end result needs to be a le that looks like the below:

option domain-name "my.lab";

option domain-name-servers 172.16.253.5;
option routers 192.168.124.1;
option ntp-servers 192.168.124.3;
option arch code 93 = unsigned integer 16; # RFC4578
default-lease-time 3600;
ddns-update-style none;
subnet 192.168.124.0 netmask 255.255.255.0 {
range 192.168.124.100 192.168.124.199;
next-server 192.168.124.3;
default-lease-time 3600;
max-lease-time 3600;
if option arch = 00:07 or option arch = 00:09 {
filename "/EFI/x86/bootx64.efi";
} else if option arch = 00:0b {
filename "/EFI/armv8/bootaa64.efi";
} else {
filename "/bios/x86/pxelinux.0";
}
}

Note: if option arch

The if option arch sections allow the DHCP server to make the correct decision on
which le to use for booting.

4 How to Set Up a Multi-PXE Installation Server

5 Setting Up Repositories
The next step is to create the installation source directories. Use a structure similar to /srv/
install/arch/product/version .

/srv/install/x86/sles12/sp2/cd1
/srv/install/armv8/sles12/sp2/cd1

Now mount the install media into the appropriate location. Be sure to add it to /etc/fstab
for persistence between reboots.

mount -o loop, crossmnt /root/sles12sp2.iso /srv/install/x86/sles12/sp2/cd1/

Do the same for each architecture’s boot media.

The final part of setting up the repositories is to export them. Although there are other supported
methods such as HTTP, FTP, etc., use NFS for this scenario. First, enable the NFS server through
YaST and select Open Port in Firewall. In this instance, export the entire /srv/install
structure as seen in the sample /etc/exports entry below.

/srv/install *(ro,root_squash,sync,no_subtree_check)

6 Setting Up TFTP
Now you need to enable the TFTP server. To do so, start YaST and select TFTP Server from
Network Services. The system then prompts to “install tftp”. Select Enable, leave the image
directory at /srv/tftpboot , select Open Port in Firewall, and click OK.

7 Setting Up PXE Boot

To ensure you set up your install server correctly, read carefully through the following sections.
Proceed as described and double check your entries to avoid typos. Getting all the right les in
the right places allows you to add more architectures, operating system install options, etc.
Create a structure in /srv/tftpboot to support the various options:

mkdir /srv/tftpboot/bios
mkdir /srv/tftpboot/bios/x86
mkdir /srv/tftpboot/EFI
mkdir /srv/tftpboot/EFI/x86
mkdir /srv/tftpboot/EFI/x86/boot

5 How to Set Up a Multi-PXE Installation Server

mkdir /srv/tftpboot/EFI/armv8
mkdir /srv/tftpboot/EFI/armv8/boot

7.1 Setting Up the x86 BIOS Boot Environment

At this point, you need to copy the necessary boot les for the x86 BIOS environment to the
appropriate boot location. To do so, navigate to the appropriate directory as shown below:

cd /srv/install/x86/sles12/sp2/cd1/boot/x86_64/loader/
cp -a linux initrd message /srv/tftpboot/bios/x86/

While still in the loader directory, create the directory for the configuration le and copy it in:

mkdir /srv/tftpboot/bios/x86/pxelinux.cfg
cp -a isolinux.cfg /srv/tftpboot/bios/x86/pxelinux.cfg/default

Copy pxelinux.0 to the same structure:

cp /usr/share/syslinux/pxelinux.0 /srv/tftpboot/bios/x86/

Now that the les are all in place, edit the configuration to ensure all the correct boot options
are also in place. Start with editing /srv/tftpboot/bios/x86/pxelinux.cfg/default . See
the example below:

default harddisk

# hard disk
label harddisk
localboot -2
# install
label install
kernel linux
append initrd=initrd showopts install=nfs://192.168.124.3/srv/install/x86/sles12/sp2/
cd1

display message
implicit 0
prompt 1
timeout 600

Now edit /srv/tftpboot/bios/x86/message to reflect the default le you edited before. See
the example below:

Welcome to the Installer Environment!

To start the installation enter 'install' and press <return>.

6 How to Set Up a Multi-PXE Installation Server

Available boot options:
harddisk - Boot from Hard Disk (this is default)
install - Installation

Have a lot of fun...

7.2 Setting Up the x86 EFI Boot Environment

Start by copying the les required for UEFI booting of a grub2-e environment.

cd /srv/install/x86/sles12/sp2/cd1/EFI/BOOT
cp -a bootx64.efi grub.efi MokManager.efi /srv/tftpboot/EFI/x86/

Copy the kernel and initrd to the directory structure.

cd /srv/install/x86/sles12/sp2/cd1/boot/x86_64/loader/
cp -a linux initrd /srv/tftpboot/EFI/x86/boot

Now you need to create a grub.cfg le. This le goes in /srv/tftpboot/EFI/x86 and should
have contents similar to the below example:

set timeout=5
menuentry 'Install SLES12 SP2 for x86_64' {
linuxefi /EFI/x86/boot/linux install=nfs://192.168.124.3/srv/install/x86/sles12/sp2/cd1
initrdefi /EFI/x86/boot/initrd
}

7.3 Setting Up the ARMv8 EFI Boot Environment

Setting up the ARMv8 EFI boot environment is done in a way very similar to the x86_64 EFI
environment. Start by copying the les required for UEFI booting of a grub2-e environment:

cd /srv/install/armv8/sles12/sp2/cd1/EFI/BOOT
cp -a bootaa64.efi /srv/tftpboot/EFI/armv8/

Copy the kernel and initrd to the directory structure:

cd /srv/install/armv8/sles12/sp2/cd1/boot/aarch64
cp -a linux initrd /srv/tftpboot/EFI/armv8/boot

Next you need to edit the grub.cfg le and add a new section. This le is located in the
directory /srv/tftpboot/EFI/armv8 . You should add contents similar to the example below.

menuentry 'Install SLES12 SP2 for SoftIron OverDrive' {

7 How to Set Up a Multi-PXE Installation Server

 linux /EFI/armv8/boot/linux network=1 usessh=1 sshpassword="suse" \
install=nfs://192.168.124.3/srv/install/armv8/sles12/sp2/cd1 \
console=ttyAMA0,115200n8
initrd /EFI/armv8/boot/initrd
}

This addition to the configuration le contains a few other options to enable the serial console
and to allow installation via ssh . This is helpful for systems that do not have a standard KVM
console interface.

Note: ARM Platforms

Be aware that this configuration is specifically set up only for a specific ARM platform.

8 Setting Up SMT
The SMT service provides a local repository mirror for updates to your software. Fol-
low the instructions in the Subscription Management Tool Guide at https://documenta-
tion.suse.com/sles/12-SP4/html/SLES-all/smt-installation.html to install and configure SMT. Be
sure to select both the pool and update repositories for each product you are supporting with
this server.

9 Installation Server Completed

At this point, you are ready to use the installation server for BIOS and EFI on x86 and EFI on
ARMv8. Be sure to select the SMT server as the registration server during installation. You can
gain further value by building custom AutoYaST les as well. These les can enable a stream-
lined installation process and even an unattended process if everything is well defined.

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

8 How to Set Up a Multi-PXE Installation Server

SUSE, the SUSE logo and YaST are registered trademarks of SUSE LLC in the United States
and other countries. For SUSE trademarks, see http://www.suse.com/company/legal/ . Linux is
a registered trademark of Linus Torvalds. All other names or trademarks mentioned in this
document may be trademarks or registered trademarks of their respective owners.
This article is part of a series of documents called "SUSE Best Practices". The individual docu-
ments in the series were contributed voluntarily by SUSE's employees and by third parties.
The articles are intended only to be one example of how a particular action could be taken. They
should not be understood to be the only action and certainly not to be the action recommended
by SUSE. Also, SUSE cannot verify either that the actions described in the articles do what they
claim to do or that they don't have unintended consequences.
Therefore, we need to specifically state that neither SUSE LLC, its affiliates, the authors, nor the
translators may be held liable for possible errors or the consequences thereof. Below we draw
your attention to the license under which the articles are published.

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 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.
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 le 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 stan-
dard-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.

9 How to Set Up a Multi-PXE Installation Server

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

D. Preserve all the copyright notices of the Document.

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.

H. Include an unaltered copy of this License.

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.

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

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

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

10 How to Set Up a Multi-PXE Installation Server

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.

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

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.

11 How to Set Up a Multi-PXE Installation Server

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.

12 How to Set Up a Multi-PXE Installation Server