Zen

Translation

English type: delimited block -
# dnf install pykickstart
26/260 · 26

Sign in to save translations.

English Friulian Actions
Start the Kickstart installation by booting the installer and using a boot option to tell the installer where to find the Kickstart file.
Scomence la instalazion di Kickstart inviant l'instaladôr e doprant une opzion di inviament par dî al instaladôr dulà cjatâ il file Kickstart.
This chapter explains these steps in detail.
Chest cjapitul al spieghe chescj passaçs tai detais.
Creating a Kickstart File
Creazion di un file Kickstart
The Kickstart file itself is a plain text file, containing keywords listed in xref:appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference], which serve as directions for the installation. Any text editor able to save files as ASCII text (such as [application]*Gedit* or [application]*vim* on Linux systems or [application]*Notepad* on Windows systems) can be used to create and edit Kickstart files.
Il file Kickstart stes al è un file di test sempliç, che al conten peraulis clâf listadis tal xref:appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Riferiment sintassi Kickstart], che a coventin tant che indicazions pe instalazion. Par creâ e modificâ i files Kickstart al è pussibil doprâ cualsisei editôrs di test che al rive a salvâ i files come tescj ASCII (come [application]*Gedit* o [application]*vim* su sistemis Linux o [application]*Notepad* su sistemis Windows).
The recommended approach to creating Kickstart files is to perform a manual installation on one system first. After the installation completes, all choices made during the installation are saved into a file named `anaconda-ks.cfg`, located in the `/root/` directory on the installed system. You can then copy this file, make any changes you need, and use the resulting configuration file in further installations.
La metodiche racomandade pe creazion di files Kickstart e je chê di eseguî prime une instalazion manuâl suntun sisteme. Dopo vê completade la instalazion, dutis lis sieltis fatis te instalazion a vignaran salvadis suntun file clamât `anaconda-ks.cfg`, posizionât te cartele `/root/` sul sisteme instalât. Tu puedis duncje copiâ chest file, fâ dutis lis modifichis necessaris e doprâ il file di configurazion risultant tes sucessivis instalazions.
When creating a Kickstart file, keep in mind the following:
Tal creâ un file Kickstart, ten iniments chest:
Lines starting with a pound sign (`#`) are treated as comments and are ignored.
Lis riis che a scomencin cuntun cancelet (`#`) a son tratadis come coments e a vegnin ignoradis.
Sections must be specified *in order*. Items within the sections do not have to be in a specific order unless otherwise specified. The correct section order is:
Al è necessari specificâ lis sezions *par ordin*. Nol è necessari che i elements dentri des sezions a sedin intun specific ordin, gjavant il câs che al sedi specificât il contrari. L'ordin just des sezions al è:
The command section which contains actual Kickstart commands and options as listed in xref:appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. Note that some commands, such as [command]#bootloader#, are mandatory, but most commands are optional.
 
The [command]#%packages# section which contains a list of packages and package groups to be installed. See xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-packages[%packages (required) - Package Selection] for details.
La sezion [command]#%packages# che e conten une liste di pachets e i grups di pachets di instalâ. Viôt xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-packages[%packages (necessaris) - Selezion pachets] pai detais.
The [command]#%pre# and [command]#%post# sections, containing a pre-installation and post-installation scripts. These two sections can be in any order and are not mandatory. See xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-preinstall[%pre (optional) - Pre-installation Script] and xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-postinstall[%post (optional) - Post-installation Script] for details.
Lis sezions [command]#%pre# e [command]#%post#, che a contegnin i scripts di pre-instalazion e post-instalazion. Chestis dôs sezions no son obligatoris e a puedin sei in cualsisei ordin. Viôt xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-preinstall[%pre (opzionâl) - Script di pre-instalazion] e xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-postinstall[%post (opzionâl) - Script di post-instalazion] pai detais.
The [command]#%packages#, [command]#%pre# and [command]#%post# sections must end with [command]#%end#, otherwise the installation program will refuse the Kickstart file. The main command section has no special ending statement.
Lis sezions [command]#%packages#, [command]#%pre# e [command]#%post# a scugnin finî cuntun [command]#%end#, in câs contrari il program di instalazion al refudarà il file Kickstart. La sezion di comant principâl (command) no à declarazions finâls speciâls.
Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation will continue. Note that if the system you are installing has no display, you will not be able to see the prompt, and the installation will appear to have failed.
La mancjance di un cualsisei element necessari al fasarà in mût che il program di instalazion al domandi al utent une rispueste par chel element, come che al sucedarès intune tipiche instalazion. Une volte dade la rispueste, la instalazion e continuarà. Fâs câs che se il sisteme dulà che tu vâs a instalâ nol à un visôr, no tu rivarâs a viodi la domande e al somearà che la instalazion no sedi lade a bon fin.
Verifying the Kickstart File
Verifiche dal file Kickstart
When creating or customizing your kickstart file, it is useful to verify that it is valid before attempting to use it in an installation. {PRODUCT} includes the [application]*ksvalidator* command line utility which can be used to do this. This tool is a part of the [package]*pykickstart* package. To install this package, execute the following command:
Tal creâ o personalizâ il to file kickstart, al è util verificâ se al è valit prime di cirî di doprâlu intune instalazion. {PRODUCT} al inclût la utilitât a rie di comant [application]*ksvalidator*, che tu puedis doprâ par fâ cheste operazion. Chest strument al è part dal pachet [package]*pykickstart*. Par instalâ chest pachet, eseguìs chest comant:
# dnf install pykickstart
# dnf install pykickstart
After installing the package, you can validate a Kickstart file using the following command:
Dopo vê instalât il pachet, tu puedis convalidâ un file Kickstart doprant chest comant:
$ [command]#ksvalidator _/path/to/kickstart.ks_#
$ [command]#ksvalidator _/path/to/kickstart.ks_#
Replace _/path/to/kickstart.ks_ with the path to the Kickstart file you want to verify.
Sostituìs _/path/to/kickstart.ks_ cul percors al file Kickstart che tu desideris verificâ.
For more information about this tool, see the `ksvalidator(1)` man page.
Par vê plui informazion su chest strument, viôt la pagjine "man" `ksvalidator(1)`.
Keep in mind that the validation tool has its limitations. The Kickstart file can be very complicated; [application]*ksvalidator* can make sure the syntax is correct and that the file does not include removed options, but it cannot guarantee the installation will be successful. It also does not attempt to validate the [command]#%pre#, [command]#%post# and [command]#%packages# sections of the Kickstart file.
Ten iniments che l'imprest di convalide al à i siei limits. Il file Kickstart al pues jessi une vore complicât; [application]*ksvalidator* al pues verificâ che la sintassi e sedi juste e che il file nol inclût opzions gjavadis, ma nol pues garantî che la instalazion e ledi a bon fin. In plui nol cirarà di convalidâ lis sezion [command]#%pre#, [command]#%post# e [command]#%packages# dal file Kickstart.
Making the Kickstart File Available
Rindi disponibil il file Kickstart
Once you create a Kickstart file, you can place it in one of the following locations:
Une volte creât un file Kickstart, tu puedis plaçâlu intune di chestis posizions:
On *removable media*, such as a DVD or USB flash drive connected to the installation system
Su *supuarts estraibii*, come DVDs o unitâts flash USB, colegâts al sisteme di instalazion
On a *hard drive* connected to the installation system
Suntun *disc fis* colegât al sisteme di instalazion
On a *network share* reachable from the installation system
Suntune *condivision di rêt* che tu puedis doprâ dal sisteme di instalazion
Normally, a Kickstart file is copied to removable media or a hard drive, or made available on the network. Placing the file in a network location complements the usual approach to Kickstart installations, which is also network-based: the system is booted using a PXE server, the Kickstart file is downloaded from a network share, and software packages specified in the file are downloaded from remote repositories.
Di norme, un file Kickstart ak ven copiât su supuart estraibil o suntun disc fis, o rindût disponibil in rêt. Il plaçâ il file intune posizion di rêt al integre la solite metodiche aes instalazions Kickstart, che e devente ancje vie rêt: il sisteme al ven inviât doprant un servidôr PXE, il file Kickstart al ven discjamât di une condivision di rêt e i pachets software indicâts tal file a vegnin discjariâts dai dipuesits lontans.
xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server] offers some additional information about preparing for a network-based installation.
xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Configurâ un servidôr pes instalazions] al ufrìs cualchi informazion in plui su cemût preparâ une instalazion vie rêt.
Starting the Kickstart Installation
Scomençâ la instalazion di Kickstart
Once you have everything ready - you have created a valid Kickstart file and you have either local boot media or a PXE server available, you can start the Kickstart installation. You need to use the [option]#inst.ks=# boot option either in the boot menu (when booting from local media), or add this option to your PXE server configuration. For information about boot options used in Kickstart installations, see xref:advanced/Boot_Options.adoc#sect-boot-options-kickstart[Kickstart Boot Options].
Une volte prontât dut - tu âs creât un file valit di Kickstart e tu âs disponibil o un supuart di inviament locâl o un servidôr PXE, tu puedis scomençâ la instalazion di Kickstart. Tu âs di doprâ la opzion di inviament [option]#inst.ks=# o tal menù di inviament (inviant di un supuart locâl) o zontant cheste opzion ae tô configurazion dal servidôr PXE. Par vê informazion su lis opzions di inviament dopradis tes instalazions di Kickstart, viôt xref:advanced/Boot_Options.adoc#sect-boot-options-kickstart[Opzions di inviament sisteme di Kickstart].

Loading…

User avatar None

String updated in the repository
# dnf install pykickstart
# dnf install pykickstart
2 years ago
User avatar None

String updated in the repository
# dnf install pykickstart
# dnf install pykickstart
2 years ago
User avatar tmtfx

Translation added
# dnf install pykickstart
# dnf install pykickstart
2 years ago
User avatar None

String updated in the repository
# dnf install pykickstart
 
2 years ago
Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English Friulian
install fedora-docs-l10n/fedora-install-guide

12590741 String information

Source string description
type: delimited block -
Flags
no-wrap
Source string location
./pages/advanced/Kickstart_Installations.adoc:65
String age
2 years ago
Last updated
a year ago
Source string age
3 years ago
Translation file
po/fur/f34/pages/advanced/Kickstart_Installations.po, string 25