UYUNI Common Workflows User Guide

UYUNI Common Workflows

UYUNI Common Workflows

UYUNI Common Workflows

Okwu mmalite

Isi nke 1

Usoro ọrụ nkịtị

Ọnwụ 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.

Ụbọchị mbipụta: 2026-04-29

Onye ahịa n'ụgbọ mmiri

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

Jiri Okwu

Usoro ọrụ a na-egosi gị otu ị ga-esi banye onye ahịa na sava Uuni gị.

Onye ahịa ga-enwerịrị sistemụ arụmọrụ Linux akwadoro. Maka ndepụta sistemụ ndị ahịa akwadoro, hụ Client-configuration › Supported-features.

Nke a bụ otu n'ime ọrụ mbụ ị ga-eme mgbe ịtọlite ​​​​Uyuni na nke mbụ, ma eleghị anya ị ga-eme ya ọtụtụ ugboro ka ị na-eji ngwaahịa ahụ.

Nsonaazụ

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. Ị nwere ike iji Uuni jikwaa onye ahịa.

Nkwadebe

Tupu ịmalite, ị ga-enwerịrị:

  • Uyuni Server arụnyere, nke ị nwere ike ịnweta site na iji Web UI.
  • Igwe ndị ahịa nwere sistemụ arụmọrụ arụnyere, nke ị nwere ike ịnweta n'ofe netwọk nke Uyuni Server gị nọ, na-eji SSH.
  • Ndebanye aha kwesịrị ekwesị sitere na http://scc.suse.com maka ngwaahịa ndị ị na-eji.

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.

Ntuziaka usoro usoro nzọụkwụ

Usoro: Configure a Fully Qualified Domain Name (FQDN) on Your Client

  1. Na onye ahịa, na ngwa ngwa iwu, gosi aha nnabata ugbu a:
    hostname -f
    Iwu a nwere ike weghachi mperi, ma ọ bụ gosi ihe dịka localhost.
  2. Tọọ aha nnabata ọhụrụ. Aha nnabata ọhụrụ gị kwesịrị inwe aha subdomain wee tinye opekata mpe nkeji abụọ. Na nke a example, we are using client1.MLM.example
    hostnamectl set-hostname client1.MLM.example
  3. Lelee na mgbanwe gị gara nke ọma:
    hostnamectl
  4. Open YaST and navigate to Network Services › Hostnames. Edit the hostname to match the one you just
    set, and click [Ọ DỊ MMA].
  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. Lelee na mgbanwe a gara nke ọma:
    hostname -f
    This command should return your new FQDN

Usoro: Kwadebe ọwa sọftụwia na sava Uyuni

  1. N'ime Uunu Web UI, gaa na Admin › Setup Wizard.
  2. Na taabụ nzere nke nzukọ, hụ na ị abanyela nzere SUSE Centre ahịa gị, wee kwado ya nke ọma.
  3. Na ngwaahịa taabụ, hụ na emelitere katalọgụ ngwaahịa a:
  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 [Tinye ngwaahịa ]:
  5. Chere ka ọwa ngwaahịa ga-emekọrịta nke ọma. Dabere na ngwaahịa ị họọrọ, nke a nwere ike iwe ogologo oge.

Usoro: Mepụta igodo ịgbalite

  1. N'ime Uunu Web UI, gaa na Sistemu Activation Keys, wee pịa [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 [Mepụta igodo ntinye].

Usoro: Bootstrap onye ahịa ahụ

  1. N'ime Uunu Web UI, gaa na Systems › Bootstrapping.
  2. Pịnye aha nnabata wee nye nzere nyocha maka onye ahịa ịchọrọ ịbanye, wee họrọ igodo mmalite. Pịa [Bootstrap]:
  3. Gaa na Systems › System List to manage your new client

Isiokwu ndị emetụtara

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

Mmelite ndị ahịa na-eji eme ugboro ugboro

Isi nke 3

Usoro ọrụ a na-egosi otu esi emelite ndị ahịa debanyere aha na Uyuni site na iji omume ugboro ugboro.

Use case / Situation

Mmelite akpaghị aka nke ndị ahịa bara uru mgbe:

  • update nke ọnụ ọgụgụ buru ibu nke ndị ahịa chọrọ
  • A ghaghị imegharị usoro ahụ n'ọrụ ọ bụla
  • windo mmezi raara onwe ya nye dị.

Nsonaazụ / Mkpebi

Mmecha usoro ọrụ a nke ọma na-ebute ọnọdụ na-agbanwe agbanwe yana nkwado.

Nkwadebe

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

Ka imelite onye ahịa chọrọ nzọụkwụ abụọ. Nzọụkwụ nke atọ bụ nhọrọ mana akwadoro nke ukwuu iji mechaa usoro mmelite ahụ.

Usoro: Creating a recurring action to update Salt itself

  1. Dị ka exampLe, anyị na-emepụta ihe iji melite nnu n'onwe ya dị ka ihe na-eme ugboro ugboro maka sistemụ niile dị na nzukọ. N'ime Uunu Web UI, gaa na Home › My Organization › Recurring Actions wee pịa [Create].
  2. Select Action Type Omenala Steeti and enter a Schedule Name like update salt .
  3. Họrọ nhazi oge. Maka example, Weekly: Wednesday, 9:00 am .
  4. Kenye steeti nnu site na ịhọrọ igbe nlele.
  5. Pịa [Save Changes ] to save the action.
  6. You can edit the execution order of the states if needed. Click [Kwapụta] to confirm the order.
  7. Pịa [Create Schedule] to save the action.

Usoro: Creating a recurring action to apply all available updates to the systems

  1. Dị ka example we create the action to apply all updates as a recurring action for a system group called infra-ọrụ. N'ime Uunu 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. Họrọ Nhazi oge. Maka 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 [Chekwaa mgbanwe ].
  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 [Kwapụta] to store the order.
  8. Pịa [Create Schedule] to save the action.

Usoro: Creating a recurring action to run a high state after the update

  1. Dị ka example, we create the action to apply the high state for the same group which was fully updated before. In the Uyuni Web UI, gaa na Systems › System Groups and click infra-services.
  2. Go to Recurring Actions and click [Create].
  3. Select Action Type Ọnọdụ dị elu and enter a Schedule Name like high state .
  4. Họrọ Nhazi oge. Maka example, Weekly: Wednesday, 10:30 am . Again, keep enough time between this action and the full-system-update action.
  5. Pịa [Create Schedule] to save the action.

Background information on up-to-date state

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

Isiokwu ndị emetụtara

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

Njikwa nhazi

Isi nke 4

Ị nwere ike iji nhazi files na ọwa iji jikwaa nhazi maka ndị ahịa gị, kama iji aka hazie onye ahịa ọ bụla. Usoro ọrụ a na-egosi gị otu esi eji Uyuni Web UI iji mepụta nhazi etiti ejirila file, kenye ya na onye ahịa, ma tinye nhazi ahụ.

Jiri Okwu

Ọ bụrụ na ị na-ejikwa ọtụtụ ndị ahịa, ikekwe ị chọghị iji aka tinye ntọala nhazi na nke ọ bụla n'ime ha. A na-eji ọwa nhazi nhazi nhazi files. Ị nwere ike ịdenye aha ndị ahịa na ọwa nhazi, ma tinye nhazi files dị ka achọrọ.

Nsonaazụ

Mgbe ịmechara usoro ọrụ a, ị ga-enwe ọwa nhazi nwere nhazi file, ekenyela ndị ahịa na ọwa ahụ, ma tinye nhazi ahụ nke ọma.

Nkwadebe

Tupu ịmalite, ị ga-enwerịrị:

  • Uyuni Server arụnyere, nke ị nwere ike ịnweta site na iji Web UI.
  • Ọ dịkarịa ala otu onye ahịa debara aha na sava gị.
  • Ndebanye aha kwesịrị ekwesị sitere na http://scc.suse.com maka ngwaahịa ndị ị na-eji.

Usoro ọrụ a na-eji nhazi a na-achịkwa nke ọma file and a Salt state. For more information about the different ways to manage configuration, see Client-configuration › Configuration-management.

Ntuziaka usoro usoro nzọụkwụ

Usoro: Mepụta ọwa nhazi ọhụrụ yana File

  1. N'ime Uunu Web UI, gaa na Configuration › Channels wee pịa [Create State Channel].
  2. Pịnye aha, akara, na nkọwa maka nhazi gị file, ma pịnye ọdịnaya nke nhazi gị file. Otu example that you can copy is at the end of this section.

Usoro: Kenye ndị ahịa na ọwa nhazi

  1. N'ime Uunu Web UI, gaa na Systems › Systems List and select the client you want to assign to your configuration channel.
  2. Gaa na taabụ nhazi. Na guimenu: Nhazi gafereview ngalaba, pịa [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 ] imecha.

Usoro: Tinye nhazi ahụ na onye ahịa gị

  1. N'ime Uunu Web UI, gaa na 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

Steeti SLS maka idobe ndị ahịa emelitere

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 %}

Isiokwu ndị emetụtara

Njikwa Ndụ okirikiri ọdịnaya

Isi nke 5

Ọ bụrụ na ị na-ejikwa ọtụtụ ndị ahịa na ịchọrọ itinye ngwungwu ahaziri ahazi nye ha, ị nwere ike iji njikwa ndụ ndụ ọdịnaya (CLM) iji jikwaa ngwugwu gị. CLM na-enye gị ohere ịhazi ma nwalee ngwugwu tupu emelite ndị ahịa mmepụta. Ọ dịkwa uru ma ọ bụrụ na ịchọrọ itinye mmelite n'oge windo mmezi nwere oke.

Jiri Okwu

Njikwa ndụ okirikiri ọdịnaya na-enye gị ohere ịhọrọ ọwa sọftụwia dị ka isi mmalite, mezie ya dịka achọrọ maka gburugburu ebe obibi gị, wee nwalee ha nke ọma tupu ịwụnye na ndị ahịa mmepụta gị. Ị nwere ike iji CLM jikwaa ọwa sọftụwia gị site na mmepe, site na nnwale, na ịtụgharị mgbanwe ndị ahịa gị.

Nsonaazụ

Mgbe ịmechara usoro ọrụ a, ị ga-enwe ọrụ nhazi usoro ndụ ọdịnaya. Ị ga-emepụtala ọrụ CLM bụ isi, wee kwalite ya site na okirikiri ndụ ya.

Nkwadebe

Tupu ịmalite, ị ga-enwerịrị:

  • Uyuni Server deployed, and accessible using the Web UI.
  • Igwe ndị ahịa nwere sistemụ arụmọrụ arụnyere, nke ị nwere ike ịnweta n'ofe netwọk nke Uyuni Server gị nọ, na-eji SSH.
  • Ndebanye aha kwesịrị ekwesị sitere na http://scc.suse.com maka ngwaahịa ndị ị na-eji.

Ntuziaka usoro usoro nzọụkwụ

Usoro: Mepụta Project CLM ọhụrụ

  1. N'ime Uunu Web UI, gaa na 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 [Chekwaa] to return to the project page.
  3. Hapụ ngalaba nzacha oghere maka ugbu a, anyị agaghị eji ha na mbụ aample. Ị nwere ike itinye nzacha ma emechaa ma ọ bụrụ na ịchọrọ.
  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. Pịa [wuo] to build version 1 of your project:

Usoro: Kenye ndị ahịa

  1. Gaa na 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.
    Maka 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. Pịa [Osote] to assign the client.

Usoro: Kwalite gburugburu

  1. N'ime Uunu Web UI, gaa na 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.

Isiokwu ndị emetụtara

  • For more information about CLM, including information about how to use filters, see Administration › Content-lifecycle.
  • Maka CLM example, hụ Administration › Content-lifecycle-examples.

Customize Apache Configuration

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

Jiri akpa

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.

Nsonaazụ

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

Nkwadebe

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

Akara 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 (maka example, custom_ tuning. conf) and add your required Apache directives.
  5. Ozugbo ị zọpụtara gị file, exit the container with command:
    exit
  6. Restart the Uyuni services to apply the changes:
    mgradm restart

Nkwalite ngwaahịa site na Web UI

Isi nke 7

Ọ bụrụ na ịchọrọ ịkwalite mkpọ ahịa ahịa SUSE Linux Enterprise edebanyere aha na ụdị ngwaahịa ọhụrụ, enwere ike ịme ya na ahịrị iwu ma ọ bụ site na Web UI.

Akwụkwọ a na-akọwa ma gosipụta n'ụzọ zuru ezu nkwalite ngwaahịa site na iji Web UI.

Akara Ụdị ngwaahịa eji eme ihe anaghị egosipụta n'ezie ụdị kachasị ọhụrụ dị. A na-eji ha naanị maka ihe atụ. Dị ka example, usoro a na-akọwa nkwalite gaa na ụdị 15 SP5 sitere na ụdị 15 nke ochie. Ọ bụrụ na ị na-ezubere ụdị dị iche, họrọ ọwa na ụdị kwekọrọ.

Usoro: Ịkwalite ngwaahịa gaa na ụdị ọhụrụ site na iji Web UI

  1. Banye na Uyuni Web UI and navigate to Admin › Setup Wizard › Products and search for SUSE Linux Enterprise Server 15 SP5 x86_64.
  2. Họrọ ọwa ndị akwadoro.
  3. Pịa [Add Products ].
  4. Gaa na Systems › Registered client › Software › Product Migration. You will see the targets available for that registered client.
  5. Họrọ SUSE Linux Enterprise Server 15 SP5 x86_64. Nke a ga-agbasawanye n'ihu.
  6. Họrọ ọwa Target Base dị ka SLE-Product-SLES15-SP5-Pool maka x86_64. Debe Kwe ka onye na-ere ahịa agbanweghị elele.
  7. Pịa [Schedule Migration]. The message will be highlighted It is better to do a dry run first so continuing with dry run first.
  8. Pịa [Ọsọ akọrọ] and check the status of the simulation in Events › History. You should see a return code 0 indicating a successful dry run.
  9. Pịa [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. Na Yuuni Web UI side, verify the successfully completed product upgrade by going to Systems › Registered client › Details.
  12. N'akụkụ ndị ahịa ị nwere ike nyochaa ya site na ịgba ọsọ:
    cat /etc/os-release
  13. Mpụta ga-adị ka:

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/"

Akwụkwọ ikike GNU efu

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

EKPERE

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.

Anyị haziri ikikere a ka anyị were ya maka akwụkwọ ntuziaka maka sọftụwia efu, n'ihi na ngwanrọ efu chọrọ akwụkwọ n'efu: mmemme efu kwesịrị ịbịa na akwụkwọ ntuziaka na-enye otu nnwere onwe nke ngwanro ahụ na-eme. Mana ikikere a ejedebeghị na akwụkwọ ntuziaka ngwanrọ; enwere ike iji ya rụọ ọrụ ederede ọ bụla, n'agbanyeghị isiokwu ma ọ bụ na e bipụtara ya dị ka akwụkwọ e biri ebi. Anyị na-akwado ikikere a maka ọrụ ndị ebumnuche ha bụ ntuziaka ma ọ bụ ntụnye aka.

Ngwa na nkọwa

Ikikere a na-emetụta akwụkwọ ntuziaka ma ọ bụ ọrụ ọ bụla, n'ụdị ọ bụla, nke nwere ọkwa nke onye ji nwebiisinka debere na-ekwu na enwere ike kesaa ya n'okpuru usoro Ikikere a. Ọkwa dị otú ahụ na-enye ikike zuru ụwa ọnụ, ikike enweghị ikike eze, na-akparaghị ókè, iji ọrụ ahụ n'okpuru ọnọdụ ndị ekwuru n'ebe a. "Akwụkwọ", n'okpuru, na-ezo aka na akwụkwọ ntuziaka ma ọ bụ ọrụ ọ bụla. Onye ọ bụla n'ime ọha bụ onye nyere ikike, a na-akpọkwa ya "gị". Ị na-anabata ikikere ma ọ bụrụ na idetuo, gbanwee ma ọ bụ kesaa ọrụ ahụ n'ụzọ chọrọ ikike n'okpuru iwu nwebiisinka.

Ụdị "Modified" nke akwụkwọ ahụ pụtara ọrụ ọ bụla nwere akwụkwọ ahụ ma ọ bụ akụkụ ya, ma ọ bụ ederede verbatim, ma ọ bụ nwere mgbanwe na/ma ọ bụ tụgharịa gaa n'asụsụ ọzọ.

"Ngalaba nke abụọ" bụ ihe mgbakwunye aha ya bụ ihe mgbakwunye ma ọ bụ akụkụ dị n'ihu nke akwụkwọ ahụ nke na-ekwu maka mmekọrịta nke ndị bipụtara ma ọ bụ ndị dere akwụkwọ ahụ na isiokwu n'ozuzu akwụkwọ (ma ọ bụ ihe metụtara) na enweghị ihe ọ bụla nwere ike ịdaba ozugbo. n'ime isiokwu ahụ n'ozuzu ya. (Ya mere, ọ bụrụ na akwụkwọ ahụ bụ akụkụ nke akwụkwọ ọgụgụ nke mgbakọ na mwepụ, ngalaba nke abụọ nwere ike ọ gaghị akọwa mgbakọ na mwepụ ọ bụla.) Mmekọrịta ahụ nwere ike ịbụ ihe gbasara njikọ akụkọ ihe mere eme na isiokwu ma ọ bụ ihe metụtara ya, ma ọ bụ nke iwu, azụmahịa, nkà ihe ọmụma, ụkpụrụ omume. ma ọ bụ ọnọdụ ndọrọ ndọrọ ọchịchị gbasara ha.

“Ngalaba ndị na-adịghị agbanwe agbanwe” bụ akụkụ nke abụọ nke aha hapụtara aha ha, dị ka nke ngalaba na-agbanwe agbanwe, na ọkwa nke na-ekwu na ewepụtara akwụkwọ ahụ n'okpuru Ikikere a. Ọ bụrụ na ngalaba adabaghị nkọwa nke ụlọ akwụkwọ sekọndrị nke dị n'elu, agaghị ekwe ka akpọpụta ya dị ka Invariant. Akwụkwọ ahụ nwere ike ịnwe akụkụ efu. Ọ bụrụ na akwụkwọ ahụ achọpụtaghị akụkụ ọ bụla na-agbanwe agbanwe mgbe ahụ ọ nweghị nke ọ bụla.

“Ihe odide mkpuchi” bụ akụkụ dị mkpirikpi nke edepụtara, dị ka ederede ihu mkpuchi ma ọ bụ ederede azụ, na ọkwa nke na-ekwu na ewepụtara akwụkwọ ahụ n'okpuru Ikikere a. Ederede mkpuchi ihu nwere ike ịbụ okwu 5 kacha karịa, yana ederede mkpuchi azụ nwere ike ịbụ okwu 25 kachasị.

Mpempe akwụkwọ “Transparent” pụtara nnomi nke igwe nwere ike ịgụ, nke nọchiri anya ya n'ụdị nke nkọwapụta ya dị maka ọha ọha, nke dabara adaba iji degharịa akwụkwọ ahụ ozugbo site na ndị editọ ederede ma ọ bụ (maka onyonyo nwere pikselụ) agba. mmemme ma ọ bụ (maka eserese) ụfọdụ editọ eserese dị ebe niile, nke ahụ dabara adaba maka ntinye na ndị na-ahazi ederede ma ọ bụ maka ntụgharị akpaka n'ụdị dị iche iche dabara adaba maka ntinye na ndị nhazi ederede. Mpempe akwụkwọ emere n'ụzọ doro anya ọzọ file Usoro nke ahaziri akara ya, ma ọ bụ enweghị akara, iji gbochie ma ọ bụ mee ka ndị na-agụ ya gbanwee na-esote abụghị N'ụzọ doro anya. Ụdị onyonyo anaghị apụ apụ ma ọ bụrụ na ejiri ya maka nnukwu ederede ọ bụla. Mpempe akwụkwọ na-abụghị “Transparent” ka a na-akpọ “Opaque”.

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. ExampỤdị ihe onyonyo pụtara ìhè gụnyere PNG, XCF na JPG. Ụdị na-adịghị ahụkebe na-agụnye ụdị nwe nke enwere ike ịgụ na dezie naanị site na ndị na-emepụta okwu, SGML ma ọ bụ XML nke DTD na/ma ọ bụ ngwaọrụ nhazi adịghị adịkarị, yana HTML, PostScript ma ọ bụ PDF mepụtara igwe nke ụfọdụ ndị na-emepụta okwu mepụtara maka. naanị mmepụta ebumnuche.

“Ibe aha” pụtara, maka akwụkwọ e biri ebi, ibe aha n'onwe ya, gbakwunyere ibe ndị na-eso nke achọrọ iji jide, n'ụzọ ziri ezi, ihe Ikikere chọrọ ka ọ pụta na ibe aha. Maka ọrụ n'ụdị nke na-enweghị ibe aha ọ bụla dị ka nke a, "Title Page" pụtara ederede dị nso na aha ọrụ ahụ kacha pụta ìhè, na-ebute mmalite nke akụkụ nke ederede.

Akụkụ “Akpọrọ aha XYZ” pụtara ngalaba aha ya bụ nke akwụkwọ aha ya bụ XYZ kpọmkwem ma ọ bụ nwere XYZ na mbomoko na-eso ederede nke sụgharịrị XYZ n'asụsụ ọzọ. (Ebe a XYZ na-anọchi anya otu ngalaba aha a kpọtụrụ aha n'okpuru, dị ka "Nkwenye", "Nraranye", "Nkwenye", ma ọ bụ "Akụkọ Ihe mere eme") Iji "chekwaa Aha" nke ngalaba dị otú ahụ mgbe ị gbanwee akwụkwọ ahụ pụtara na ọ bụ ya. ka bụ ngalaba “Akpọrọ aha XYZ” dịka nkọwapụta a siri dị.

Akwụkwọ ahụ nwere ike ịgụnye nkwusa akwụkwọ ikike n'akụkụ ọkwa nke na-ekwu na Ikikere a metụtara akwụkwọ ahụ. A na-ahụta nkwusa akwụkwọ ikike ndị a ka agụnyere site na ntụaka na ikike a, mana naanị n'ihe gbasara ịzaghachi akwụkwọ ikike: nhụta ọ bụla ọzọ nke nkwusa akwụkwọ ikike ndị a nwere ike inwe bụ ihe efu na enweghị mmetụta na nkọwa akwụkwọ ikike a.

Iṅomi okwu ọnụ

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.

Ị nwekwara ike ịgbazinye akwụkwọ, n'okpuru otu ọnọdụ ekwuru n'elu, ma ị nwere ike igosi ọha mmadụ.

Iṅomi n'ọnụọgụgụ

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.

Ọ bụrụ na ederede achọrọ maka mkpuchi nke ọ bụla dị oke oke nke dabara nke ọma, ị ga-etinye nke mbụ edepụtara (nke dabara nke ọma) na mkpuchi ahụ n'ezie, wee gaa n'ihu nke ọzọ na ibe ndị dị n'akụkụ.

Ọ bụrụ na ibipụta ma ọ bụ kesaa mbipụta akwụkwọ akụkọ ihe karịrị 100, ị ga-enwerịrị ike itinye nnomi transparent nke igwe nwere ike ịgụ ya yana nke ọ bụla Opaque, ma ọ bụ kwuo na ma ọ bụ jiri Opaque nke ọ bụla detuo ọnọdụ netwọkụ kọmputa nke sitere na netwọkụ ọha. iji ọha nwere ohere iji budata site na iji ụkpụrụ netwọkụ ọkọlọtọ ọha, nnomi nke akwụkwọ ahụ enweghị nkọwa zuru oke, enweghị ihe agbakwunyere. Ọ bụrụ na ị na-eji nhọrọ nke ikpeazụ, ị ga-emerịrị usoro ezi uche dị na ya, mgbe ịmalitere nkesa mbipụta Opaque n'ọtụtụ, iji hụ na ngbanwe a Transparent ga-anọgide na-enweta ya na ebe ekwuputara ruo opekata mpe otu afọ mgbe oge ikpeazụ ị kesaa ihe. Mpempe akwụkwọ na-enweghị isi (kpọmkwem ma ọ bụ site na ndị nnọchi anya gị ma ọ bụ ndị na-ere ahịa) nke mbipụta ahụ nye ọha.

A na-arịọ ya, mana ọ bụghị achọrọ, ka ị kpọtụrụ ndị dere akwụkwọ ahụ nke ọma tupu ị kesaa ọnụ ọgụgụ buru ibu nke mbipụta ọ bụla, iji nye ha ohere ịnye gị ụdị akwụkwọ ahụ emelitere.

Mgbanwe

Ị nwere ike idetuo ma kesaa ụdị akwụkwọ ahụ gbanwetụrụ n'okpuru ọnọdụ nke ngalaba 2 na 3 dị n'elu, ma ọ bụrụhaala na ị weputara Ụdị Mgbanwe n'okpuru Ikikere a kpọmkwem, yana ụdị Modified na-ejuputa ọrụ nke akwụkwọ ahụ, si otú a na-enye ikike nkesa na mgbanwe nke Modified Version nye onye ọ bụla nwere otu ya. Na mgbakwunye, ị ga-emerịrị ihe ndị a na ụdị modified:

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

Ọ bụrụ na ụdị gbanwetụrụ gụnyere ngalaba ma ọ bụ ihe mgbakwunye ọhụrụ tozuru oke dị ka ngalaba nke abụọ na enweghị ihe e depụtaghachiri na dọkụmentị ahụ, ị ​​nwere ike na nhọrọ gị wepụta ụfọdụ ma ọ bụ akụkụ ndị a niile ka enweghị mgbanwe. Iji mee nke a, tinye aha ha na ndepụta nke ngalaba ndị na-adịghị agbanwe agbanwe na ọkwa ikike nke ụdị modified. Aha ndị a ga-adị iche na aha ngalaba ọ bụla ọzọ.

Ị nwere ike ịgbakwunye ngalaba akpọrọ "Endorsements", ma ọ bụrụ na ọ nwere ihe ọ bụla ma ọ bụghị nkwado nke ụdị gị nke ndị otu dị iche iche - maka ex.ample, nkwupụta nke ndị ọgbọ review ma ọ bụ na òtù akwadola ederede dị ka nkọwa ikike nke ọkọlọtọ.

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.

Ndị odee na ndị mbipụta akwụkwọ ahụ enyeghị ikike iji aha ha maka mgbasa ozi maka ma ọ bụ kwupụta ma ọ bụ gosipụta nkwado nke ụdị gbanwetụrụ ọ bụla.

NA-ejikọta akwụkwọ

Ị nwere ike ijikọ akwụkwọ ahụ na akwụkwọ ndị ọzọ ewepụtara n'okpuru Ikikere a, n'okpuru usoro akọwara na ngalaba 4 dị n'elu maka ụdị gbanwetụrụ, ma ọ bụrụhaala na ị gụnyere na nchikota akụkụ niile na-adịghị agbanwe agbanwe nke akwụkwọ mbụ niile, agbanwebeghị, wee depụta ha niile. dị ka akụkụ ndị na-adịghị agbanwe agbanwe nke ọrụ gị jikọtara ọnụ na ọkwa ikike ya, yana na ị na-echekwa nkwupụta akwụkwọ ikike ha niile.

Ọrụ agbakwunyere kwesịrị ịnwe naanị otu akwụkwọ ikike a, yana enwere ike iji otu oyiri dochie ọtụtụ ngalaba Invariant yiri ya. Ọ bụrụ na enwere ọtụtụ ngalaba na-agbanwe agbanwe nwere otu aha mana ọdịnaya dị iche iche, mee ka aha ngalaba nke ọ bụla bụrụ ihe pụrụ iche site n'ịgbakwunye na njedebe ya, n'ime akara aka, aha onye mbụ dere ma ọ bụ onye bipụtara ngalaba ahụ ma ọ bụrụ na amaara ya, ma ọ bụ ọzọ. pụrụ iche nọmba. Mee otu mgbanwe ahụ na aha ngalaba dị na ndepụta nke ngalaba ndị na-agbanwe agbanwe na ọkwa ikike nke ọrụ jikọtara ọnụ.

Na ngwakọta, ị ga-ejikọta akụkụ ọ bụla akpọrọ "Akụkọ" na akwụkwọ mbụ dị iche iche, na-eme otu ngalaba akpọrọ "History"; n'otu aka ahụ, jikọta ngalaba ọ bụla akpọrọ "Nkwenye", yana ngalaba ọ bụla akpọrọ "Nraranye". Ị ga-ehichapụrịrị ngalaba niile akpọrọ "Endorsements".

Mkpokọta akwụkwọ

Ị nwere ike ịmepụta mkpokọta nke nwere akwụkwọ na akwụkwọ ndị ọzọ ewepụtara n'okpuru Ikikere a, ma jiri otu oyiri nke etinyere na mkpokọta ahụ dochie akwụkwọ ikike a n'otu n'otu. idegharị okwu ọnụ nke ọ bụla n'ime akwụkwọ ahụ n'akụkụ ndị ọzọ niile.

Ị nwere ike wepụ otu akwụkwọ na nchịkọta dị otú ahụ, ma kesaa ya n'otu n'otu n'okpuru Ikikere a, ma ọ bụrụ na ịtinye akwụkwọ ikike a n'ime akwụkwọ ewepụtara, ma soro Ikikere a n'akụkụ ndị ọzọ gbasara idegharị akwụkwọ ahụ ozugbo.

Mkpokọta na ọrụ onwe

A na-akpọ nchịkọta akwụkwọ ma ọ bụ ihe nrụpụta ya na akwụkwọ ma ọ bụ ọrụ ndị ọzọ dị iche na nke nọọrọ onwe ya, n'ime ma ọ bụ na mpịakọta nke nchekwa ma ọ bụ usoro nkesa, "nchịkọta" ma ọ bụrụ na ejighị ikike nwebisiinka sitere na nchịkọta ahụ iji kpachie ikike iwu kwadoro. nke ndị ọrụ chịkọtara karịa ihe onye ọrụ nyere ikike. Mgbe etinyere akwụkwọ ahụ na mkpokọta, ikike a anaghị emetụta ọrụ ndị ọzọ na mkpokọta nke na-abụghị ọrụ ewepụtara nke akwụkwọ ahụ n'onwe ha.

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.

Nsụgharị

A na-ewere ntụgharị dị ka ụdị mgbanwe, yabụ ị nwere ike kesaa ntụgharị asụsụ nke akwụkwọ ahụ n'okpuru usoro nke ngalaba 4. Dochie ngalaba ndị na-agbanwe agbanwe na ntụgharị asụsụ chọrọ ikike pụrụ iche site n'aka ndị nwe nwebisiinka, mana ị nwere ike ịgụnye ntụgharị asụsụ nke ụfọdụ ma ọ bụ akụkụ niile na-agbanwe agbanwe na mgbakwunye. nsụgharị mbụ nke ngalaba ndị a na-adịghị agbanwe agbanwe. Ị nwere ike ịgụnye ntụgharị asụsụ nke akwụkwọ ikike a, yana ọkwa ikike niile dị na akwụkwọ ahụ, yana akwụkwọ ikike nkwụghachi ụgwọ ọ bụla, ma ọ bụrụhaala na ị tinyekwara nsụgharị Bekee mbụ nke Ikikere a na ụdị izizi nke ọkwa na nkwupụta ndị ahụ. Ọ bụrụ na enwere nghọtahie n'etiti ntụgharị asụsụ na ụdị izizi nke ikike a ma ọ bụ ọkwa ma ọ bụ nkwuputa, ụdị izizi ga-emeri.

Ọ bụrụ na ngalaba dị na akwụkwọ ahụ nwere aha "Nkwanye", "Nraranye", ma ọ bụ "Akụkọ", ihe achọrọ (ngalaba 4) iji chekwaa aha ya (ngalaba 1) ga-achọkarị ịgbanwe aha ya.

Nkwụsị

Ịnweghị ike idetuo, gbanwee, ịnye ikike, ma ọ bụ kesaa akwụkwọ ahụ belụsọ dị ka enyere nke ọma n'okpuru Ikikere a. Mgbalị ọ bụla ọzọ iji detuo, gbanwee, inye ikike ma ọ bụ kesaa akwụkwọ ahụ bụ ihe efu, ọ ga-ewepụ ikike gị n'okpuru Ikikere a ozugbo. Agbanyeghị, ndị otu natara akwụkwọ ikike, ma ọ bụ ikike, n'aka gị n'okpuru Ikikere a agaghị akwụsị ikike ha ma ọ bụrụhaala na ndị otu a ga-anọ na nnabata zuru oke.

Ntụleghachi nke ikikere a n'ọdịnihu

Ntọala sọftụwia efu nwere ike ibipụta ụdị ikikere GNU efu edegharịrị ọhụrụ site n'oge ruo n'oge. Ụdị ọhụrụ ndị dị otú ahụ ga-adị ka mmụọ dị ugbu a, mana ọ nwere ike ịdị iche na nkọwa zuru ezu iji dozie nsogbu ma ọ bụ nchegbu ọhụrụ. Lee http://www.gnu.org/copyleft/.

A na-enye ụdị ikike ọ bụla nọmba ụdị pụrụ iche. Ọ bụrụ na akwụkwọ ahụ na-akọwapụta na otu ụdị akwụkwọ ikike a nwere nọmba “ma ọ bụ ụdị ọ bụla ọzọ” na-emetụta ya, ị nwere nhọrọ nke ịgbaso usoro na ọnọdụ nke ụdị ahụ akọwapụtara ma ọ bụ nke mbipute ọ bụla ọzọ ebipụtara (ọ bụghị dị ka a draft) site na Free Software Foundation. Ọ bụrụ na akwụkwọ ahụ akọwapụtaghị nọmba ụdị nke ikike a, ị nwere ike họrọ ụdị ọ bụla ebipụtara (ọ bụghị dị ka akwụkwọ) nke Free Software Foundation bipụtara.

ADDENDUM: Otu esi eji akwụkwọ ikike a maka akwụkwọ gị

Nwebiisinka (c) AFỌ aha gị. Enyere ikike ka idetuo, kesaa na/ma ọ bụ gbanwee akwụkwọ a n'okpuru usoro nke GNU Free Documentation License, Ụdị 1.2 ma ọ bụ ụdị ọ bụla ọzọ nke Free Software Foundation bipụtara; na-enweghị ngalaba na-agbanwe agbanwe, enweghị ederede mkpuchi ihu, yana enweghị ederede mkpuchi azụ. Mpempe akwụkwọ ikike a gụnyere na ngalaba akpọrọ "Ikikere Akwụkwọ N'efu GNU".

Logo

Akwụkwọ / akụrụngwa

PDF thumbnailUsoro ọrụ nkịtị
User Guide · 2026.04, Common Workflows, Workflows

Jụọ ajụjụ

Use this section to ask about setup, compatibility, troubleshooting, or anything missing from this manual.

Jụọ ajụjụ

Ask about setup, compatibility, troubleshooting, or anything missing from this manual. Name and email are optional.