第 12 章 Semi-automated installations: Making Kickstart files available to the RHEL installer
After your Kickstart file is ready, you can make it available for installation on the destination system.
12.1. Sharing the installation files on a local volume 复制链接链接已复制到粘贴板!
You can store Kickstart files on a local storage volume to enable automated installations without network dependencies. It is ideal for isolated environments or systems where network access is limited, providing a portable solution for unattended RHEL deployments.
Prerequisites
- You have a drive that can be moved to the machine to be installed, such as a USB stick.
-
The drive contains a partition that can be read by the installation program. The supported types are
ext2,ext3,ext4,xfs, andfat. - The drive is connected to the system and its volumes are mounted.
Procedure
List volume information and note the UUID of the volume to which you want to copy the Kickstart file.
# lsblk -l -p -o name,rm,ro,hotplug,size,type,mountpoint,uuid- Navigate to the file system on the volume.
- Copy the Kickstart file to this file system.
-
Make a note of the string to use later with the
inst.ks=option. This string is in the formhd:UUID=volume-UUID:path/to/kickstart-file.cfg. Note that the path is relative to the file system root, not to the/root of file system hierarchy. Replace volume-UUID with the UUID you noted earlier from the output oflsblk. Unmount all drive volumes:
# umount /dev/xyz ...(add all the volumes to the command, separated by spaces.)