UYUNI Common Workflows User Guide

UYUNI Common Workflows

Prefazju

Kapitolu 1

Flussi tax-Xogħol Komuni

Uyuni 2026.04

The Uyuni Common Workflows Guide provides step-by-step instructions for the most frequently used workflows to install, manage, and configure clients with Uyuni.

Each workflow in this guide has a clear objective and includes detailed steps to help you achieve it efficiently.

Designed for both routine and advanced tasks, this guide not only explains the actions you take but also highlights the available options at each stage.

Throughout this guide, each routine task is referred to as a Workflow.

Data tal-Pubblikazzjoni: 2026-04-29

Klijent Onboarding

Kapitolu 2

Uyuni is all about managing client systems. So one of the first things you need to do is onboard some clients.
This workflow shows you how to set up your Uyuni Server to manage a new client, set up the software channels you need, and bootstrap the client using an activation key.

Każ ta' Użu

Dan il-fluss tax-xogħol jurik kif tqabbad klijent fis-Server Uyuni tiegħek.

Il-klijent irid ikun qed iħaddem sistema operattiva Linux appoġġjata. Għal lista ta' sistemi ta' klijenti appoġġjati, ara Client-configuration › Supported-features.

Din hija waħda mill-ewwel kompiti li trid tagħmel meta twaqqaf Uyuni għall-ewwel darba, u probabilment ikollok tagħmel dan ħafna aktar drabi hekk kif tuża l-prodott.

Riżultat

When you have completed this workflow, your client is on boarded, and it can be seen in the systems list of the Uyuni Web UI. Imbagħad tista 'tuża Uyuni biex tmexxi l-klijent.

Preparazzjoni

Qabel ma tibda, diġà għandu jkollok:

• Uyuni Server installat, li inti tista 'aċċess bl-użu Web UI
• Magna Klijent b'sistema operattiva installata, li tista' taċċessaha fuq in-netwerk li jinsab fuq is-Server Uyuni tiegħek, billi tuża SSH.
• Abbonamenti xierqa minn http://scc.suse.com għall-prodotti li qed tuża.

This workflow uses a SUSE Linux Enterprise Server 15 SP2 operating system. You can use other Linux operating systems, but some of the steps might be different. For more information on onboarding other clients, see Client-configuration › Registration-methods.

Istruzzjonijiet tal-fluss tax-xogħol pass pass

Proċedura: Configure a Fully Qualified Domain Name (FQDN) on Your Client

1. Fuq il-klijent, fil-pront tal-kmand, uri l-isem tal-host attwali:
   hostname -f
   Dan il-kmand probabbilment se jirritorna żball, jew juri xi ħaġa bħal localhost.
2. Issettja hostname ġdid. L-isem tal-host il-ġdid tiegħek għandu jkollu isem ta' sottodominju u għalhekk jinkludi mill-inqas żewġ perjodi. F'dan example, we are using client1.MLM.example
   hostnamectl set-hostname client1.MLM.example
3. Iċċekkja li l-bidla tiegħek kienet ta' suċċess:
   hostnamectl
4. Open YaST and navigate to Network Services › Hostnames. Edit the hostname to match the one you just
   set, and click [KOLLOX SEW].
5. In YaST, navigate to System › Network Settings and go to the Hostname/DNS tab. In the Static hostname field, type your new hostname.
6. Iċċekkja li l-bidla kienet ta’ suċċess:
   hostname -f
   This command should return your new FQDN

Proċedura: Ipprepara Kanali tas-Software fuq is-Server Uyuni

1. Fil-Uyuni Web UI, innaviga lejn Admin › Setup Wizard.
2. Fit-tab tal-Kredenzjali tal-Organizzazzjoni, kun żgur li daħħalt il-kredenzjali tiegħek taċ-Ċentru tal-Klijent SUSE, u li tkun awtentikata b'mod korrett.
3. Fit-tab Prodotti, kun żgur li l-katalgu tal-prodott huwa kompletament aġġornat:
4. Use the product search bar to find the channels you need for your client operating system. Check the channels you want to install, and click [Żid il-prodotti ]:
5. Stenna li l-kanali tal-prodott jissinkronizzaw bis-sħiħ. Skont il-prodotti li għażilt, dan jista 'jieħu żmien twil.

Proċedura: Oħloq Ċavetta ta' Attivazzjoni

1. Fil-Uyuni Web UI, innaviga lejn Sistemi › Activation Keys, u kklikkja [Create Key].
2. Give your activation key a name, and select the base channel that matches the client you want to onboard.
   This should be the product you just enabled:
3. Check the child channels to include, and any add-on system types you want clients registered with this key to have. Click [Oħloq Ċavetta ta 'Attivazzjoni].

Proċedura: Ibbutja l-Klijent

1. Fil-Uyuni Web UI, innaviga lejn Systems › Bootstrapping.
2. Ittajpja l-isem tal-host u ipprovdi kredenzjali ta' awtentikazzjoni għall-klijent li trid tiddaħħal abbord, u agħżel iċ-ċavetta tal-attivazzjoni. Ikklikkja [Bootstrap]:
3. Innaviga lejn Systems › System List to manage your new client

Suġġetti Relatati

• For more information about supported clients and client features, see Client-configuration › Supported features.
• For more information about different onboarding methods, and instructions for clients running various operating systems, see Client-configuration › Registration-methods.
• For more information about general client concepts, see Client-configuration › Channels.

Aġġornament tal-Klijenti Użu Azzjonijiet Rikorrenti

Kapitolu 3

Dan il-fluss tax-xogħol juri kif awtomat l-aġġornament tal-klijenti rreġistrati f'Uyuni billi juża azzjonijiet rikorrenti.

Use case / Situation

L-aġġornament awtomatizzat tal-klijenti huwa ta' benefiċċju meta:

• aġġornament ta 'numru kbir ta' klijenti huwa mfittex
• il-fluss tax-xogħol m'għandux jerġa' jsir kull eżekuzzjoni
• teżisti tieqa ta' manutenzjoni apposta.

Riżultat / Riżoluzzjoni

It-tlestija b'suċċess ta 'dan il-fluss tax-xogħol jirriżulta fi stat konsistenti u appoġġabbli.

Preparazzjoni

Before you start, you should have a number of clients on boarded. It may make sense to have them sorted into groups you want to update together. In this workflow we use a system group named infra-services.

Step-by-Step workflow instructions

Biex taġġorna klijent huma meħtieġa żewġ passi. It-tielet pass huwa fakultattiv iżda rakkomandat ħafna biex jiġi ffinalizzat il-proċess ta 'aġġornament.

Proċedura: Creating a recurring action to update Salt itself

1. Bħala example, noħolqu l-azzjoni biex taġġorna Salt innifsu bħala azzjoni rikorrenti għas-sistemi kollha fl-organizzazzjoni. Fil-Uyuni Web UI, innaviga lejn Home › My Organization › Recurring Actions u kklikkja [Create].
2. Select Action Type Custom Stat and enter a Schedule Name like update salt .
3. Agħżel skeda. Per example, Weekly: Wednesday, 9:00 am .
4. Assenja l-istat tal-aġġornament-melħ billi tagħżel il-kaxxa tal-kontroll.
5. Ikklikkja [Save Changes ] to save the action.
6. You can edit the execution order of the states if needed. Click [Ikkonferma] to confirm the order.
7. Ikklikkja [Create Schedule] to save the action.

Proċedura: Creating a recurring action to apply all available updates to the systems

1. Bħala example we create the action to apply all updates as a recurring action for a system group called infra-servizzi. Fil-Uyuni Web UI go to Systems › System Groups and click on infra-services.
2. Now go to Recurring Actions and click [Create].
3. Select Action Type Custom State and enter a Schedule Name like full system-update.
4. Agħżel Skeda. Per example, Weekly: Wednesday, 9:30 am . Keep enough time between this action and the update-salt action. The update salt actions must be finished on all systems before this action should be executed.
5. Assign the states util. syn call, certs, channels and up-to-date by selecting the checkboxes. To perform a reboot afterwards you can also add reboot or reboot if needed.
6. Save the action by clicking [Ħlief Bidliet ].
7. You can edit the execution order of the states. The order should be util. syn call, certs, channels, up-to-date and finally reboot or reboot if needed if chosen. Click [Ikkonferma] to store the order.
8. Ikklikkja [Create Schedule] to save the action.

Proċedura: Creating a recurring action to run a high state after the update

1. Bħala example, we create the action to apply the high state for the same group which was fully updated before. In the Uyuni Web UI, innaviga lejn Systems › System Groups and click infra-services.
2. Go to Recurring Actions and click [Create].
3. Select Action Type Stat għoli and enter a Schedule Name like high state .
4. Agħżel Skeda. Per example, Weekly: Wednesday, 10:30 am . Again, keep enough time between this action and the full-system-update action.
5. Ikklikkja [Create Schedule] to save the action.

Background information on up-to-date state

1. Il- up-to-date state applies critical patches to the update components.
   • a. On SUSE-based systems, the state executes the command:
     zypper --non-interactive patch --updatestack-only
     And then, the state also updates Salt.
   • b. On all the other systems, not based on SUSE, the state only updates Salt.
2. The state runs the package manager, such as dnf, yum, apt, or zypper based on what is available on the client operating system to update the rest of the packages.
   • a. The state lists all of the upgradable packages, based on the synchronized package repositories in Uyuni.
   • b. The state upgrades the packages to their latest available version by using the client’s package manager. The executed command depends on the operating system of the client:
     • i. For Debian-based clients, such as Debian or Ubuntu, the action executes apt dist-upgrade -q -y $PACKAGES.
     • ii. For RPM-based clients that are not SUSE, such as Red Hat Enterprise Linux or SUSE Liberty Linux, the action executes yum –quiet -y update $PACKAGES or dnf –quiet -y upgrade $PACKAGES (depending on the package manager the client is using).
     • iii. For non-transactional SUSE clients, such as SUSE Linux Enterprise 15, the action executes zypper –non-interactive –auto-agree-with-licenses update $PACKAGES.
     • iv. For transactional SUSE clients, the action executes the same in a transactional shell.
3. Uyuni provides the reboot and reboot if needed actions. Use one of the actions if you want your client to reboot after the package upgrade.
   Reboot detection is specific to the client operating system.
   • For Debian or Ubuntu, see https://www.debian.org/doc/debian-policy/ch-opersys.html#signaling-that-a-reboot-is-required.
   • For non-transactional SUSE clients, Uyuni reboots the client when zypper -x list-patches indicates that the patches require a reboot.
   • For transactional SUSE clients, Uyuni reboots the client if there is a pending transaction.
   • For the Red Hat-based clients, Uyuni reboots the client if dnf -q needs-restarting -r indicates that a reboot is required.

For more information, see the reboot_info.py module: https://github.com/uyuni-project/uyuni/blob/master/susemanager-utils/susemanager-sls/src/modules/reboot_info.py

Suġġetti relatati

• For more information about recurring actions, see Recurring Actions.
• For more information about custom info values, see Client-configuration › Custom-info.

Ġestjoni tal-Konfigurazzjoni

Kapitolu 4

Tista' tuża l-konfigurazzjoni files u kanali biex timmaniġġja l-konfigurazzjoni għall-klijenti tiegħek, aktar milli tikkonfigura kull klijent manwalment. Dan il-fluss tax-xogħol jurik kif tuża l-Uyuni Web UI biex toħloq konfigurazzjoni ġestita ċentralment file, tassenjaha lil klijent, u applika l-konfigurazzjoni.

Każ ta' Użu

Jekk qed timmaniġġja ħafna klijenti, probabbilment ma tridx tapplika manwalment is-settings tal-konfigurazzjoni għal kull wieħed minnhom imbagħad. Il-kanali tal-konfigurazzjoni jintużaw biex tiġi organizzata l-konfigurazzjoni files. Tista 'tabbona klijenti għal kanali ta' konfigurazzjoni, u tuża konfigurazzjoni files kif meħtieġ.

Riżultat

Meta tkun lestejt dan il-fluss tax-xogħol, ser ikollok kanal ta' konfigurazzjoni li jkun fih konfigurazzjoni file, assenjaw klijenti lill-kanal, u applikaw il-konfigurazzjoni b'suċċess.

Preparazzjoni

Qabel ma tibda, diġà għandu jkollok:

• Uyuni Server installat, li inti tista 'aċċess bl-użu Web UI
• Mill-inqas klijent wieħed irreġistrat mas-server tiegħek.
• Abbonamenti xierqa minn http://scc.suse.com għall-prodotti li qed tuża.

Dan il-fluss tax-xogħol juża konfigurazzjoni ġestita ċentralment file and a Salt state. For more information about the different ways to manage configuration, see Client-configuration › Configuration-management.

Istruzzjonijiet tal-fluss tax-xogħol pass pass

Proċedura: Oħloq Kanal ta' Konfigurazzjoni Ġdid u File

1. Fil-Uyuni Web UI, innaviga lejn Configuration › Channels u kklikkja [Create State Channel].
2. Ittajpja isem, tikketta u deskrizzjoni għall-konfigurazzjoni tiegħek file, u ittajpja l-kontenut tal-konfigurazzjoni tiegħek file. Example that you can copy is at the end of this section.

Proċedura: Assenja Klijenti lill-Kanal tal-Konfigurazzjoni

1. Fil-Uyuni Web UI, innaviga lejn Systems › Systems List and select the client you want to assign to your configuration channel.
2. Innaviga fit-tab Konfigurazzjoni. Fil-guimenu: Konfigurazzjoni Overview sezzjoni, ikklikkja [Subscribe to channels ].
3. Check the configuration channel you created earlier, and click [Continue].
4. If you have more than one configuration channel, you can rank them in order of importance, or click [Update Channel Rankings ] biex jintemm.

Proċedura: Applika l-Konfigurazzjoni għall-Klijent Tiegħek

1. Fil-Uyuni Web UI, innaviga lejn Systems › Systems List and select the client you want to assign to your configuration channel.
2. Navigate to the Configuration tab. In the guimenu: Configuration Actions section, click [Deploy all managed config files ]

Example

L-Istat SLS għaż-Żamma Aġġornata tal-Klijenti

include:
- channels
int_keep_system_up2date_updatestack:
pkg.latest:
- pkgs:
- salt
- salt-minion
{%- if grains.os_family == 'Suse'%}
- zypper
- libzypp
{%- elif grains['os_family'] == 'RedHat' %}
{%- if grains['osmajorrelease'] >= 8 %}
- dnf
{%- else %}
- yum
{%- endif %}
{%- endif %}
- require:
- sls: channels
- order: last
int_keep_system_up2date_pkgs:
pkg.up-to-date :

- require:
- sls: channels
- pkg: int_keep_system_up2date_updatestack
- order: last
int_reboot_if_needed:
cmd.run:
- name: shutdown -r +5
{%- if grains['os_family'] == 'RedHat' and grains['osmajorrelease'] >= 8 %}
- onlyif: 'dnf -q needs-restarting -r; [ $? -eq 1 ]'
{%- elif grains['os_family'] == 'RedHat' and grains['osmajorrelease'] <= 7 %}
- onlyif: 'needs-restarting -r; [ $? -eq 1 ]'
{%- elif grains['os_family'] == 'Debian' %}
- onlyif:
- test -e /var/run/reboot-required
{%- else %}
- onlyif: 'zypper ps -s; [ $? -eq 102 ]'
{%- endif %}

Suġġetti Relatati

• For more information about configuration management, see Client-configuration › Configuration management.
• Għal aktar informazzjoni dwar SLS files, ara: https://docs.saltproject.io/en/latest/topics/tutorials/starting_states.html.

Ġestjoni taċ-ċiklu tal-ħajja tal-kontenut

Kapitolu 5

Jekk qed timmaniġġja ħafna klijenti u għandek bżonn tapplika pakketti personalizzati għalihom, tista' tuża l-ġestjoni taċ-ċiklu tal-ħajja tal-kontenut (CLM) biex timmaniġġja l-pakketti tiegħek. CLM jippermettilek tippersonalizza u tittestja pakketti qabel taġġorna l-klijenti tal-produzzjoni. Huwa utli wkoll jekk ikollok bżonn tapplika aġġornamenti waqt tieqa ta 'manutenzjoni limitata.

Każ ta' Użu

Il-ġestjoni taċ-ċiklu tal-ħajja tal-kontenut tippermettilek tagħżel kanali tas-softwer bħala sorsi, taġġustahom kif meħtieġ għall-ambjent tiegħek, u tittestjahom bir-reqqa qabel ma tinstalla fuq il-klijenti tal-produzzjoni tiegħek. Tista 'tuża CLM biex timmaniġġja l-kanali tas-software tiegħek mill-iżvilupp, permezz tal-ittestjar, u tgħaddi l-bidliet lill-klijenti tiegħek.

Riżultat

Meta tkun lestejt dan il-fluss tax-xogħol, ser ikollok stabbilit proġett taċ-ċiklu tal-ħajja tal-kontenut. Int tkun ħoloq proġett CLM bażiku, u ppromwovjewh matul iċ-ċiklu tal-ħajja tiegħu.

Preparazzjonijiet

Qabel ma tibda, diġà għandu jkollok:

• Uyuni Server deployed, and accessible using the Web UI
• Magna Klijent b'sistema operattiva installata, li tista' taċċessaha fuq in-netwerk li jinsab fuq is-Server Uyuni tiegħek, billi tuża SSH.
• Abbonamenti xierqa minn http://scc.suse.com għall-prodotti li qed tuża.

Istruzzjonijiet tal-fluss tax-xogħol pass pass

Proċedura: Oħloq Proġett CLM ġdid

1. Fil-Uyuni Web UI, innaviga lejn Content Lifecycle › Projects section, and click [Create Project].
   Type a name, label, and description for your project, and click [Create].
2. In the Sources section, click [Attach/Detach Sources ].
   Select the source type, and select a base channel for your project.
   The available child channels for the selected base channel are displayed, including information on whether the channel is mandatory or recommended. Check the child channels you require, and click [Issejvja] to return to the project page.
3. Ħalli s-sezzjoni tal-Filtri vojta għalissa, mhux se nkunu qed nużawhom f'dan l-eżample. Tista 'żżid filtri aktar tard jekk ikollok bżonn.
4. In the Environment Lifecycle section, create three environments: production, testing, and development. Click [Add Environment] and complete the name and label for each.
   For the production environment, leave the Insert before field blank.
   For the testing environment, in the Insert before field, select production.
   For the development environment, in the Insert before field, select testing.
5. Ikklikkja [Ibni] to build version 1 of your project:

Proċedura: Assenja Klijenti

1. Innaviga lejn Systems › System List, select the client to assign, and go to the Software › Software Channels tab.
2. In the Base Channel section, select the CLM project and environment you want to assign the client to.
   Per example, if you want this client to receive updates from your CLM only when packages are in the production environment, assign the base channel < CLM _ Project _ Name> – production-<Channel _ Name >
   Alternatively, you could use this client as a way to test if your CLM packages are working as expected before you promote them to development, so you assign the base channel < CLM _ Project _ Name> – testing – <Channel _ Name >.
3. Ikklikkja [Li jmiss] to assign the client.

Proċedura: Tippromwovi Ambjenti

1. Fil-Uyuni Web UI, innaviga lejn Content Lifecycle › Projects, and select the project you want to work with.
2. In the Environment Lifecycle section, locate the environment to promote to its successor, and click [Promote]. You can monitor build progress in the Environment Lifecycle section.

Suġġetti Relatati

• For more information about CLM, including information about how to use filters, see Administration › Content-lifecycle.
• Għal CLM examples, ara Administration › Content-lifecycle-examples.

Customize Apache Configuration

Kapitolu 6.

This workflow shows you how to add custom configuration to Uyuni components, specifically the Apache HTTP server, within a containerized environment. It ensures that your custom configurations are stored in a persisted volume and are not overwritten during image updates.

Każ ta' użu

This workflow is beneficial when:

• You need to overwrite or extend the default Apache configuration.
• You need to ensure that configuration changes persist after a container image update.
• You want to add specific tuning configurations to the server.

Riżultat

After completing this workflow, your custom Apache configuration will be active and will persist through future updates or restarts of the Uyuni containers.

Preparazzjoni

Before you start, you should have:

• Root access to the Uyuni Server host.
• Knowledge of the specific Apache directives you wish to apply.

Step-by-step workflow instructions

You should only add new configuration files, and not modify the existing configuration files provided by the image.

Procedure: Adding custom Apache configuration files

1. Open a terminal on your Uyuni Server.
2. Access the server container shell by running the following command:
   mgrctl term
3. Navigate to the configuration directory. You must create your new configuration file in the path /etc/apache2/conf. d, as this folder is persisted.
4. Create your new configuration file (eżample, custom_ tuning. conf) and add your required Apache directives.
5. Ladarba tkun salvajt tiegħek file, exit the container with command:
   exit
6. Restart the Uyuni services to apply the changes:
   mgradm restart

Aġġornament tal-Prodott permezz Web UI

Kapitolu 7

Jekk trid taġġorna l-pakkett tal-klijenti reġistrat SUSE Linux Enterprise għal verżjoni tal-prodott aktar ġdida, jista 'jsir jew fuq il-linja tal-kmand jew permezz Web UI

Dan id-dokument jiddeskrivi u juri fid-dettall l-aġġornament tal-prodott bl-użu tal- Web UI

Il-verżjonijiet tal-prodott użati ma jirriflettux l-aħħar verżjonijiet attwali disponibbli. Jintużaw għal skopijiet ta' illustrazzjoni biss. Bħala example, il-proċedura li ġejja tiddeskrivi l-aġġornament għall-verżjoni 15 SP5 minn u verżjoni eqdem 15. Jekk qed timmira verżjoni differenti, agħżel il-kanali u l-verżjonijiet korrispondenti.

Proċedura: Aġġornament tal-Prodott għal Verżjoni Aktar Ġdida Bl-użu Web UI

1. Idħol f'Uyuni Web UI and navigate to Admin › Setup Wizard › Products and search for SUSE Linux Enterprise Server 15 SP5 x86_64.
2. Agħżel il-kanali rakkomandati.
3. Ikklikkja [Add Products ].
4. Innaviga lejn Systems › Registered client › Software › Product Migration. You will see the targets available for that registered client.
5. Agħżel SUSE Linux Enterprise Server 15 SP5 x86_64. Dan se jespandi aktar.
6. Agħżel Target Base Channel bħala SLE-Product-SLES15-SP5-Pool għal x86_64. Żomm Ħalli Tibdil Bejjiegħa mhux ikkontrollat.
7. Ikklikkja [Schedule Migration]. The message will be highlighted It is better to do a dry run first so continuing with dry run first.
8. Ikklikkja [Tiġi niexfa] and check the status of the simulation in Events › History. You should see a return code 0 indicating a successful dry run.
9. Ikklikkja [Schedule Migration] to perform the actual product migration. The message will be highlighted on top of the screen indicating the scheduling of the action.
10. When the upgrade is complete, check the status in Events › History.
11. Fuq l-Uyuni Web UI side, verify the successfully completed product upgrade by going to Systems › Registered client › Details.
12. Fuq in-naħa tal-klijent tista' tivverifikaha billi tmexxi:
    cat /etc/os-release
13. L-output se jidher simili għal:

NAME="SLES"
VERSION="15-SP5"
VERSION_ID="15.5"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp5"
DOCUMENTATION_URL="https://documentation.suse.com/"

Liċenzja tad-Dokumentazzjoni Ħieles GNU

Kapitolu 8

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.

PREAMBLU

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 “copy left”, 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 copy left license designed for free software.

Iddisinjajna din il-Liċenzja sabiex nużawha għal manwali għal softwer b'xejn, għax is-softwer b'xejn jeħtieġ dokumentazzjoni b'xejn: programm b'xejn għandu jiġi b'manwali li jipprovdu l-istess libertajiet li jagħmel is-softwer. Iżda din il-Liċenzja mhix limitata għal manwali tas-softwer; jista' jintuża għal kwalunkwe xogħol testwali, irrispettivament mis-suġġett jew jekk huwiex ippubblikat bħala ktieb stampat. Nirrakkomandaw din il-Liċenzja prinċipalment għal xogħlijiet li l-iskop tagħhom huwa struzzjoni jew referenza.

APPLIKABILITÀ U DEFINIZZJONIJIET

Din il-Liċenzja tapplika għal kull manwal jew xogħol ieħor, fi kwalunkwe mezz, li jkun fih avviż imqiegħed mid-detentur tad-drittijiet tal-awtur li jgħid li jista’ jitqassam taħt it-termini ta’ din il-Liċenzja. Avviż bħal dan jagħti liċenzja dinjija bla royalties, bla limitu fit-tul, biex jintuża dak ix-xogħol taħt il-kundizzjonijiet imsemmija hawnhekk. Id-“Dokument”, hawn taħt, jirreferi għal kwalunkwe manwal jew xogħol bħal dan. Kwalunkwe membru tal-pubbliku huwa liċenzjat, u huwa indirizzat bħala "int". Taċċetta l-liċenzja jekk tikkopja, timmodifika jew tqassam ix-xogħol b'mod li jeħtieġ permess taħt il-liġi tad-drittijiet tal-awtur.

“Verżjoni Modifikata” tad-Dokument tfisser kwalunkwe xogħol li jkun fih id-Dokument jew porzjon minnu, jew ikkupjat verbatim, jew b’modifiki u/jew tradott f’lingwa oħra.

“Taqsima Sekondarja” hija appendiċi msemmi jew taqsima ta’ quddiem tad-Dokument li tittratta esklussivament mar-relazzjoni tal-pubblikaturi jew l-awturi tad-Dokument mas-suġġett ġenerali tad-Dokument (jew materji relatati) u ma fih xejn li jista’ jaqa’ direttament fi ħdan dak is-suġġett ġenerali. (Għalhekk, jekk id-Dokument huwa parzjalment ktieb tal-matematika, Taqsima Sekondarja tista’ ma tispjega l-ebda matematika.) Ir-relazzjoni tista’ tkun kwistjoni ta’ konnessjoni storika mas-suġġett jew ma’ kwistjonijiet relatati, jew ta’ liġi, kummerċjali, filosofika, etika jew pożizzjoni politika dwarhom.

It-“Taqsimiet Invarjanti” huma ċerti Sezzjonijiet Sekondarji li t-titli tagħhom huma indikati, bħala dawk ta’ Sezzjonijiet Invarjanti, fl-avviż li jgħid li d-Dokument jinħareġ taħt din il-Liċenzja. Jekk taqsima ma taqbilx mad-definizzjoni ta' hawn fuq ta' Sekondarja allura mhux permess li tiġi indikata bħala Invarjanti. Id-Dokument jista' jkun fih żero Sezzjonijiet Invarjanti. Jekk id-Dokument ma jidentifika l-ebda Sezzjoni Invarjanti allura m'hemm l-ebda.

It-"Testi ta' Qoxra" huma ċerti siltiet qosra ta' test li huma elenkati, bħala Testi ta' Qoxra ta' Quddiem jew Testi ta' Kopertura ta' wara, fl-avviż li jgħid li d-Dokument huwa rilaxxat taħt din il-Liċenzja. Test fuq il-qoxra ta' quddiem jista' jkun ta' mhux aktar minn 5 kelmiet, u Test fuq il-qoxra ta' wara jista' jkun ta' mhux aktar minn 25 kelma.

Kopja “Trasparenti” tad-Dokument tfisser kopja li tinqara mill-magni, rappreżentata f’format li l-ispeċifikazzjoni tagħha hija disponibbli għall-pubbliku ġenerali, li hija adattata biex tirrevedi d-dokument b’mod sempliċi b’edituri ta’ test ġeneriċi jew (għall-immaġini komposti minn pixels) żebgħa ġenerika programmi jew (għal tpinġijiet) xi editur tat-tpinġija disponibbli b'mod wiesa ', u li huwa adattat għall-input għall-formatters tat-test jew għat-traduzzjoni awtomatika għal varjetà ta' formati adattati għall-input għall-formatters tat-test. Kopja magħmula b'mod ieħor Trasparenti file format li l-markup tiegħu, jew in-nuqqas ta' markup, ġie rranġat biex ifixkel jew jiskoraġġixxi modifika sussegwenti mill-qarrejja mhuwiex Trasparenti. Format ta' immaġni mhuwiex Trasparenti jekk jintuża għal kwalunkwe ammont sostanzjali ta' test. Kopja li mhix "Trasparenti" tissejjaħ "Opaka".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Tex info 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. Exampil-formati ta' immaġini trasparenti jinkludu PNG, XCF u JPG. Formati opaki jinkludu formati proprjetarji li jistgħu jinqraw u editjati biss minn word processors proprjetarji, SGML jew XML li għalihom id-DTD u/jew l-għodod tal-ipproċessar mhumiex ġeneralment disponibbli, u l-HTML, PostScript jew PDF iġġenerat mill-magni prodotti minn xi word processors għal skopijiet ta' output biss.

Il-“Paġna tat-Titolu” tfisser, għal ktieb stampat, il-paġna tat-titlu nnifisha, flimkien ma’ dawk il-paġni li ġejjin li huma meħtieġa biex iżommu, b’mod leġibbli, il-materjal li din il-Liċenzja teħtieġ biex jidher fil-paġna tat-titlu. Għal xogħlijiet f'formati li m'għandhom l-ebda paġna tat-titlu bħala tali, "Paġna tat-Titlu" tfisser it-test ħdejn l-aktar dehra prominenti tat-titlu tax-xogħol, qabel il-bidu tal-korp tat-test.

Sezzjoni “XYZ Intitolat” tfisser subunità msemmija tad-Dokument li t-titlu tiegħu jew huwa preċiżament XYZ jew fih XYZ fil-parentesi wara test li jittraduċi XYZ f'lingwa oħra. (Hawnhekk XYZ tirrappreżenta isem ta' sezzjoni speċifika msemmi hawn taħt, bħal "Rikonoxximenti", "Dedikazzjoni", "Endorsjari", jew "Storja".) Biex "Ippreserva t-Titolu" ta' taqsima bħal din meta timmodifika d-Dokument tfisser li hija tibqa’ taqsima “XYZ intitolata” skont din id-definizzjoni.

Id-Dokument jista' jinkludi Ċaħdiet ta' Garanzija ħdejn l-avviż li jgħid li din il-Liċenzja tapplika għad-Dokument. Dawn iċ-Ċaħdiet ta' Garanzija huma kkunsidrati li huma inklużi b'referenza f'din il-Liċenzja, iżda biss fir-rigward ta' garanziji ta' ċaħda: kwalunkwe implikazzjoni oħra li dawn iċ-Ċaħdiet ta' Garanzija jista' jkollhom hija nulla u m'għandha l-ebda effett fuq it-tifsira ta' din il-Liċenzja.

KOPJAR VERBATIM

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.

Tista' wkoll isellef kopji, taħt l-istess kundizzjonijiet imsemmija hawn fuq, u tista' turi kopji pubblikament.

KOPJAR FI KWANTITÀ

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.

Jekk it-testi meħtieġa għal kwalunkwe qoxra huma voluminużi wisq biex jinqraw b'mod leġibbli, għandek tpoġġi l-ewwel dawk elenkati (kemm joqogħdu raġonevolment) fuq il-qoxra attwali, u kompli l-bqija fuq paġni ta' maġenbhom.

Jekk tippubblika jew tqassam kopji Opaki tad-Dokument li jnumeraw aktar minn 100, trid jew tinkludi kopja Trasparenti li tinqara mill-magni flimkien ma’ kull kopja Opaka, jew tiddikjara fi jew ma’ kull kopja Opaka post tan-netwerk tal-kompjuter li minnu n-netwerk ġenerali- billi tuża l-pubbliku għandu aċċess biex tniżżel permezz ta' protokolli tan-netwerk standard pubbliku kopja Trasparenti sħiħa tad-Dokument, mingħajr materjal miżjud. Jekk tuża din l-aħħar għażla, trid tieħu passi raġonevolment prudenti, meta tibda tqassam kopji Opaki fi kwantità, biex tiżgura li din il-kopja Trasparenti tibqa’ b’hekk aċċessibbli fil-post iddikjarat sa mill-inqas sena wara l-aħħar darba li tqassam Kopja opaka (direttament jew permezz tal-aġenti jew tal-bejjiegħa tiegħek) ta’ dik l-edizzjoni lill-pubbliku.

Huwa mitlub, iżda mhux meħtieġ, li tikkuntattja lill-awturi tad-Dokument sew qabel ma tqassam mill-ġdid kwalunkwe numru kbir ta’ kopji, biex tagħtihom iċ-ċans li jipprovdulek verżjoni aġġornata tad-Dokument.

MODIFIKI

Tista' tikkopja u tqassam Verżjoni Mmodifikata tad-Dokument taħt il-kundizzjonijiet tat-taqsimiet 2 u 3 hawn fuq, sakemm tirrilaxxa l-Verżjoni Mmodifikata taħt preċiżament din il-Liċenzja, bil-Verżjoni Mmodifikata timla r-rwol tad-Dokument, u b'hekk tagħti liċenzja għad-distribuzzjoni u l-modifika ta' il-Verżjoni Modifikata lil min jippossjedi kopja tagħha. Barra minn hekk, trid tagħmel dawn l-affarijiet fil-Verżjoni Modifikata:

• A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document).
  You may use the same title as a previous version if the original publisher of that version gives permission.
• B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least 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.
• C. State on the Title page the name of the publisher of the Modified Version, as the publisher.
• D. Preserve all the copyright notices of the Document.
• E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
• F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
• G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document’s license notice.
• H. Include an unaltered copy of this License.
• I. Preserve the section Entitled “History”, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled “History” in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
• J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
• K. For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
• L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
• M. Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version.
• N. Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section.
• O. Preserve any Warranty Disclaimers.

Jekk il-Verżjoni Modifikata tinkludi taqsimiet jew appendiċi ġodda ta' quddiem li jikkwalifikaw bħala Sezzjonijiet Sekondarji u ma fihom ebda materjal ikkupjat mid-Dokument, tista' fuq l-għażla tiegħek tagħżel xi wħud minn dawn it-taqsimiet jew kollha bħala invarjanti. Biex tagħmel dan, żid it-titoli tagħhom mal-lista ta 'Sezzjonijiet Invarjanti fl-avviż tal-liċenzja tal-Verżjoni Modifikata. Dawn it-titoli għandhom ikunu distinti minn kwalunkwe titoli ta' sezzjoni oħra.

Tista' żżid taqsima Imsieħba “Endorsjari”, sakemm ma jkun fiha xejn ħlief approvazzjonijiet tal-Verżjoni Modifikata tiegħek minn diversi partijiet—eż.ample, dikjarazzjonijiet ta' peer review jew li t-test ġie approvat minn organizzazzjoni bħala definizzjoni awtorevoli ta' 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.

L-awtur(i) u l-pubblikatur(i) tad-Dokument ma jagħtux permess b'din il-Liċenzja biex jużaw isimhom għall-pubbliċità għal jew biex jasserixxu jew jimplikaw l-approvazzjoni ta' kwalunkwe Verżjoni Modifikata.

DOKUMENTI TA' KOMBINAZZJONI

Tista' tgħaqqad id-Dokument ma' dokumenti oħra rilaxxati taħt din il-Liċenzja, taħt it-termini definiti fit-taqsima 4 hawn fuq għal verżjonijiet modifikati, sakemm tinkludi fil-kombinazzjoni t-Taqsimiet Invarjanti kollha tad-dokumenti oriġinali kollha, mhux modifikati, u telenkahom kollha. bħala Sezzjonijiet Invarjanti tax-xogħol magħqud tiegħek fl-avviż tal-liċenzja tiegħu, u li inti tippreserva l-Caħdiet ta’ Garanzija kollha tagħhom.

Ix-xogħol magħqud jeħtieġ li jkun fih biss kopja waħda ta' din il-Liċenzja, u Sezzjonijiet Invarjanti identiċi multipli jistgħu jiġu sostitwiti b'kopja waħda. Jekk ikun hemm diversi Sezzjonijiet Invarjanti bl-istess isem iżda kontenut differenti, agħmel it-titlu ta’ kull taqsima bħal din uniku billi żżid fl-aħħar tagħha, fil-parentesi, l-isem tal-awtur oriġinali jew tal-pubblikatur ta’ dik it-taqsima jekk magħruf, jew inkella numru uniku. Agħmel l-istess aġġustament għat-titoli tas-sezzjonijiet fil-lista tat-Taqsimiet Invarjanti fl-avviż tal-liċenzja tax-xogħol magħqud.

Fil-kombinazzjoni, trid tgħaqqad kwalunkwe sezzjoni Intitolata "Storja" fid-diversi dokumenti oriġinali, u tifforma taqsima waħda Imsejsa "Storja"; bl-istess mod għaqqad kwalunkwe sezzjoni intitolata “Rikonoxximenti”, u kwalunkwe sezzjoni intitolata “Dedikazzjoni”. Int trid tħassar it-taqsimiet kollha intitolati “Endorsjar”.

ĠABRIJIET TA' DOKUMENTI

Tista’ tagħmel ġabra li tikkonsisti mid-Dokument u dokumenti oħra rilaxxati taħt din il-Liċenzja, u tissostitwixxi l-kopji individwali ta’ din il-Liċenzja fid-diversi dokumenti b’kopja waħda li tkun inkluża fil-ġbir, sakemm issegwi r-regoli ta’ din il-Liċenzja għal ikkuppjar verbatim ta’ kull wieħed mid-dokumenti fl-aspetti l-oħra kollha.

Tista' tiġbed dokument wieħed minn kollezzjoni bħal din, u tqassam individwalment taħt din il-Liċenzja, sakemm iddaħħal kopja ta' din il-Liċenzja fid-dokument estratt, u ssegwi din il-Liċenzja fl-aspetti l-oħra kollha rigward l-ikkuppjar verbatim ta' dak id-dokument.

AGGREGAZZJONI MA' XOGĦLIJIET INDIPENDENTI

Kumpilazzjoni tad-Dokument jew id-derivattivi tiegħu ma’ dokumenti jew xogħlijiet oħra separati u indipendenti, fi jew fuq volum ta’ mezz ta’ ħażna jew distribuzzjoni, tissejjaħ “aggregat” jekk id-drittijiet tal-awtur li jirriżultaw mill-kumpilazzjoni ma jintużawx biex jillimitaw id-drittijiet legali. tal-utenti tal-kumpilazzjoni lil hinn minn dak li jippermettu x-xogħlijiet individwali. Meta d-Dokument ikun inkluż f'aggregat, din il-Liċenzja ma tapplikax għax-xogħlijiet l-oħra fl-aggregat li huma stess mhumiex xogħlijiet derivattivi tad-Dokument.

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.

TRADUZZJONI

It-traduzzjoni hija meqjusa bħala tip ta’ modifika, għalhekk tista’ tqassam traduzzjonijiet tad-Dokument taħt it-termini tat-taqsima 4. Is-sostituzzjoni tat-Taqsimiet Invarjanti bi traduzzjonijiet teħtieġ permess speċjali mid-detenturi tad-drittijiet tal-awtur tagħhom, iżda tista’ tinkludi traduzzjonijiet ta’ xi wħud jew it-Taqsimiet Invarjanti kollha flimkien ma’ il-verżjonijiet oriġinali ta’ dawn it-Taqsimiet Invarjanti. Tista' tinkludi traduzzjoni ta' din il-Liċenzja, u l-avviżi kollha tal-liċenzja fid-Dokument, u kwalunkwe Ċaħda ta' Garanzija, sakemm tinkludi wkoll il-verżjoni oriġinali bl-Ingliż ta' din il-Liċenzja u l-verżjonijiet oriġinali ta' dawk l-avviżi u ċaħdiet. F'każ ta' nuqqas ta' qbil bejn it-traduzzjoni u l-verżjoni oriġinali ta' din il-Liċenzja jew avviż jew ċaħda ta' responsabbiltà, il-verżjoni oriġinali tipprevali.

Jekk taqsima fid-Dokument tkun Intitolata “Rikonoxximenti”, “Dedikazzjoni”, jew “Storja”, ir-rekwiżit (taqsima 4) biex Jippreserva t-Titolu tiegħu (taqsima 1) tipikament jeħtieġ li jinbidel it-titolu attwali.

TERMINAZZJONI

Inti ma tistax tikkopja, timmodifika, tissottoliċenzja jew tqassam id-Dokument ħlief kif ipprovdut espressament taħt din il-Liċenzja. Kwalunkwe tentattiv ieħor biex tikkopja, timmodifika, sottoliċenzja jew tqassam id-Dokument huwa null, u awtomatikament itemm id-drittijiet tiegħek taħt din il-Liċenzja. Madankollu, partijiet li jkunu rċevew kopji, jew drittijiet, mingħandek taħt din il-Liċenzja mhux se jkollhom il-liċenzji tagħhom mitmuma sakemm dawn il-partijiet jibqgħu f'konformità sħiħa.

REVIŻJONIJIET FUTUR TA’ DIN IL-LIĊENZA

Il-Free Software Foundation tista' tippubblika verżjonijiet ġodda u riveduti tal-Liċenzja ta' Dokumentazzjoni Ħieles GNU minn żmien għal żmien. Verżjonijiet ġodda bħal dawn se jkunu simili fl-ispirtu għall-verżjoni preżenti, iżda jistgħu jvarjaw fid-dettall biex jindirizzaw problemi jew tħassib ġodda. Ara http://www.gnu.org/copyleft/.

Kull verżjoni tal-Liċenzja tingħata numru ta' verżjoni distintiv. Jekk id-Dokument jispeċifika li verżjoni numerata partikolari ta’ din il-Liċenzja “jew kwalunkwe verżjoni aktar tard” tapplika għaliha, għandek l-għażla li ssegwi t-termini u l-kundizzjonijiet jew ta’ dik il-verżjoni speċifikata jew ta’ kwalunkwe verżjoni aktar tard li tkun ġiet ippubblikata (mhux bħala abbozz) mill-Free Software Foundation. Jekk id-Dokument ma jispeċifikax numru tal-verżjoni ta' din il-Liċenzja, tista' tagħżel kwalunkwe verżjoni li qatt tkun ippubblikata (mhux bħala abbozz) mill-Free Software Foundation.

ADDENDUM: Kif tuża din il-Liċenzja għad-dokumenti tiegħek

Copyright (c) SENA ISEM TIEGĦEK. Jingħata permess biex dan id-dokument jiġi kkopjat, imqassam u/jew immodifikat taħt it-termini tal-Liċenzja tad-Dokumentazzjoni Ħieles GNU, Verżjoni 1.2 jew kwalunkwe verżjoni aktar tard ippubblikata mill-Free Software Foundation; mingħajr l-ebda Sezzjonijiet Invarjanti, l-ebda Testi ta’ Qoxra ta’ Quddiem, u l-ebda Testi ta’ Kopertura ta’ wara. Kopja tal-liċenzja hija inkluża fit-taqsima intitolata “Liċenzja tad-Dokumentazzjoni Ħieles GNU”.