uyuni/docs client-configuration master — Czech @ openSUSE Weblate: Autoinstallable Distributions

Translation

Source change

English [[build-iso-with-mkisofs]] == Build a RedHat ISO Image With mkisofs You can use [command]``mkisofs`` to create a bootable ISO image to be used by the target system for installation of a {redhat} system. When the system is rebooted or switched on, it boots from the image, loads the {kickstart} configuration from your {productname}, and installs {rhel} according to the {kickstart} profile. .Procedure: Building a Bootable ISO With mkisofs . Copy the contents of [path]``/isolinux`` from the first CD-ROM of the target distribution. . Edit the [path]``isolinux.cfg`` file to default to 'ks'. Change the 'ks' section to read: + ---- label ks kernel vmlinuz append text ks=`url` initrd=initrd.img lang= devfs=nomount #. ramdisk_size=16438 `ksdevice` ---- + IP address-based {kickstart} URLs look like this: + ---- http://`my.manager.server`/kickstart/ks/mode/ip_range ---- + The {kickstart} distribution defined via the IP range should match the distribution from which you are building, to prevent errors occurring. . OPTIONAL: If you want to use the [replaceable]``ksdevice``, it looks like this: + ---- ksdevice=eth0 ---- + It is possible to change the distribution for a Kickstart profile within a family, such as {rhel} AS 4 to {rhel} ES 4, by specifying the new distribution label. Note that you cannot move between versions (4 to 5) or between updates (U1 to U2). . Customize [path]``isolinux.cfg`` further as required. For example, you can add multiple options, different boot messages, or shorter timeout periods. . Create the ISO with this command: + ---- mkisofs -o file.iso -b isolinux.bin -c boot.cat -no-emul-boot #. -boot-load-size 4 -boot-info-table -R -J -v -T isolinux/ ---- + Note that [path]``isolinux/`` is the relative path to the directory containing the modified isolinux files copied from the distribution CD, while [path]``file.iso`` is the output ISO file, which is placed into the current directory. . Burn the ISO to CD-ROM and insert the disk. Alternatively prepare an USB key and insert it. . Boot the system and type [command]``ks`` at the prompt (if you left the label for the Kickstart boot as 'ks'). . Press kbd:[Enter] to start {kickstart}. type: Title =

Czech

Needs editing

Skip

	English	Czech	Actions
	In order to prepare an ISO image with {cobbler}, you need to prepare a distribution and a profile, similar to using network boot over PXE. For information about creating a distribution, see xref:client-configuration:autoinst-distributions.adoc[Autoinstallable Distributions]. For information about creating a profile, see xref:client-configuration:autoinst-profiles.adoc[Autoinstallation Profiles].
	The {cobbler} [command]``buildiso`` command takes parameters to define the name and output location of the boot ISO. Specifying the distribution with [option]``--distro`` is mandatory when running [command]``buildiso`` command.
	cobbler buildiso --iso=/path/to/boot.iso --distro=<your-distro-label>
	You must use distro and profile labels as listed by {cobbler}, and not simply as shown in the UI.
	To list the names of distributions and profiles stored by {cobbler}, run the commands:
	# cobbler distro list # cobbler profile list
	The boot ISO includes all profiles and systems by default. You can limit which profiles and systems are used with the [option]``--profiles`` and [option]``--systems`` options. For example:
	cobbler buildiso --systems="system1 system2 system3" \ --profiles="<your-profile1-label> <your-profile2-label> <your-profile3-label> --distro=<your-distro-label>
	If you cannot write an ISO image to a public [path]``tmp`` directory, check your systemd settings in [path]``/usr/lib/systemd/system/cobblerd.service``.
	Build a SUSE ISO Image With KIWI
	KIWI is an image creation system. You can use KIWI to create a bootable ISO image to be used by the target system for installation of a {suse} system. When the system is rebooted or switched on, it boots from the image, loads the {ay} configuration from your {productname}, and installs {sles} according to the {ay} profile.
	To use the ISO image, boot the system and type `autoyast` at the prompt (assuming you left the label for the {ay} boot as ``autoyast``). Press kbd:[Enter] to begin the {ay} installation.
	For more information about KIWI, see http://doc.opensuse.org/projects/kiwi/doc/.
	Build a Red Hat ISO Image With {cobbler}
	For more information, see xref:client-configuration:autoinst-cdrom.adoc#build-iso-with-cobbler[].	Další informace viz xref:client-configuration:registration-cli.adoc[].
	Autoinstallable Distributions	Uložte stisknutím tlačítka: [Create Autoinstallable Distribution] (Vytvořit automaticky instalovatelnou distribuci).
	The autoinstallation process relies on an several files to initiate the installation. These files include the Linux kernel, an initial RAM disk, and other files required to boot the operating system in installation mode.
	You can extract the needed files from a DVD image. For information, see xref:client-configuration:autoinst-distributions.adoc#based-on-iso-image[Distribution Based on an ISO Image].
	Alternatively, you can install the [package]``tftpboot-installation`` package. For information, see xref:client-configuration:autoinst-distributions.adoc#based-on-rpm-package[Distribution Based on a RPM Package].	Další informace o aktivačních klíčích viz xref:client-configuration:activation-keys.adoc[].
	You must also have a base channel synchronized on your {productname} Server for the same operating system version as those files.
	When you have the files ready, and the base channel synchronized, you need to declare the distribution. This operation associates the installation files to the base channel. The distribution can be referred to by one or more installation profiles. For information, see xref:client-configuration:autoinst-distributions.adoc#declare-distribution[Declare an Autoinstallable Distribution].
	Distribution Based on an ISO Image
	This method assumes you have installation media for the operating system you want to install on the clients. This is usually a DVD [path]``.iso`` image that contains the Linux kernel, an [path]``initrd`` file, and other files required to boot the operating system in installation mode.
	Procedure: Importing Files from Installation Media	Postup: Příprava instalačního média
	Copy the installation media to your {productname} Server. For {suse} operating systems, you can download installation media from https://www.suse.com/download/.
	Loop-mount the ISO image, and copy its contents somewhere:
	# mount -o loop,ro <image_name>.iso /mnt # mkdir -p /srv/www/distributions # cp -a /mnt /srv/www/distributions/<image_name> # umount /mnt
	Take a note of the file path. You will need it when you declare the distribution to {productname}.
	Distribution Based on a RPM Package
	This method works on {suse} systems. It is simpler than importing contents from an installation media, because it uses prepackaged files for your installation system.
	Procedure: Extracting Files from an Installation Package	Postup: Vytvoření profilu automatické instalace

Loading…

None

Source string changed

English 27 characters edited

3 years ago

Browse all string changes

Things to check

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	Czech
No related strings found in the glossary.

String information

Source string description

[[build-iso-with-mkisofs]] == Build a RedHat ISO Image With mkisofs You can use [command]``mkisofs`` to create a bootable ISO image to be used by the target system for installation of a {redhat} system. When the system is rebooted or switched on, it boots from the image, loads the {kickstart} configuration from your {productname}, and installs {rhel} according to the {kickstart} profile. .Procedure: Building a Bootable ISO With mkisofs . Copy the contents of [path]``/isolinux`` from the first CD-ROM of the target distribution. . Edit the [path]``isolinux.cfg`` file to default to 'ks'. Change the 'ks' section to read: + ---- label ks kernel vmlinuz append text ks=`url` initrd=initrd.img lang= devfs=nomount #. ramdisk_size=16438 `ksdevice` ---- + IP address-based {kickstart} URLs look like this: + ---- http://`my.manager.server`/kickstart/ks/mode/ip_range ---- + The {kickstart} distribution defined via the IP range should match the distribution from which you are building, to prevent errors occurring. . OPTIONAL: If you want to use the [replaceable]``ksdevice``, it looks like this: + ---- ksdevice=eth0 ---- + It is possible to change the distribution for a Kickstart profile within a family, such as {rhel} AS 4 to {rhel} ES 4, by specifying the new distribution label. Note that you cannot move between versions (4 to 5) or between updates (U1 to U2). . Customize [path]``isolinux.cfg`` further as required. For example, you can add multiple options, different boot messages, or shorter timeout periods. . Create the ISO with this command: + ---- mkisofs -o file.iso -b isolinux.bin -c boot.cat -no-emul-boot #. -boot-load-size 4 -boot-info-table -R -J -v -T isolinux/ ---- + Note that [path]``isolinux/`` is the relative path to the directory containing the modified isolinux files copied from the distribution CD, while [path]``file.iso`` is the output ISO file, which is placed into the current directory. . Burn the ISO to CD-ROM and insert the disk. Alternatively prepare an USB key and insert it. . Boot the system and type [command]``ks`` at the prompt (if you left the label for the Kickstart boot as 'ks'). . Press kbd:[Enter] to start {kickstart}. type: Title =

Flags

no-wrap

Source string location

modules/client-configuration/pages/autoinst-distributions.adoc:1

String age

3 years ago

Last updated

2 weeks ago

Source string age

3 years ago

Translation file

l10n-weblate/client-configuration/cs.po, string 207