Suse linux enterprise server 12 sp3 �����

Release Notes #

These release notes are generic for all SUSE Linux Enterprise DesktopВ 12 SP3 based products. Some parts may not apply to particular architectures or products. Where this is not the case, the respective architecture is listed explicitly. General documentation can be found at: http://www.suse.com/documentation/sled-12/

Product to be released: September 2017

1 About the Release Notes #

The most recent version of these Release Notes is always available online at http://www.suse.com/releasenotes/.

Some entries may be listed twice, if they are important and belong to more than one section.

Release notes usually only list changes that happened between two subsequent releases. Always review all release notes documents that apply in your upgrade scenario.

2 SUSE Linux Enterprise Desktop #

SUSE Linux Enterprise Desktop is the market’s only enterprise-quality Linux desktop ready for routine business use. Developed and backed by SUSE, SUSE Linux Enterprise Desktop provides market-leading usability, seamless interoperability with existing IT systems, and dozens of essential applications—all at a fraction of the price of proprietary operating systems.

2.1 Interoperability and Hardware Support #

It comes bundled with the latest versions of leading applications such as LibreOffice office productivity suite, Mozilla Firefox web browser, and Evolution e-mail and calendar suite. In addition, it integrates with Microsoft SharePoint for group collaboration and supports a wide range of multimedia file formats, wireless and networking standards, and plug-and-play devices.

Through the latest enhancements in power management and security, SUSE Linux Enterprise Desktop also provides an environmentally friendly IT experience (GreenВ IT) and an error-proof desktop. Finally, SUSE Linux Enterprise Desktop offers unparalleled flexibility. You can deploy it on a wide range of thick client devices (including desktops, notebooks, netbooks, and workstations), on thin client devices, or as a virtual desktop. By leveraging the power of SUSE Linux Enterprise Desktop, your business can dramatically reduce costs, improve end user security and increase workforce productivity.

2.2 Support and Life Cycle #

SUSE Linux Enterprise Desktop 12 has a 7 year life cycle. The current version (SP3) will be fully maintained and supported until 6 months after the release of SUSE Linux Enterprise 12 SP4.

SUSE does not support skipping Service Packs of SUSE Linux Enterprise Desktop when upgrading.

2.3 What Is New? #

SUSE Linux Enterprise Desktop 12 introduces a number of innovative changes. Here are some of the highlights:

Robustness on administrative errors and improved management capabilities with full system rollback based on Btrfs as the default file system for the operating system partition and snapper technology from SUSE.

An overhaul of the installer introduces a new workflow that allows you to register your system and receive all available maintenance updates as part of the installation.

New core technologies like systemd, replacing the time honored System V based init process.

GNOME 3.20 gives users a modern desktop environment with a choice of several different look and feel options, including a special SUSE Linux Enterprise Classic mode for easier migration from earlier SUSE Linux Enterprise Desktop environments.

For users wishing to use the full range of productivity applications of a Desktop with SUSE Linux Enterprise Server, we are now offering the SUSE Linux Enterprise Workstation Extension

Integration with the new SUSE Customer Center, the central web portal from SUSE to manage subscriptions, entitlements, and provide access to support.

2.4 Documentation and Other Information #

2.4.1 Available on the Product Media #

Read the READMEs on the media.

Get the detailed changelog information about a particular package from the RPM ( FILENAME is the name of the RPM):

Check the ChangeLog file in the top level of the media for a chronological log of all changes made to the updated packages.

Find more information in the docu directory of the media of SUSE Linux Enterprise DesktopВ 12 SP3. This directory includes PDF versions of the SUSE Linux Enterprise DesktopВ 12 SP3 Installation Quick Start and Deployment Guides. Documentation (if installed) is available below the /usr/share/doc/ directory of an installed system.

2.4.2 Additional or Updated Documentation #

For SUSE Linux Enterprise Desktop 12 documentation, see http://www.suse.com/documentation/sled-12/, where you can download PDF documents. For installation with YaST software management or with zypper, packages are available on the product media. Some of these packages are installed by default. These are the package names:

sled-installquick_en-pdf : SLEDВ 12 SP3 Installation Quick Start

sled-gnomeuser_en-pdf : SLEDВ 12 SP3 GNOME User Guide

sled-admin_en-pdf : SLEDВ 12 SP3 Administration Guide

sled-deployment_en-pdf : SLEDВ 12 SP3 Deployment Guide

sled-security_en-pdf : SLEDВ 12 SP3 Security Guide

sled-tuning_en-pdf : SLEDВ 12 SP3 Tuning Guide

sled-manuals_en : the set of all SLED books in HTML format

2.5 How to Obtain Source Code #

This SUSE product includes materials licensed to SUSE under the GNU General Public License (GPL). The GPL requires SUSE to provide the source code that corresponds to the GPL-licensed material. The source code is available for download at http://www.suse.com/download-linux/source-code.html. Also, for up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code. Requests should be sent by e-mail to mailto:sle_source_request@suse.com or as otherwise instructed at http://www.suse.com/download-linux/source-code.html. SUSE may charge a reasonable fee to recover distribution costs.

2.6 Support Statement for SUSE Linux Enterprise Desktop #

2.7 Related Products #

This sections lists related products. In many cases, these products have own release notes documents that are available from https://www.suse.com/releasenotes/.

SUSE Linux Enterprise Server for SAP Applications: https://www.suse.com/products/sles-for-sap

Additionally, there are the following extensions which are not covered by SUSE support agreements, available at no additional cost and without an extra registration key:

SUSE Linux Enterprise Software Development Kit

3 Installation and Upgrade #

This section includes information related to the initial installation of SUSE Linux Enterprise Desktop 12 SP3. For information about installing, see Deployment Guide at https://www.suse.com/documentation/sled-12/book_sle_deployment/data/book_sle_deployment.html.

3.1 Update-Related Notes #

This section includes update-related information for SUSE Linux Enterprise Desktop 12 SP3. For information about general preparations and supported upgrade methods and paths, see the documentation at https://www.suse.com/documentation/sled-12/book_sle_deployment/data/cha_update_sle.html.

3.1.1 Online Migration: Checking the Status of Registered Products #

It is common that during the lifecycle of a system installation, registered extensions and modules are removed from the system without also deactivating them on the registration server.

To prevent errors and unexpected behavior during an online migration, the status of installed products needs to be checked before the migration to allow reinstalling or deactivating products.

A new step has been added to the current online migration workflow, it will check the registered products that are not currently installed in the system and allows:

Trying to install the products from the available repositories ( Install ).

Deactivating the products in SCC ( Deactivate ).

4 Systems Management #

4.1 System Clone AutoYaST XML Reflects Btrfs Snapshot State #

In previous versions of SLE 12, when using yast clone_system , AutoYaST would always enable snapshots for Btrfs Volumes, regardless of whether they were enabled on the original system.

Starting with SLE 12 SP3, yast clone_system will now create an AutoYaST XML file that accurately reflects snapshot state of Btrfs volumes.

4.2 «Register Extensions or Modules Again» Has Been Removed from YaST #

The button Register Extensions or Modules Again has been removed from the YaST registration module.

This option was redundant: It is still possible to register modules or extensions again with a different SCC account or using a different registration server (SCC or SMT).

Additionally, the option to filter out beta versions is now only visible if the server provides beta versions, otherwise the check box is hidden.

4.3 YaST: Default Auto-Refresh Status for Local Repositories Is «Off» #

In previous versions of SLE 12, when installing from a USB drive or external disk, the repository linking to the installation media was set to auto-refresh. This means that when the USB drive or the external disk had been removed and you are trying to work with YaST or Zypper, you were asked to insert the external medium again.

In the YaST version shipped with SLE 12 SP3, we have changed the default auto-refresh status for local repositories (USB drives, hard disks or dir:// ) to off which avoids checking the now usually unnecessary repository.

5 Miscellaneous #

5.1 IBus Input Switcher Settings Are Not Shared Between GNOME and IceWM #

When setting a key combination for switching between IBus input methods using ibus-setup , this setting will only be applied in IceWM but not in GNOME.

Under GNOME, use the GNOME Settings application to configure IBus:

To change input methods, start gnome-control-center and use the panel Region & Language .

To change the key combination to switch between input methods, start gnome-control-center and use the panel Keyboard . In it, choose the category Typing and the entry Switch to next input source .

Under IceWM, you can continue to use ibus-setup .

5.2 Qt 5 Now Supports Remote Print Queues #

Qt 5 can now list and print over CUPS network print queues. Unfortunately, this means that remote queues need to be looked up in the network, which takes time. The first time that printers are listed (usually when opening the print dialog for the first time), this adds a delay of up to 4 seconds.

If you do not have any network print servers and you do not want to use this feature, you can avoid the timeout. To do so, set the environment variable QT_DISABLE_PRINTER_DISCOVERY=1 before running your application.

5.3 GNOME: Support for Chinese, Japanese, Korean Installed and Configured Automatically #

When first logging in to GNOME on SLES 12 SP3 with the Workstation Extension or SLED 12 SP3, gnome-initial-setup will ask Chinese, Japanese, and Korean users for their preferred input method.

Because gnome-initial-setup is set up to run directly after the first login, it is also set up to not run before the GDM interface starts. This behavior is configured in the GDM configuration file /etc/gdm/custom.conf with the line InitialSetupEnable=False . Do not change this setting, otherwise a system without a normal user will not be able to provide the expected GDM log-in window.

6 Legal Notices #

SUSE makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.

Further, SUSE makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.

Источник

Краткое руководство по установке #

SUSE Linux Enterprise Server 12 с пакетом обновления 3

В этом руководстве приведены требования к системе, а также пошаговые инструкции по установке сервера SUSE Linux Enterprise Server с помощью DVD-диска или ISO-образа.

Далее приведены указания по установке новой версии SUSE® Linux Enterprise Server 12 с пакетом обновления 3 . В этом документе кратко описывается стандартная процедура установки SUSE Linux Enterprise Server на компьютерах с архитектурой AMD64 или Intel 64.

1 Вас приветствует сервер SUSE Linux Enterprise Server #

Более подробные указания по установке и стратегии развертывания см. в документации к серверу SUSE Linux Enterprise Server по ссылке http://www.suse.com/documentation/.

1.1 Минимальные требования к системе #

любой процессор AMD64/Intel* EM64T (32-разрядные процессоры не поддерживаются);

физическое ОЗУ с объемом памяти 512 МБ (рекомендуется 1 ГБ или более);

3,5 ГБ свободного места на диске (рекомендуется больше);

дисплей с разрешением 800 x 600 (рекомендуется 1024 x 768 или выше).

1.2 Установка сервера SUSE Linux Enterprise Server #

Следуйте этим указаниям, если система Linux не установлена на компьютере либо требуется заменить установленную ранее версию Linux.

Вставьте в дисковод DVD-диск SUSE Linux Enterprise Server и перезагрузите компьютер, чтобы запустить программу установки. На компьютере с обычной системой BIOS вы увидите графический экран загрузки, показанный ниже. На компьютерах с UEFI используется немного иной экран загрузки. На компьютерах с UEFI поддерживается безопасная загрузка.

Чтобы изменить язык установщика, используйте клавишу F2 . Соответствующая раскладка клавиатуры будет выбрана автоматически. Дополнительные сведения об изменении параметров загрузки: Book “ Deployment Guide”, Chapter 6 “Installation with YaST”, Section 6.2.2.1 “The Boot Screen on Machines Equipped with Traditional BIOS” или Book “ Deployment Guide”, Chapter 6 “Installation with YaST”, Section 6.2.2.2 “The Boot Screen on Machines Equipped with UEFI” .

На экране загрузки выберите Installation (Установка) и нажмите Enter . Это загрузит систему и запустит установщик сервера SUSE Linux Enterprise Server .

Параметры Language (Язык) и Keyboard Layout (Раскладка клавиатуры) будут запущены в соответствии с языковыми настройками, выбранными на экране загрузки. Если необходимо, их можно изменить здесь.

Прочтите лицензионное соглашение. Язык соглашения соответствует языку, выбранному на загрузочном экране. Доступны Переводы лицензии . Чтобы установить сервер SUSE Linux Enterprise Server , необходимо принять соглашение, отметив флажком пункт I Agree to the License Terms (Я согласен(-на) с лицензионным соглашением). Для продолжения нажмите кнопку Далее .

Будет проведен анализ системы. Установщик проверит устройства хранения данных и выполнит поиск других установленных систем. Если сеть нельзя настроить автоматически при запуске системы установки, откроется диалоговое окно Network Settings (Параметры сети).

После настройки как минимум одного сетевого интерфейса можно зарегистрировать систему в Центре по работе с клиентами SUSE. Введите адрес электронной почты, связанный с вашей учетной записью Центра по работе с клиентами SUSE, и код регистрации сервера SUSE Linux Enterprise Server . Успешная регистрация является необходимым условием для получения обновлений продукта и использования технической поддержки. Для продолжения нажмите кнопку Далее .

Подсказка: Установка исправлений продуктов во время установки

Если сервер SUSE Linux Enterprise Server успешно зарегистрирован в Центре по работе с клиентами SUSE, отобразится запрос установки последних доступных в Интернете обновлений в процессе установки. Если выбрать Да , система будет установлена с последними пакетами обновления и их не надо будет устанавливать впоследствии. Рекомендуется активировать этот параметр.

Примечание: Примечания к выпуску

С этого момента примечания к выпуску можно просмотреть в любом окне в процессе установки, выбрав элемент Release Notes (Примечания к выпуску).

После успешной регистрации системы средство установки YaST отобразит список модулей и расширений, доступных для сервера SUSE Linux Enterprise Server в Центре по работе с клиентами SUSE. Список содержит бесплатные модули, например SUSE Linux Enterprise SDK, а также расширения, для которых необходим платный регистрационный ключ. Щелкните элемент списка, чтобы посмотреть его описание. Кроме того, можно выбрать модуль или расширение для установки, установив соответствующую пометку. Для продолжения нажмите кнопку Далее .

Диалоговое окно Add-on Product (Дополнительный продукт) позволяет добавить дополнительные источники программного обеспечения (так называемые « репозитории » ) к серверу SUSE Linux Enterprise Server , которые не предоставляются Центром по работе с клиентами SUSE. Эти дополнительные продукты могут включать в себя продукты и драйверы сторонних производителей или дополнительное программное обеспечение для вашей системы.

Подсказка: Добавление драйверов во время установки

Можно также добавить репозитории обновления драйверов с помощью диалогового окна Add-On Products (Дополнительные продукты). Обновления драйверов для сервера SUSE Linux Enterprise расположены по ссылке http://drivers.suse.com/. Эти драйверы были созданы в рамках партнерской программы SUSE SolidDriver.

Чтобы пропустить этот шаг, нажмите кнопку Далее . В противном случае установите флажок I would like to Install an Add-on Product (Я хочу установить еще один дополнительный продукт). Укажите тип носителя, локальный путь или сетевой ресурс, на котором находится репозиторий, и следуйте инструкциям на экране.

Установите флажок Download Repository Description Files (Загрузить файлы описания хранилища), чтобы загрузить файлы с описанием репозитория. Если не активировать этот параметр, файлы будут загружены после начала установки. Чтобы продолжить, нажмите кнопку Далее и вставьте носитель (если он необходим). В зависимости от содержимого продукта, возможно, будет необходимо принять условия дополнительных лицензионных соглашений. Для продолжения нажмите кнопку Далее . Если вы выбрали дополнительный продукт, для которого необходим регистрационный ключ, необходимо будет ввести его на странице Extension and Module Registration Codes (Коды регистрации расширений и модулей).

Выберите подходящую вам системную роль в поле System Role (Системная роль). Выберите систему по умолчанию для физических машин и виртуальных гостей в поле Default System (Система по умолчанию). Для хоста виртуализации, на котором могут работать другие виртуальные машины, выберите пункт KVM Virtualization Host (Хост виртуализации KVM) или Xen Virtualization Host (Хост виртуализации Xen).

Проверьте настройку разделов, предлагаемую системой. При необходимости измените ее. Существуют следующие возможности:

Позволяет изменить параметры предложенных настроек, но не саму разметку разделов.

Create Partition Setup (Создать разметку)

Выберите диск, для которого будет применено предложение.

Expert Partitioner (Экспертный разделитель)

Откроется Экспертный разделитель . Подробнее о нем: Book “ Deployment Guide”, Chapter 11 “Advanced Disk Setup”, Section 11.1 “Using the YaST Partitioner” .

Чтобы принять предложенные настройки без изменений и продолжить, нажмите кнопку Далее .

Выберите часы и часовой пояс для использования в системе. Чтобы настроить время вручную или настроить NTP-сервер для синхронизации времени, выберите параметр Other Settings (Другие настройки). Дополнительные сведения: Book “ Deployment Guide”, Chapter 6 “Installation with YaST”, Section 6.12 “Clock and Time Zone” . Для продолжения нажмите кнопку Далее .

Чтобы создать локального пользователя, введите его имя и фамилию в поле User’s Full Name (Полное имя пользователя), имя пользователя в поле Username (Имя пользователя) и пароль в поле Password (Пароль).

Пароль должен состоять не менее чем из восьми символов, включая прописные и строчные буквы и цифры. Максимальная длина паролей составляет 72 символа, регистр символов учитывается.

В целях безопасности настоятельно рекомендуется не включать Automatic Login (Автоматический вход в систему). Не следует использовать параметр Use this Password for the System Administrator (Использовать этот пароль для системного администратора). Вместо этого создайте отдельный пароль учетной записи root на следующем шаге. Для продолжения нажмите кнопку Далее .

Введите пароль для учетной записи системного администратора (которого называют пользователем root ).

Пароль учетной записи root не следует забывать! После ввода этого пароля здесь извлечь его будет невозможно. Дополнительная информация: Book “ Deployment Guide”, Chapter 6 “Installation with YaST”, Section 6.14 “Password for the System Administrator root ” . Для продолжения нажмите кнопку Далее .

Проверьте и при необходимости исправьте предлагаемые параметры установки на экране Installation Settings (Настройки установки). Для каждого параметра указана текущая конфигурация. Чтобы изменить ее, щелкните заголовок. Некоторые параметры, например настройки брандмауэра или SSH, можно изменить, щелкнув соответствующую ссылку.

Подсказка: Удаленный доступ

Изменения, которые здесь можно внести, можно также сделать в любое время в уже установленной системе. Но если вам необходим удаленный доступ непосредственно после установки, следует настроить параметры Firewall and SSH (Брандмауэр и SSH) в соответствии с вашими нуждами.

По умолчанию в программное обеспечение включена базовая система и X Window с рабочим столом среды GNOME. Если щелкнуть элемент Software (Программное обеспечение), откроется экран Software Selection and System Tasks (Выбор программного обеспечения и системные задачи), где можно изменить выбор программного обеспечения, выбрав или отменив выбор шаблонов. Каждый шаблон содержит несколько пакетов программного обеспечения, необходимых для определенных функций (например, веб-сервер и LAMP-сервер или сервер печати). Чтобы ознакомиться с более широким выбором на основе пакетов программного обеспечения для установки, выберите элемент Details (Подробная информация) для перехода к Менеджеру программного обеспечения YaST. Дополнительная информация: Book “ Deployment Guide”, Chapter 12 “Installing or Removing Software” .

В этом разделе рассказывается о конфигурации загрузчика. Изменение настроек по умолчанию рекомендуется, только если это действительно необходимо. Дополнительная информация: Book “ Administration Guide”, Chapter 12 “The Boot Loader GRUB 2” .

Брандмауэр и SSH

По умолчанию брандмауэр включен, а активный сетевой интерфейс настроен на внешнюю зону. Дополнительная информация: Book “ Security Guide”, Chapter 15 “Masquerading and Firewalls”, Section 15.4 “SuSEFirewall2” .

Служба SSH по умолчанию выключена, а ее порт (22) закрыт. Поэтому вход с удаленного расположения по умолчанию невозможен. Чтобы изменить эти параметры, выберите команду включить и открыть .

Kdump сохраняет образ памяти ( « дамп памяти » ) в файловую систему на случай аварийного отказа ядра. Это позволяет вам узнать причину аварийного отказа, выполнив отладку файла дампа. Kdump предварительно настроен и включен по умолчанию. Дополнительная информация: Book “ System Analysis and Tuning Guide”, Chapter 17 “Kexec and Kdump”, Section 17.7 “Basic Kdump Configuration” .

Назначение systemd, используемое по умолчанию

По умолчанию система загружается в графический целевой объект с поддержкой сети, нескольких пользователей и менеджером дисплея. Переключитесь в многопользовательский режим, если нет необходимости выполнять вход через менеджер дисплея.

Чтобы просмотреть подробную информацию об оборудовании, щелкните элемент Система . В открывшемся окне можно также изменить Kernel Settings (Параметры ядра). Дополнительная информация: Book “ Deployment Guide”, Chapter 6 “Installation with YaST”, Section 6.15.8 “ System Information ” .

После окончательной настройки конфигурации системы на экране Installation Settings (Настройки установки) нажмите кнопку Install (Установить). В зависимости от выбора программного обеспечения, возможно, вам понадобится принять условия лицензионного соглашения перед тем, как появится экран подтверждения установки. До этого момента в системе не было сделано изменений. После повторного нажатия кнопки Install (Установить) запустится процесс установки.

Во время установки на экране Details (Подробная информация) отображается ход ее выполнения.

После завершения установки компьютер будет перезагружен, загрузится установленная система. Выполните вход и запустите средство установки YaST, чтобы настроить систему. Если вы не используете графический интерфейс рабочего стола или работаете с удаленного расположения, см. информацию об использовании средства установки YaST с терминала: Book “ Administration Guide”, Chapter 5 “YaST in Text Mode” .

2 Уведомление #

© SUSE LLC и другие участники, 2006– 2021 . Все права защищены.

Разрешение на копирование, распространение и (или) изменение данного документа предоставляется только в соответствии с условиями лицензии GNU Free Documentation License (версии 1.2 или — по вашему выбору — версии 1.3). При этом содержимым неизменяемого раздела лицензии являются данное уведомление об авторских правах и лицензия. Копия лицензии версии 1.2 включена в раздел « GNU Free Documentation License » .

Информацию о товарных знаках SUSE см. в разделе http://www.suse.com/company/legal/. Товарные знаки других поставщиков являются собственностью соответствующих владельцев. Символы ®, ™ и т. д. означают товарные знаки, принадлежащие компании SUSE и ее дочерним компаниям. Символ * означает товарные знаки других поставщиков.

При сборе информации, содержащейся в данной книге, особенное внимание уделялось деталям. Однако это не гарантирует абсолютной точности. Компания SUSE LLC, ее филиалы, авторы и переводчики не несут ответственности за возможные ошибки или их последствия.

3 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 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 non-commercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

3. COPYING IN QUANTITY #

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to 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:

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 #

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 #

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with. Texts.” line with this:

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.

Источник