SUSE Linux Enterprise Micro 5.0
Installation Quick Start #Edit source
SUSE Linux Enterprise Micro 5.0
Abstract#
This Quick Start guides you step-by-step through the installation of SUSE® Linux Enterprise Micro 5.0.
1 Welcome to SUSE Linux Enterprise Micro #Edit source
SUSE Linux Enterprise Micro is a modern system primarily designed for edge computing. The main features of SUSE Linux Enterprise Micro are predictability and reliability thanks to the read-only root file system and transactional updates. The read-only file system ensures that the system cannot be altered during runtime and that the system behaves the same way after each reboot. Transactional updates enable you to update the system without influencing the running system and always provide a rollback.
If you want to install SUSE Linux Enterprise Micro, you can choose any of the following installation procedures:
manual installation, see Section 3, “The manual installation procedure”
unattended automatic installation by using AutoYaST, see Section 4, “Unattended installation by using AutoYaST”
deployment of prebuilt images, see Section 5, “Raw image deployment”.
2 SUSE Linux Enterprise Micro hardware requirements #Edit source
SUSE Linux Enterprise Micro has the following minimum hardware requirements:
1 GB RAM
12 GB HDD.
The recommended hard disk space is 20 GB for SLE Micro itself and 40 GB for containers data. Bear in mind that actual hardware requirements depend on the workloads of your containers.
3 The manual installation procedure #Edit source
The following installation steps assume that you have successfully booted to the installation system.
3.1 The language and keyboard selection #Edit source
The default language and keyboard layout is English (US). You can choose a different language in the drop-down box. If necessary, select a different keyboard layout from the drop-down box.
Read the license agreement. The default language is English, but the licence agreement is available in multiple languages. To get a particular translation, click and in the drop-down box select the desired language and click . After you read the license agreement, check and click to proceed to the next installation step.
3.2 Registration #Edit source
In order to receive technical support and product updates, you need to register and activate your SUSE Linux Enterprise Micro with the SUSE Customer Center or a local registration server.
To register with the SUSE Customer Center, enter the associated with your SCC account and the for SUSE Linux Enterprise Micro. Proceed with .
If your organization provides a local registration server, you may alternatively register there. Activate and either choose a URL from the drop-down box or type in an address. Proceed with .
If you want to skip registration, click . Accept the warning with and proceed with .
Important: Skipping registration
Your system needs to be registered in order to retrieve updates and to be eligible for support. You can register later, after the installation.
After completing registration, click .
3.3 NTP servers configuration #Edit source
In order to keep time on your system properly synchronized, configure at least one NTP server.
3.4 Authentication for root #Edit source
Configure a strong password for root with at least 5
characters—a combination of uppercase and lowercase letters and
numbers. The maximum length for passwords is 72 characters, and passwords
are case-sensitive.
You can import an already existing SSH key by clicking and selecting the public SSH key.
Click to proceed to the next installation step.
3.5 Installation settings #Edit source
The last installation step provides a summary of installation setting. Review the settings and—if necessary—perform changes. To change a setting, click the button behind the option or click the setting headline for more options.
To modify partitions, you can use the . To encrypt your disk or to enable logical volume management, click and then fill in a password for the disk decryption.
Clicking opens the screen, where you can change the software selection by selecting or deselecting patterns. Each pattern contains several software packages needed for specific functions. To view and manage these packages, click .
By default, the time is synchronized by using the NTP servers you provided in the previous steps of the installation procedure, but you can select the region and time zone. If you want to set the time and date manually, click the button and select .
Displays the current network configuration. Click to change the settings.
This section shows the boot loader configuration. Changing the defaults is only recommended if really needed.
Kdump saves the memory image (“core dump”) to the file system in case the kernel crashes. This enables you to find the cause of the crash by debugging the dump file. Kdump is preconfigured and enabled by default.
Only the text mode is available.
View detailed hardware information by clicking . In the resulting screen you can also change .
The 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.
By default, the firewall is disabled. Click to change the default.
The SSH service is enabled by default. Click to change the setting. Bear in mind that if you disable the SSH service, you will not be able to login to your system remotely. The SSH port (22) is open by default.
The default SELinux option is . You can change the value by clicking and selecting another option in the menu.
If you reviewed the installation settings, you can proceed to installation by clicking and then confirming the installation.
4 Unattended installation by using AutoYaST #Edit source
SUSE Linux Enterprise Micro can be installed by using AutoYaST. You need to manually create an XML control file also called profile. AutoYaST then installs SLE Micro according to the instructions in the profile. For details, refer to Book “AutoYaST Guide”.
Important
Some of the resources and properties in the AutoYaST profile are by default applied in the second stage of the unattended installation, but the second stage is not available for SUSE Linux Enterprise Micro. Thus in order to apply all resources and properties, you need to disable the second stage in the AutoYaST profile:
<second_stage config:type="boolean">false</second_stage>
AutoYaST then applies all resources and properties in the first stage regardless of whether they are by default applied in the second stage.
5 Raw image deployment #Edit source
SUSE Linux Enterprise Micro provides raw images that can be directly deployed to your device storage—a memory card, USB flash drive, or a hard disk. The options for which type of device you can deploy the image to depend on your particular hardware—follow your vendor documentation.
To initially configure the deployed image, you need to prepare the configuration data as described in Procedure 2, “Preparing the configuration device.” and you need to copy the configuration data to a device (e.g. USB disk). The device needs to be connected to your host running SLE Micro during its first boot.
To prepare the setup, you need two separate devices. One for the raw disk image, where SLE Micro runs, and another one that serves as a configuration medium.
Procedure 1: Preparing the raw disk image #
Download the raw image and decompress it:
tux >xz -d <downloaded_image.raw.xz>Copy the decompressed image to the device where SLE Micro will run:
tux >dd if=<downloaded_image.raw> of=/dev/sdX
The following procedure describes how to prepare the configuration device (usually a USB flash disk).
Procedure 2: Preparing the configuration device. #
Format the disk to any file system supported by SLE Micro: Ext3, Ext4, etc.:
tux >sudo mkfs.ext4 /dev/sdYSet the device label to either
ignitionorcombustion. For the Ext4 file system:tux >sudo e2label /dev/sdY ignitionYou can use any type of configuration storage media that your virtualization system or your hardware supports—ISO image, a USB flash disk, etc.
Mount the device:
tux >sudo mount /dev/sdY /mntCreate the directory structure as mentioned in Section 5.1, “Configuration by using Ignition” or Section 5.2, “Configuration by using Combustion”, depending on the configuration tool used:
tux >sudo mkdir -p /mnt/ignition/or:
tux >sudo mkdir -p /mnt/combustion/Prior to booting for the first time, prepare all elements of the configuration that will be used by Ignition or Combustion. The minimal configuration must provide a password for
root, otherwise the system will not be accessible after the first boot.
After the first boot, you need to register your SUSE Linux Enterprise Micro instance by using the
command line tool SUSEConnect. For details, refer to
Section 5.3, “Registering with SUSEConnect”.
5.1 Configuration by using Ignition #Edit source
Ignition configures your system on the first boot according to the
config.ign configuration file. The
config.ign file must be placed in a directory named
ignition. The ignition directory
is a subdirectory of the root directory on the configuration medium labeled
ignition. The directory structure is then the following:
<root directory> - ignition - config.ign
Note: Using Ignition on a QEMU virtual machine
Ignition can be used to configure your QEMU virtual machine on the first
boot. To configure your virtual machine by using Ignition, use the QEMU
commnad line attribute fw_cfg to pass the location of
the config.ign to your virtual machine.
-fw_cfg name=opt/com.coreos/config,file=<path to config.ign>
The config.ign is in JSON format. A minimal example
follows:
{
"ignition": { "version": "3.1.0" },
"passwd": {
"users": [
{
"name": "root",
"passwordHash": "O9h4s2UUtAtok"
}
]
}
}
The example above sets a password for root to
password. To obtain your own password hash, use the
command:
root # openssl passwd5.2 Configuration by using Combustion #Edit source
Combustion is a minimal module for dracut. You can provide your script and Combustion runs the script on the first boot of the system. You can use Combustion to add files, install packages, set up devices, and repartition your disk. You can provide the configuration as a shell script on external storage. The script is executed during the boot process in a transactional update shell. If the process is successful, the system boots into the new snapshot.
To use Combustion on boot, create a directory named
combustion as a subdirectory of the root directory on
the configuration medium labeled ignition or
combustion. In the combustion
directory, place a file named script and any other
necessary files. The directory structure looks as follows:
<root directory> - combustion - script - other files
Note: Using Combustion on a QEMU virtual machine
Combustion searches for the script in
opt/org.opensuse.combustion/script. If the
script is present, Combustion creates the
combustion directory on the device and copies the
script to the directory.
To pass the script to your virtual machine, use the
following QEMU fw cfg parameter:
-fw_cfg name=opt/org.opensuse.combustion/script,file=/var/combustion-script
You can use Combustion together with Ignition. In this case, label your
device ignition, create also the
ignition subdirectory of the root directory, and place
the config.ign into the ignition
directory. The directory structure then looks as follows:
<root directory> -combustion - script - other files - ignition - config.ign
The following example of script sets a root
password, copies an SSH key (the SSH key must be located in the
combustion directory), and installs the
Vim editor with reduced features.
#!/bin/bash # combustion: network # Redirect output to the console exec > >(exec tee -a /dev/tty0) 2>&1 # Set a password for root, generate the hash with "openssl passwd -6" echo 'root:$5$.wn2BZHlEJ5R3B1C$TAHEchlU.h2tvfOpOki54NaHpGYKwdNhjaBuSpDotD7' | chpasswd -e # Add a public ssh key and enable sshd mkdir -pm700 /root/.ssh/ cat id_rsa_new.pub >> /root/.ssh/authorized_keys systemctl enable sshd.service # Install vim-small zypper --non-interactive install vim-small # Leave a marker echo "Configured with combustion" > /etc/issue.d/combustion
Note
The statement # combustion: network informs Combustion
that the network must be configured before the script is executed.
Combustion uses the initrd network
configuration—DHCP is used by default.
5.3 Registering with SUSEConnect #Edit source
Registering the system is possible from the command line using
SUSEConnect. For information that goes beyond the scope
of this section, refer to the inline documentation with
SUSEConnect --help
Procedure 3: Product registration with SUSEConnect #
To register SUSE Linux Enterprise Micro with SUSE Customer Center, run
SUSEConnectas follows:tux >sudo SUSEConnect -r REGISTRATION_CODE -e EMAIL_ADDRESSTo register with a local registration server, additionally provide the URL to the server:
tux >sudo SUSEConnect -r REGISTRATION_CODE -e EMAIL_ADDRESS \ --url "https://suse_register.example.com/"Replace REGISTRATION_CODE with the registration code you received with your copy of SUSE Linux Enterprise Micro. Replace EMAIL_ADDRESS with the e-mail address associated with the SUSE account you or your organization uses to manage subscriptions.
SUSE Linux Enterprise Micro is now registered.
6 Legal notice #Edit source
Copyright© 2006– 2022 SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”.
For SUSE trademarks, see https://www.suse.com/company/legal/. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.
All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors, nor the translators shall be held liable for possible errors or the consequences thereof.
7 GNU free documentation license #Edit source
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 #Edit source
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 #Edit source
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named sub-unit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
2. VERBATIM COPYING #Edit source
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 #Edit source
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 #Edit source
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
State on the Title page the name of the publisher of the Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
Include an unaltered copy of this License.
Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
5. COMBINING DOCUMENTS #Edit source
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 #Edit source
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 #Edit source
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 #Edit source
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 #Edit source
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 #Edit source
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 #Edit source
Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this:
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.