Jump to content

SUSE Manager for Retail Migration Guide

Publication Date: 2019-09-20

1 Introduction

1.1 What is SUSE Manager for Retail?

SUSE Manager for Retail 3.2 is an open source infrastructure management solution, optimized and tailored specifically for the retail industry. It uses the same technology as SUSE Manager, but is customized to address the needs of retail organizations.

SUSE Manager for Retail is designed for use in retail situations where customers can use point-of-service terminals to purchase or exchange goods, take part in promotions, or collect loyalty points. In addition to retail installations, it can also be used for novel purposes, such as maintaining student computers in an educational environment, or self-service kiosks in banks or hospitals.

SUSE Manager for Retail is intended for use in installations that include servers, workstations, point-of-service terminals, and other devices. It allows administrators to install, configure, and update the software on their servers, and manage the deployment and provisioning of point-of-service machines.

1.2 About this book

This document provides instructions for migrating SUSE Linux Enterprise Point of Service 11 or SUSE Manager for Retail 3.1 to SUSE Manager for Retail {smrproductnumber}.

It should be read in conjunction with the SUSE Manager for Retail documentation suite, available from https://www.suse.com/documentation/suse-manager-for-retail/.

2 Prepare to Migrate

2.1 Before you Begin

This book is intended to guide you through migration your SUSE Linux Enterprise Point of Service or older SUSE Manager for Retail installation, to the newest version of SUSE Manager for Retail.

Important
Important

Migrating configuration from SUSE Linux Enterprise Point of Service to SUSE Manager for Retail is a technology preview and will be enhanced in future releases of SUSE Manager.

The book is divided into scenarios. Pick the scenario that best suits your environment, and follow the instructions in that chapter to migrate your installation.

Note
Note

Ensure your existing installation is fully updated, and that you have performed a backup, before you begin your migration.

2.2 Migration Scenarios

This document contains several different migration scenarios. Ensure you pick the most appropriate migration scenario for your environment.

If you are migrating from SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail, and you do not have a SUSE Manager installation, see SLEPOS to new SUSE Manager.

If you are migrating from SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail, and you already have a SUSE Manager installation that you want to use, see SLEPOS to Independent SUSE Manager.

2.2.1 Migrating from SUSE Linux Enterprise Point of Service

SUSE Linux Enterprise Point of Service cannot be upgraded directly to SUSE Manager for Retail, so the migration process requires you to perform some manual configuration. To assist you in the migration, as much information as possible about the existing hardware configuration and network infrastructure is recorded and then prepared and used for rebuilding the new SUSE Manager for Retail installation.

In some cases, this will require a lengthy downtime to perform the migration. If you are not able to manage downtime, you can install new servers and run them in parallel to the existing ones while you perform the migration. This is especially relevant for large installations.

It is possible to run a SLEPOS Admin server and a SUSE Manager server in parallel, as branches that have been migrated will run on the SUSE Manager server, while those which have not yet been migrated can continue to run on the Admin server. This includes all operations, such as adding new terminals, or building and deploying new images.

However, if you run network services (especially DHCP) on the branch servers, you will not be able to run both old and new branch servers in parallel on the same branch, because they can conflict with each other. This can result in multiple terminals having the same IP address, or terminals randomly assigned to different branch servers. If you need to migrate in this environment, and you want to configure a new Branch server while the branch is still running on old infrastructure, make sure that the new Branch server is not connected to the network with the terminals.

If your branch server does not provide DHCP services, you can configure the new one in parallel and, when you are ready, change the configuration of your DHCP server from the old to the new branch server.

3 SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail

3.1 Migration from SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail

This section describes migrating from an existing SUSE Linux Enterprise Point of Service 11 installation, to a new SUSE Manager installation. You can perform this migration all at once by creating a data dump in a single file, then moving it to the new server; see Section 3.1.1, “Migration with Complete Data Dump”. Alternatively, you can perform the migration in stages by creating a data dump for each branch, and moving them to the new server one by one; see Section 3.1.2, “Migration with Branch by Branch Data Dump”. Importing and deploying the converted data can also be done in one step, or multiple steps, depending on your environment.

3.1.1 Migration with Complete Data Dump

In this procedure, you create a single data dump in an XML file, convert it to YAML, and migrate it to the new infrastructure all at once.

  1. Install a SUSE Manager server 3.2 (with the Retail pattern). For more information, see https://www.suse.com/documentation/suse-manager-for-retail-3-2/retail-getting-started/retail.chap.install.html.

  2. On the SLEPOS Admin server export all the data stored in LDAP to an XML file. Run this command as an administrator:

    posAdmin --export --type xml --file dumpfile.xml

    The resulting dumpfile.xml file will contain global information, with parts about images, hardware and its partitioning, and the description of the branch servers with networking data, services, and attached terminals.

  3. Move the XML file to the newly created SUSE Manager server, and convert it to YAML:

    retail_migration dumpfile.xml retail.yml
  4. Review the generated YAML file (retail.yml) and adjust it as necessary. Consider HWTYPE group naming and image name and version changes in the partitioning data. Group names must not exceed the 56 character limit. You can shorten the names as needed, and the image names must match the images in SUSE Manager. The --save-mapping option can help you with this task.

    Also check whether there are duplicate MAC addresses of the terminals in the generated YAML file. Choose which entry you want to keep. If there are duplicate MAC addresses, importing the YAML file will fail.

    Note
    Note

    SUSE Linux Enterprise Point of Service images will not be migrated. You must rebuild the images using the OS image building functionality. For more information about building images, see https://www.suse.com/documentation/suse-manager-3/3.2/susemanager-advanced-topics/html/book.suma.advanced.topics/at.images.html#at.images.kiwi.

  5. Import the complete data (YAML) with:

    retail_yaml --from-yaml retail.yml

    You can see statistical data while importing. Then check the results in the Web UI. In Main MenuSystemsSystemsAll, find empty profiles, and in Main MenuSystemsGroups, the groups for the hardware configuration, the branches, servers, and terminals.

To finalize the branch server migration, you must install the branch server machines as Salt-based minions and bootstrap them as proxies. For more information about proxy installation, see Installing and Registering. For more information about using an activation key to assign the required channels, see Configuring Server. After onboarded to SUSE Manager, the branch servers machines are connected with the empty profiles (by FQDN), and so they will get the Retail configuration.

After all the branches are migrated, shutdown and remove the old SLEPOS Admin Server.

3.1.2 Migration with Branch by Branch Data Dump

In this procedure, you migrate the SLEPOS infrastructure and the branches one by one, first exporting and then importing.

  1. Install a SUSE Manager server 3.2 (with the Retail pattern). For more information, see https://www.suse.com/documentation/suse-manager-for-retail-3-2/retail-getting-started/retail.chap.install.html.

  2. On every branch server:

    posAdmin --export --type xml --file dumpfile.xml

    These dumps will contain only the LDAP data of the branch, and any global data.

  3. Similarily, you can export the LDAP data of every branch if you run the command on the Admin server with the branch credentials explicitly specified:

    posAdmin --export --type xml --file dumpfile.xml --user $branch_dn \
        --password $password

    For background information about SLEPOS branch server configuration, see https://www.suse.com/documentation/slepos11/book_slepos/data/cha_slepos_branchserv.html.

  4. Review the generated YAML file (retail.yml) and adjust it as necessary. Consider HWTYPE group naming and image name and version changes in the partitioning data. You can shorten the names as needed, and the image names must match the images in SUSE Manager. The --save-mapping option can help you with this task.

    Check whether there are duplicate MAC addresses of the terminals in the generated YAML file. Choose which entry you want to keep. As long as there are duplicate MAC addresses, SUSE Manager will refuse importing the YAML file.

    Note
    Note

    SUSE Linux Enterprise Point of Service images will not be migrated. You must rebuild the images using the OS image building functionality. For more information about building images, see https://www.suse.com/documentation/suse-manager-3/3.2/susemanager-advanced-topics/html/book.suma.advanced.topics/at.images.html#at.images.kiwi.

The data can be imported branch by branch. For each branch perform the following steps:

  1. Run the import command for one branch after the other:

    retail_yaml --from-yaml retail.yml --branch <branch_name>

    Repeat the command for every branch.

  2. To finalize each branch server migration, you must install the branch server machine as a Salt-based minion and bootstrap it as a proxy. For more information about proxy installation, see Installing and Registering. For more information about using an activation key to assign the required channels, see Configuring Server. After onboarded to SUSE Manager for Retail, the branch server machine is connected with the empty profile (by FQDN), and so it will get the Retail configuration.

  3. Apply Highstate on the branch server; this will happen automatically if Configuration File Deployment is enabled.

  4. Boot the terminals of the branch.

After all the branches are migrated, shut down and remove the old SLEPOS Admin Server.

3.1.3 Converting XML to YAML

When you perform a migration using one of the methods in this chapter, one of the steps takes the XML data dump file from SUSE Linux Enterprise Point of Service, and converts it to a YAML file for SUSE Manager for Retail. The tool that performs this conversion has additional features, which are outlined in this section.

To validate the XML file before conversion, and print any errors:

retail_migration dumpfile.xml

To write a mapping file called map.yml:

retail_migration dumpfile.xml  --save-mapping map.yml

The mapping file contains two dictionaries: . images, which maps old SUSE Linux Enterprise Point of Service images to new images built in SUSE Manager. . groups, which maps legacy SUSE Linux Enterprise Point of Service scCashRegister objects to SUSE Manager HWTYPE groups. Group names must not exceed the 56 character limit.

The mapping file should be edited as required for your environment.

To perform a conversion using a mapping file:

retail_migration dumpfile.xml  retail.yml --mapping map.yml

If you are performing a branch-by-branch migration, the resulting retail.yml file will contain a new version of SUSE Linux Enterprise Point of Service LDAP data. If you want to preserve any global changes in your {sme} settings, remove the global hardware types from the resulting retail.yml file before importing it. Alternatively, you can import retail.yml using this command to import only the new systems and groups defined in the file, and leave any existing configuration settings untouched:

retail_yaml --only-new

3.2 Migration from SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail with SUSE Manager Installed Independantly

Proceed as follows if you want to migrate an existing SLEPOS installation to SUSE Manager that was already installed independantly.

  1. Check the version number of the installed SUSE Manager. If needed migrate SUSE Manager to version 3.2.

  2. Check whether the Retail extension is already installed. If not, see SUSE Manager for Retail Installation and install the Retail extension.

  3. Continue as in Scenario 1, Step 2.

A GNU Licenses

This appendix contains the GNU Free Documentation License version 1.2.

4 GNU Free Documentation License

Copyright © 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 noncommercially. 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 in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or 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 fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

  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.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See 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{ldquo}GNU
   Free Documentation License{rdquo}.

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.

Print this page