UYUNI Common Workflows User Guide

UYUNI Common Workflows

Àsọyé

Abala 1

Wọpọ Workflows

Ọdun 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.

Ọjọ Atẹjade2026-04-29

Onibara Onboarding

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

Lo Ọran

Ise sise yii fihan ọ bi o ṣe le wọ inu alabara si olupin Uyuni rẹ.

Onibara gbọdọ nṣiṣẹ ẹrọ ṣiṣe Linux ti o ni atilẹyin. Fun atokọ ti awọn eto alabara atilẹyin, wo Client-configuration › Supported-features.

Eyi jẹ ọkan ninu awọn iṣẹ-ṣiṣe akọkọ ti o nilo lati ṣe nigbati o ba ṣeto Uyuni fun igba akọkọ, ati pe iwọ yoo ni lati ṣe ni ọpọlọpọ igba diẹ sii bi o ṣe nlo ọja naa.

Abajade

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. Lẹhinna o le lo Uyuni lati ṣakoso alabara naa.

Igbaradi

Ṣaaju ki o to bẹrẹ, o yẹ ki o ti ni:

• Uyuni Server ti fi sori ẹrọ, ti o le wọle si lilo awọn Web UI.
• Ẹrọ alabara ti o ni ẹrọ ti a fi sori ẹrọ, eyiti o le wọle si kọja nẹtiwọọki ti olupin Uyuni rẹ wa lori, ni lilo SSH.
• Awọn ṣiṣe alabapin ti o yẹ lati http://scc.suse.com fun awọn ọja ti o nlo.

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.

Igbesẹ-nipasẹ-Igbese Awọn ilana Sisẹ Ṣiṣẹ

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

1. Lori alabara, ni aṣẹ aṣẹ, ṣafihan orukọ olupin lọwọlọwọ:
   hostname -f
   O ṣee ṣe pe aṣẹ yii yoo da aṣiṣe pada, tabi ṣafihan nkan bi localhost.
2. Ṣeto orukọ ogun titun kan. Orukọ ogun tuntun rẹ yẹ ki o ni orukọ subdomain ati nitorinaa pẹlu o kere ju awọn akoko meji. Ninu example, we are using client1.MLM.example
   hostnamectl set-hostname client1.MLM.example
3. Ṣayẹwo pe iyipada rẹ ṣaṣeyọri:
   hostnamectl
4. Open YaST and navigate to Network Services › Hostnames. Edit the hostname to match the one you just
   set, and click [O DARA].
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. Ṣayẹwo pe iyipada naa ṣaṣeyọri:
   hostname -f
   This command should return your new FQDN

Ilana: Mura awọn ikanni sọfitiwia sori olupin Uyuni

1. Ninu Uyuni Web UI, lilö kiri si Admin › Setup Wizard.
2. Ninu taabu Awọn iwe-ẹri Ajo, rii daju pe o ti tẹ awọn iwe-ẹri Ile-iṣẹ Onibara SUSE rẹ sii, ati pe o ti jẹri ni deede.
3. Ninu taabu Awọn ọja, rii daju pe katalogi ọja ti ni imudojuiwọn ni kikun:
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 [Fi awọn ọja kun ]:
5. Duro fun awọn ikanni ọja lati muṣiṣẹpọ ni kikun. Ti o da lori awọn ọja ti o yan, eyi le gba akoko pipẹ.

Ilana: Ṣẹda bọtini imuṣiṣẹ

1. Ninu Uyuni Web UI, lilö kiri si Awọn ọna ṣiṣe › Activation Keys, ki o si tẹ [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 [Ṣẹda bọtini imuṣiṣẹ].

Ilana: Bootstrap onibara

1. Ninu Uyuni Web UI, lilö kiri si Systems › Bootstrapping.
2. Tẹ orukọ agbalejo naa ki o pese awọn iwe-ẹri ijẹrisi fun alabara ti o fẹ lati wọ inu ọkọ, ki o yan bọtini imuṣiṣẹ. Tẹ [Bootstrap]:
3. Lilö kiri si Systems › System List to manage your new client

Awọn koko-ọrọ ti o jọmọ

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

Imudojuiwọn Awọn alabara Lilo Awọn iṣe Loorekoore

Abala 3

Ṣiṣan iṣẹ ṣiṣe fihan bi o ṣe le ṣe imudojuiwọn adaṣe awọn alabara ti o forukọsilẹ ni Uyuni ni lilo awọn iṣe loorekoore.

Use case / Situation

Imudojuiwọn adaṣe ti awọn alabara jẹ anfani nigbati:

• imudojuiwọn ti kan ti o tobi nọmba ti ibara ti wa ni fe
• iṣiṣẹ iṣẹ ko yẹ ki o tun ṣe gbogbo ipaniyan
• ferese itọju igbẹhin kan wa.

Abajade / Opinnu

Ipari aṣeyọri ti iṣan-iṣẹ iṣẹ yii ni ibamu ati ipo atilẹyin.

Igbaradi

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

Lati ṣe imudojuiwọn alabara awọn igbesẹ meji ni o nilo. Igbesẹ kẹta jẹ iyan ṣugbọn a gbaniyanju gaan lati pari ilana imudojuiwọn naa.

Ilana: Creating a recurring action to update Salt itself

1. Bi example, a ṣẹda awọn igbese lati mu Iyọ ara bi a loorekoore igbese fun gbogbo awọn ọna šiše ni ajo. Ninu Uyuni Web UI, lilö kiri si Home › My Organization › Recurring Actions ki o si tẹ [Create].
2. Select Action Type Aṣa Ìpínlẹ̀ and enter a Schedule Name like update salt .
3. Yan iṣeto kan. Fun example, Weekly: Wednesday, 9:00 am .
4. Fi ipo imudojuiwọn-iyọ silẹ nipa yiyan apoti.
5. Tẹ [Save Changes ] to save the action.
6. You can edit the execution order of the states if needed. Click [Jẹrisi] to confirm the order.
7. Tẹ [Create Schedule] to save the action.

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

1. Bi example we create the action to apply all updates as a recurring action for a system group called infra-iṣẹ. Ninu 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. Yan Iṣeto kan. Fun 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 fun asiko by selecting the checkboxes. To perform a reboot afterwards you can also add reboot or reboot if needed.
6. Save the action by clicking [Fipamọ awọn iyipada ].
7. You can edit the execution order of the states. The order should be util. syn call, certs, channels, fun asiko and finally reboot or reboot if needed if chosen. Click [Jẹrisi] to store the order.
8. Tẹ [Create Schedule] to save the action.

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

1. Bi example, we create the action to apply the high state for the same group which was fully updated before. In the Uyuni Web UI, lilö kiri si Systems › System Groups and click infra-services.
2. Go to Recurring Actions and click [Create].
3. Select Action Type Ipo giga and enter a Schedule Name like high state .
4. Yan Iṣeto kan. Fun example, Weekly: Wednesday, 10:30 am . Again, keep enough time between this action and the full-system-update action.
5. Tẹ [Create Schedule] to save the action.

Background information on up-to-date state

1. Awọn fun asiko 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

Awọn koko-ọrọ ti o jọmọ

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

Isakoso iṣeto ni

Abala 4

O le lo iṣeto ni files ati awọn ikanni lati ṣakoso iṣeto ni fun awọn alabara rẹ, dipo atunto alabara kọọkan pẹlu ọwọ. Ise sise yii fihan ọ bi o ṣe le lo Uyuni Web UI lati ṣẹda iṣeto ni iṣakoso aarin file, fi o si kan ni ose, ati ki o waye iṣeto ni.

Lo Ọran

Ti o ba n ṣakoso ọpọlọpọ awọn alabara, o ṣee ṣe ko fẹ lati lo awọn eto iṣeto ni ọwọ si ọkọọkan wọn ni titan. Awọn ikanni iṣeto ni a lo lati ṣeto iṣeto ni files. O le ṣe alabapin awọn alabara si awọn ikanni atunto, ati mu iṣeto ṣiṣẹ files bi beere.

Abajade

Nigbati o ba ti pari iṣan-iṣẹ yii, iwọ yoo ni ikanni iṣeto kan ti o ni iṣeto ni file, ti yan awọn alabara si ikanni, ati lo iṣeto ni aṣeyọri.

Igbaradi

Ṣaaju ki o to bẹrẹ, o yẹ ki o ti ni:

• Uyuni Server ti fi sori ẹrọ, ti o le wọle si lilo awọn Web UI.
• O kere ju alabara kan ti forukọsilẹ si olupin rẹ.
• Awọn ṣiṣe alabapin ti o yẹ lati http://scc.suse.com fun awọn ọja ti o nlo.

Sisan-iṣẹ yii nlo iṣeto iṣakoso aarin file and a Salt state. For more information about the different ways to manage configuration, see Client-configuration › Configuration-management.

Igbese-nipasẹ-Igbese Awọn ilana Sisẹ-iṣẹ

Ilana: Ṣẹda ikanni Iṣeto Tuntun ati File

1. Ninu Uyuni Web UI, lilö kiri si Configuration › Channels ki o si tẹ [Create State Channel].
2. Tẹ orukọ kan, aami, ati apejuwe fun iṣeto rẹ file, ki o si tẹ awọn awọn akoonu ti rẹ iṣeto ni file. Ohun example that you can copy is at the end of this section.

Ilana: Fi awọn onibara si ikanni iṣeto ni

1. Ninu Uyuni Web UI, lilö kiri si Systems › Systems List and select the client you want to assign to your configuration channel.
2. Lilö kiri si taabu Iṣeto. Ni awọn guimenu: Iṣeto ni Loriview apakan, tẹ [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 ] lati pari.

Ilana: Waye Iṣeto si Onibara Rẹ

1. Ninu Uyuni Web UI, lilö kiri si 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

Ipinle SLS fun Titọju Awọn alabara Imudojuiwọn

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

Awọn koko-ọrọ ti o jọmọ

• For more information about configuration management, see Client-configuration › Configuration management.
• Fun alaye siwaju sii nipa SLS files, wo: https://docs.saltproject.io/en/latest/topics/tutorials/starting_states.html.

Akoonu Lifecycle Management

Abala 5

Ti o ba n ṣakoso ọpọlọpọ awọn alabara ati pe o nilo lati lo awọn idii adani si wọn, o le lo iṣakoso igbesi aye akoonu (CLM) lati ṣakoso awọn idii rẹ. CLM gba ọ laaye lati ṣe akanṣe ati idanwo awọn idii ṣaaju ṣiṣe imudojuiwọn awọn alabara iṣelọpọ. O tun wulo ti o ba nilo lati lo awọn imudojuiwọn lakoko window itọju to lopin.

Lo Ọran

Isakoso igbesi aye akoonu gba ọ laaye lati yan awọn ikanni sọfitiwia bi awọn orisun, ṣatunṣe wọn bi o ṣe nilo fun agbegbe rẹ, ati idanwo wọn daradara ṣaaju fifi sori awọn alabara iṣelọpọ rẹ. O le lo CLM lati ṣakoso awọn ikanni sọfitiwia rẹ lati idagbasoke, nipasẹ idanwo, ati yiyi awọn ayipada jade si awọn alabara rẹ.

Abajade

Nigbati o ba ti pari iṣan-iṣẹ yii, iwọ yoo ni iṣẹ akanṣe igbesi aye akoonu ti a ṣeto. Iwọ yoo ti ṣẹda iṣẹ akanṣe CLM ipilẹ kan, ati gbega nipasẹ igbesi aye rẹ.

Awọn igbaradi

Ṣaaju ki o to bẹrẹ, o yẹ ki o ti ni:

• Uyuni Server deployed, and accessible using the Web UI.
• Ẹrọ alabara ti o ni ẹrọ ti a fi sori ẹrọ, eyiti o le wọle si kọja nẹtiwọọki ti olupin Uyuni rẹ wa lori, ni lilo SSH.
• Awọn ṣiṣe alabapin ti o yẹ lati http://scc.suse.com fun awọn ọja ti o nlo.

Igbesẹ-nipasẹ-Igbese Awọn ilana Sisẹ Ṣiṣẹ

Ilana: Ṣẹda titun CLM Project

1. Ninu Uyuni Web UI, lilö kiri si 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 [Fipamọ] to return to the project page.
3. Fi apakan Awọn Ajọ silẹ ni ofifo fun bayi, a kii yoo lo wọn ni iṣaaju yiiample. O le ṣafikun awọn asẹ nigbamii ti o ba nilo lati.
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. Tẹ [Kọ] to build version 1 of your project:

Ilana: Fi awọn onibara ranṣẹ

1. Lilö kiri si Systems › System List, select the client to assign, and go to the Software › Software Channels taabu.
2. In the Base Channel section, select the CLM project and environment you want to assign the client to.
   Fun 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. Tẹ [Itele] to assign the client.

Ilana: Igbelaruge Awọn Ayika

1. Ninu Uyuni Web UI, lilö kiri si 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.

Awọn koko-ọrọ ti o jọmọ

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

Customize Apache Configuration

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

Lo irú

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.

Abajade

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

Igbaradi

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 (fun example, custom_ tuning. conf) and add your required Apache directives.
5. Ni kete ti o ti fipamọ rẹ file, exit the container with command:
   exit
6. Restart the Uyuni services to apply the changes:
   mgradm restart

Ọja Igbesoke nipasẹ Web UI

Abala 7

Ti o ba fẹ ṣe igbesoke idii alabara ile-iṣẹ SUSE Linux ti o forukọsilẹ si ẹya ọja tuntun, o le ṣee ṣe boya lori laini aṣẹ tabi nipasẹ Web UI.

Iwe yii ṣapejuwe ati ṣapejuwe ni apejuwe awọn igbesoke ọja nipa lilo awọn Web UI.

Awọn ẹya ọja ti a lo ko ṣe afihan awọn ẹya tuntun ti o wa. Wọn lo fun awọn idi apejuwe nikan. Bi example, awọn wọnyi ilana apejuwe awọn igbesoke to version 15 SP5 lati ati agbalagba version 15. Ti o ba ti wa ni ìfọkànsí kan ti o yatọ version, yan awọn ti o baamu awọn ikanni ati awọn ẹya.

Ilana: Igbegasoke Ọja si Ẹya Tuntun Lilo Web UI

1. Wọle si Uyuni Web UI and navigate to Admin › Setup Wizard › Products and search for SUSE Linux Enterprise Server 15 SP5 x86_64.
2. Yan awọn ikanni iṣeduro.
3. Tẹ [Add Products ].
4. Lilö kiri si Systems › Registered client › Software › Product Migration. You will see the targets available for that registered client.
5. Yan SUSE Linux Enterprise Server 15 SP5 x86_64. Eleyi yoo faagun siwaju.
6. Yan Ikanni Ipilẹ Àkọlé bi SLE-Ọja-SLES15-SP5-Pool fun x86_64. Jeki Gba Ayipada ataja laiṣayẹwo.
7. Tẹ [Schedule Migration]. The message will be highlighted It is better to do a dry run first so continuing with dry run first.
8. Tẹ [Ṣiṣe gbigbẹ] and check the status of the simulation in Events › History. You should see a return code 0 indicating a successful dry run.
9. Tẹ [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. Lori Uyuni Web UI side, verify the successfully completed product upgrade by going to Systems › Registered client › Details.
12. Ni ẹgbẹ alabara o le jẹrisi rẹ nipa ṣiṣe:
    cat /etc/os-release
13. Ijade yoo dabi:

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

Iwe-aṣẹ Iwe-aṣẹ Ọfẹ GNU

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

PRAMBLE

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.

A ti ṣe apẹrẹ Iwe-aṣẹ yii lati le lo fun awọn iwe afọwọkọ fun sọfitiwia ọfẹ, nitori sọfitiwia ọfẹ nilo iwe ọfẹ: eto ọfẹ yẹ ki o wa pẹlu awọn iwe afọwọkọ ti n pese awọn ominira kanna ti sọfitiwia naa ṣe. Ṣugbọn Iwe-aṣẹ yii ko ni opin si awọn itọnisọna sọfitiwia; o le ṣee lo fun eyikeyi iṣẹ ọrọ, laibikita koko-ọrọ tabi boya o ti gbejade bi iwe ti a tẹ. A ṣeduro Iwe-aṣẹ ni akọkọ fun awọn iṣẹ ti idi wọn jẹ itọnisọna tabi itọkasi.

Ohun elo ATI itumo

Iwe-aṣẹ yii kan si eyikeyi iwe afọwọkọ tabi iṣẹ miiran, ni eyikeyi alabọde, ti o ni akiyesi kan ti a fi silẹ nipasẹ ẹniti o ni aṣẹ lori ara ti o sọ pe o le pin labẹ awọn ofin ti Iwe-aṣẹ yii. Iru akiyesi bẹ n funni ni agbaye, iwe-aṣẹ ọfẹ ọfẹ ti ọba, ailopin ni iye akoko, lati lo iṣẹ yẹn labẹ awọn ipo ti a sọ ninu rẹ. “Iwe-ipamọ”, ni isalẹ, tọka si iru iwe afọwọkọ tabi iṣẹ eyikeyi. Eyikeyi ọmọ ẹgbẹ ti gbogbo eniyan jẹ iwe-aṣẹ, ati pe a pe ni “iwọ”. O gba iwe-aṣẹ ti o ba daakọ, yipada tabi pinpin iṣẹ naa ni ọna ti o nilo igbanilaaye labẹ ofin aṣẹ-lori.

“Ẹya ti a Ṣatunṣe” ti Iwe naa tumọ si iṣẹ eyikeyi ti o ni Iwe-ipamọ tabi ipin kan ninu rẹ, boya daakọ ni iṣoju, tabi pẹlu awọn iyipada ati/tabi tumọ si ede miiran.

“Apakan Atẹle” jẹ afikun ti a npè ni tabi apakan ọrọ iwaju ti Iwe-ipamọ ti o ṣe iyasọtọ pẹlu ibatan ti awọn olutẹjade tabi awọn onkọwe Iwe naa si koko-ọrọ gbogbogbo Iwe-ipamọ naa (tabi si awọn ọran ti o jọmọ) ati pe ko ni ohunkohun ti o le ṣubu taara laarin ti ìwò koko. (Nitorinaa, ti Iwe-ipamọ naa ba wa ni apakan iwe-ẹkọ ti mathimatiki, Abala Atẹle kan le ma ṣe alaye eyikeyi mathematiki.) Ibasepo naa le jẹ ọrọ ti itan-akọọlẹ pẹlu koko-ọrọ tabi pẹlu awọn ọrọ ti o jọmọ, tabi ti ofin, iṣowo, imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-imọ-ọrọ. tabi ipo oselu nipa wọn.

Awọn “Awọn apakan Ayipada” jẹ awọn apakan Atẹle kan ti awọn akọle wọn jẹ apẹrẹ, gẹgẹ bi awọn ti Awọn apakan Ayipada, ninu akiyesi ti o sọ pe Iwe-ipamọ ti tu silẹ labẹ Iwe-aṣẹ yii. Ti abala kan ko ba ni ibamu si asọye loke ti Atẹle lẹhinna ko gba ọ laaye lati ṣe apẹrẹ bi Alaiyipada. Iwe-ipamọ le ni awọn apakan Ayipada odo. Ti Iwe naa ko ba ṣe idanimọ eyikeyi Awọn apakan Ayipada lẹhinna ko si.

Awọn “Awọn ọrọ Ideri” jẹ awọn ọrọ kukuru kan ti a ṣe akojọ, bi Awọn ọrọ Ideri Iwaju tabi Awọn ọrọ Ideri, ninu akiyesi ti o sọ pe Iwe-ipamọ ti tu silẹ labẹ Iwe-aṣẹ yii. Ọrọ Ideri Iwaju le jẹ pupọ julọ awọn ọrọ 5, ati pe Ọrọ Ideri Afẹyinti le jẹ awọn ọrọ 25 julọ.

Ẹda “Sihan” ti Iwe naa tumọ si ẹda ti o le ka ẹrọ, ti o ṣojuuṣe ni ọna kika ti sipesifikesonu wa fun gbogbo eniyan, ti o dara fun atunyẹwo iwe ni taara pẹlu awọn olootu ọrọ jeneriki tabi (fun awọn aworan ti o ni awọn piksẹli) kun jeneriki awọn eto tabi (fun awọn iyaworan) diẹ ninu awọn olootu iyaworan ti o wa ni ibigbogbo, ati pe o dara fun titẹ sii si awọn oluka ọrọ tabi fun itumọ adaṣe si ọpọlọpọ awọn ọna kika ti o dara fun titẹ sii si awọn oluka ọrọ. Ẹda ti a ṣe ni bibẹẹkọ Sihin file ọna kika eyiti isamisi, tabi isansa ti isamisi, ti ṣeto lati dena tabi ṣe irẹwẹsi iyipada ti o tẹle nipasẹ awọn oluka kii ṣe Sihin. Aworan ọna kika kii ṣe Sihin ti o ba lo fun eyikeyi idaran ti ọrọ. Ẹda ti kii ṣe “Transparent” ni a pe ni “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. ExampAwọn ọna kika aworan sihin pẹlu PNG, XCF ati JPG. Awọn ọna kika opaque pẹlu awọn ọna kika ohun-ini ti o le ka ati ṣatunkọ nikan nipasẹ awọn olutọpa ọrọ ti ara, SGML tabi XML eyiti DTD ati/tabi awọn irinṣẹ sisẹ ko wa ni gbogbogbo, ati HTML ti a ṣe ipilẹṣẹ ẹrọ, PostScript tabi PDF ti a ṣe nipasẹ diẹ ninu awọn olutọpa ọrọ fun o wu idi nikan.

“Oju-iwe akọle” tumọ si, fun iwe titẹjade, oju-iwe akọle funrararẹ, pẹlu iru awọn oju-iwe atẹle ti o nilo lati mu, ni ilodi si, ohun elo Iwe-aṣẹ nilo lati han ni oju-iwe akọle. Fun awọn iṣẹ ni awọn ọna kika eyiti ko ni oju-iwe akọle eyikeyi bii iru, “Oju-iwe Akọle” tumọ si ọrọ ti o sunmọ ifarahan olokiki julọ ti akọle iṣẹ naa, ṣaaju ibẹrẹ ti ara ti ọrọ naa.

Apa kan “Ti o ni ẹtọ XYZ” tumọ si ipin ti a npè ni Iwe-ipamọ ti akọle boya jẹ XYZ gangan tabi ni XYZ ninu akomo ti o tẹle ọrọ ti o tumọ XYZ ni ede miiran. (Nibi XYZ duro fun orukọ apakan kan pato ti a mẹnuba ni isalẹ, gẹgẹbi “Awọn Ijẹwọgbigba”, “Awọn iyasọtọ”, “Awọn ifọwọsi”, tabi “Itan-akọọlẹ”) Lati “Ṣitọju Akọle” ti iru apakan nigbati o ba yipada Iwe naa tumọ si pe o jẹ apakan kan “Ti o ni ẹtọ XYZ” ni ibamu si itumọ yii.

Iwe naa le pẹlu Awọn AlAIgBA Atilẹyin ọja lẹgbẹẹ akiyesi eyiti o sọ pe Iwe-aṣẹ yii kan Iwe-ipamọ naa. Awọn idawọle Atilẹyin ọja wọnyi ni a gba pe o wa pẹlu itọka si ni Iwe-aṣẹ yii, ṣugbọn niti awọn iwe-ẹri aibikita: eyikeyi itumọ miiran ti Awọn AlAIgBA Atilẹyin ọja le ni ofo ati pe ko ni ipa lori itumọ Iwe-aṣẹ yii.

ÌṢÀKỌ̀ Ọ̀RỌ̀

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.

O tun le ya awọn ẹda, labẹ awọn ipo kanna ti a sọ loke, ati pe o le ṣafihan awọn ẹda ni gbangba.

didaakọ ni opoiye

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.

Ti awọn ọrọ ti a beere fun boya ideri ba pọ ju lati baamu ni ilodi si, o yẹ ki o fi awọn akọkọ ti a ṣe akojọ (bii ọpọlọpọ bi o ṣe yẹ) sori ideri gangan, ki o tẹsiwaju iyokù si awọn oju-iwe ti o wa nitosi.

Ti o ba ṣe atẹjade tabi kaakiri awọn ẹda Opaque ti nọmba Iwe-ipamọ diẹ sii ju 100, o gbọdọ pẹlu pẹlu ẹda ti o ṣee ṣe kika ẹrọ pẹlu ẹda Opaque kọọkan, tabi sọ sinu tabi pẹlu Opaque kọọkan daakọ ipo nẹtiwọọki kọnputa lati eyiti nẹtiwọọki gbogbogbo- lilo gbogbo eniyan ni aye lati ṣe igbasilẹ nipa lilo awọn ilana nẹtiwọọki boṣewa ti gbogbo eniyan ni pipe ẹda Sihin ti Iwe naa, laisi ohun elo ti a ṣafikun. Ti o ba lo aṣayan ti o kẹhin, o gbọdọ gbe awọn igbesẹ ti oye, nigbati o bẹrẹ pinpin awọn ẹda Opaque ni opoiye, lati rii daju pe ẹda Transparent yii yoo wa ni wiwọle si ni ipo ti a sọ titi o kere ju ọdun kan lẹhin igba ikẹhin ti o pin kaakiri. Ẹda komo (taara tabi nipasẹ awọn aṣoju tabi awọn alatuta) ti ẹda yẹn si gbogbo eniyan.

O beere, ṣugbọn kii ṣe dandan, pe o kan si awọn onkọwe Iwe naa daradara ṣaaju pinpin nọmba nla ti awọn ẹda, lati fun wọn ni aye lati fun ọ ni ẹya imudojuiwọn ti Iwe naa.

Awọn Atunṣe

O le daakọ ati pinpin Ẹya Iyipada ti Iwe naa labẹ awọn ipo ti awọn apakan 2 ati 3 loke, ti o ba jẹ pe o tu Ẹya ti Atunse silẹ labẹ Iwe-aṣẹ ni deede, pẹlu ẹya ti Atunṣe ti n kun ipa ti Iwe naa, nitorinaa pinpin iwe-aṣẹ ati iyipada ti Ẹ̀dà Títúnṣe sí ẹnikẹ́ni tí ó ní ẹ̀dà kan. Ní àfikún, o gbọ́dọ̀ ṣe àwọn nǹkan wọ̀nyí nínú Ẹ̀dà Títúnṣe:

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

Ti Ẹya ti Atunṣe pẹlu awọn apakan ọrọ iwaju tuntun tabi awọn ohun elo ti o pege bi Awọn apakan Atẹle ti ko si ni ohun elo ti a daakọ ninu Iwe-ipamọ naa, o le ni aṣayan rẹ yan diẹ ninu tabi gbogbo awọn apakan wọnyi bi aiyipada. Lati ṣe eyi, ṣafikun awọn akọle wọn si atokọ ti Awọn apakan Ayipada ninu akiyesi iwe-aṣẹ Ẹya ti Atunṣe. Awọn akọle wọnyi gbọdọ jẹ iyatọ si eyikeyi awọn akọle apakan miiran.

O le ṣafikun apakan kan ti o ni ẹtọ “Awọn ifarabalẹ”, ti o ba jẹ pe ko ni nkankan bikoṣe awọn ifọwọsi ti Ẹya Titunse rẹ nipasẹ awọn ẹgbẹ oriṣiriṣi—fun ex.ample, awọn gbólóhùn ti ẹlẹgbẹ review tabi pe ọrọ naa ti fọwọsi nipasẹ ajọ kan gẹgẹbi itumọ aṣẹ ti boṣewa kan.

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.

Awọn onkọwe (awọn) ati olutẹwe (awọn) Iwe naa ko ṣe nipasẹ Iwe-aṣẹ yii fun ni aṣẹ lati lo awọn orukọ wọn fun ikede fun tabi lati fi idi rẹ mulẹ tabi tọkasi ifọwọsi eyikeyi ti Atunṣe Ẹya.

APAPO awọn iwe aṣẹ

O le ṣajọpọ Iwe-ipamọ naa pẹlu awọn iwe aṣẹ miiran ti a tu silẹ labẹ Iwe-aṣẹ yii, labẹ awọn ofin ti a ṣalaye ni apakan 4 loke fun awọn ẹya ti o yipada, ti o ba jẹ pe o ṣafikun ni apapọ gbogbo Awọn apakan Ayipada ti gbogbo awọn iwe aṣẹ atilẹba, ti ko yipada, ati ṣe atokọ gbogbo wọn bi Awọn apakan Ayipada ti iṣẹ apapọ rẹ ninu akiyesi iwe-aṣẹ rẹ, ati pe o tọju gbogbo Awọn AlAIgBA Atilẹyin ọja wọn.

Iṣẹ apapọ nilo ẹda kan ti Iwe-aṣẹ yii nikan ni, ati pe ọpọlọpọ awọn apakan Ayipada Ayipada le paarọ rẹ pẹlu ẹda kan. Ti o ba wa ọpọlọpọ Awọn apakan Ayipada pẹlu orukọ kanna ṣugbọn awọn akoonu ti o yatọ, jẹ ki akọle iru apakan kọọkan jẹ alailẹgbẹ nipa fifi kun ni ipari rẹ, ni awọn akọmọ, orukọ ti onkọwe atilẹba tabi olutẹjade apakan yẹn ti a ba mọ, tabi bibẹẹkọ a oto nọmba. Ṣe atunṣe kanna si awọn akọle apakan ninu atokọ ti Awọn apakan Ayipada ninu akiyesi iwe-aṣẹ ti iṣẹ apapọ.

Ni apapọ, o gbọdọ darapọ awọn apakan eyikeyi ti o ni ẹtọ “Itan-akọọlẹ” ni ọpọlọpọ awọn iwe atilẹba, ti o ṣẹda apakan kan ti o ni ẹtọ “Itan-akọọlẹ”; Bakanna darapọ awọn apakan eyikeyi ti o ni ẹtọ “Awọn Ijẹwọ”, ati eyikeyi awọn apakan ti o ni ẹtọ “Awọn iyasọtọ”. O gbọdọ pa gbogbo awọn apakan ti o ni ẹtọ ni "Awọn idaniloju".

Awọn akojọpọ ti awọn iwe aṣẹ

O le ṣe ikojọpọ ti Iwe-ipamọ ati awọn iwe aṣẹ miiran ti a tu silẹ labẹ Iwe-aṣẹ yii, ki o rọpo awọn ẹda kọọkan ti Iwe-aṣẹ yii ni oriṣiriṣi awọn iwe aṣẹ pẹlu ẹda kan ti o wa ninu ikojọpọ, ti o pese pe o tẹle awọn ofin Iwe-aṣẹ yii fun didaakọ awọn iwe aṣẹ kọọkan ni gbogbo awọn ọna miiran.

O le yọ iwe-ipamọ kan jade lati iru ikojọpọ kan, ki o pin kaakiri ni ẹyọkan labẹ Iwe-aṣẹ yii, ti o ba fi ẹda Iwe-aṣẹ yii sii sinu iwe ti o jade, ki o tẹle Iwe-aṣẹ yii ni gbogbo awọn ọna miiran nipa didakọ iwe yẹn ni ilodisi.

IPAPO PẸLU IṢẸ AWỌN NIPA

Akopọ Iwe-ipamọ tabi awọn itọsẹ rẹ pẹlu awọn iwe aṣẹ lọtọ ati ominira tabi awọn iṣẹ, ninu tabi lori iwọn ibi ipamọ tabi alabọde pinpin, ni a pe ni “apapọ” ti o ba jẹ pe aṣẹ-lori ti o waye lati akopọ ko ni lo lati ṣe idinwo awọn ẹtọ ofin ti awọn olumulo akopo ju ohun ti awọn ẹni kọọkan ṣiṣẹ laye. Nigbati Iwe-ipamọ naa ba wa ninu apapọ, Iwe-aṣẹ yii ko kan awọn iṣẹ miiran ninu apapọ eyiti kii ṣe awọn iṣẹ itọsẹ ti ara wọn ti Iwe naa.

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.

ITUMO

Itumọ jẹ iru iyipada, nitorinaa o le pin awọn itumọ ti Iwe naa labẹ awọn ofin ti apakan 4. Rirọpo Awọn apakan Ayipada pẹlu awọn itumọ nilo igbanilaaye pataki lati ọdọ awọn ti o ni ẹtọ lori ara wọn, ṣugbọn o le ni awọn itumọ ti diẹ ninu tabi gbogbo Awọn apakan Ayipada ni afikun si awọn ẹya atilẹba ti Awọn apakan Ayipada wọnyi. O le ni itumọ Iwe-aṣẹ yii, ati gbogbo awọn akiyesi iwe-aṣẹ ti o wa ninu Iwe-ipamọ naa, ati Awọn Idasilẹ Atilẹyin ọja eyikeyi, ti o ba jẹ pe o tun pẹlu ẹya Gẹẹsi atilẹba ti Iwe-aṣẹ yii ati awọn ẹya atilẹba ti awọn akiyesi ati awọn ailabo wọnyẹn. Bí èdèkòyédè bá wáyé láàárín ìtúmọ̀ àti ẹ̀yà ìpilẹ̀ṣẹ̀ ìwé àṣẹ yìí tàbí àfiyèsí tàbí àjálù, ẹ̀yà ìpilẹ̀ṣẹ̀ yóò borí.

Ti apakan kan ninu Iwe-ipamọ naa ba ni ẹtọ “Awọn Ijẹrisi”, “Awọn iyasọtọ”, tabi “Itan-akọọlẹ”, ibeere (apakan 4) lati Tọju Akọle rẹ (apakan 1) yoo nilo deede iyipada akọle gangan.

TERMINATION

O le ko daakọ, yipada, sublicense, tabi kaakiri iwe ayafi bi a ti pese taara fun labẹ iwe-aṣẹ. Eyikeyi igbiyanju miiran lati daakọ, yipada, fi iwe-aṣẹ tabi pinpin Iwe-ipamọ jẹ ofo, ati pe yoo fopin si awọn ẹtọ rẹ laifọwọyi labẹ Iwe-aṣẹ yii. Sibẹsibẹ, awọn ẹgbẹ ti o ti gba awọn ẹda, tabi awọn ẹtọ, lati ọdọ rẹ labẹ Iwe-aṣẹ yii kii yoo fopin si awọn iwe-aṣẹ wọn niwọn igba ti iru awọn ẹgbẹ ba wa ni ibamu ni kikun.

Awọn atunwo ọjọ iwaju ti iwe-aṣẹ YI

Ipilẹ Software Ọfẹ le ṣe atẹjade tuntun, awọn ẹya ti a tunṣe ti Iwe-aṣẹ Iwe-aṣẹ Ọfẹ GNU lati igba de igba. Iru awọn ẹya tuntun yoo jọra ni ẹmi si ẹya ti o wa, ṣugbọn o le yatọ ni awọn alaye lati koju awọn iṣoro tabi awọn ifiyesi tuntun. Wo http://www.gnu.org/copyleft/.

Ẹya kọọkan ti Iwe-aṣẹ ni a fun ni nọmba ẹya iyatọ. Ti Iwe-ipamọ naa ba ṣalaye pe ẹya nọmba kan pato ti Iwe-aṣẹ “tabi eyikeyi ẹya nigbamii” kan si, o ni aṣayan lati tẹle awọn ofin ati ipo boya ti ẹya pato tabi ti eyikeyi ti ikede nigbamii ti o ti tẹjade (kii ṣe bi a osere) nipasẹ Free Software Foundation. Ti Iwe-ipamọ naa ko ba pato nọmba ẹya ti Iwe-aṣẹ yii, o le yan ẹya eyikeyi ti a gbejade lailai (kii ṣe bi yiyan) nipasẹ Foundation Software Ọfẹ.

ÀFIKÚN: Bii o ṣe le lo Iwe-aṣẹ yii fun awọn iwe aṣẹ rẹ

Aṣẹ-lori-ara (c) ODUN ORUKO RẸ. A fun ni igbanilaaye lati daakọ, kaakiri ati/tabi ṣe atunṣe iwe yii labẹ awọn ofin ti Iwe-aṣẹ Iwe-aṣẹ Ọfẹ GNU, Ẹya 1.2 tabi eyikeyi ẹya nigbamii ti a tẹjade nipasẹ Foundation Software Ọfẹ; laisi Awọn apakan Ayipada, ko si Awọn ọrọ Ideri Iwaju, ati pe ko si Awọn ọrọ Ideri Afẹyinti. Ẹda iwe-aṣẹ naa wa ninu apakan ti o ni ẹtọ ni “Iwe-aṣẹ Iwe-aṣẹ Ọfẹ GNU”.