{"results":[{"id":"anaconda-boot-parameter-framework","text":"Anaconda installation is controlled through a layered boot parameter framework: inst.ks= for Kickstart automation, inst.repo= for installation source selection (supporting HTTP/FTP/NFS/CDN), inst.stage2= for runtime image location, inst.graphical/text/cmdline for UI mode control, and inst.sshd for remote access during installation.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"anaconda-ks-cfg-saved-after-install","text":"After every interactive RHEL installation, a reference Kickstart file is saved at `/root/anaconda-ks.cfg`.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"inst-graphical-is-default-mode","text":"`inst.graphical` is the default Anaconda installation mode; `inst.text` forces text mode, `inst.cmdline` forces non-interactive mode (requires Kickstart).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"inst-ks-boot-option","text":"The `inst.ks=` boot option specifies the Kickstart file location for automated RHEL installations (e.g., `inst.ks=http://server/path/ks.cfg`).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"inst-ksstrict-turns-warnings-to-errors","text":"The `inst.ksstrict` boot option turns deprecated Kickstart command warnings into errors.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"inst-sshd-enables-ssh-during-install","text":"`inst.sshd` enables SSH access during installation; on IBM Z it is auto-started by default; root has no password unless set via `sshpw` Kickstart command.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-anaconda-ks-cfg-auto-created","text":"`/root/anaconda-ks.cfg` is automatically created after every interactive RHEL installation and can be reused as a Kickstart file","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-anaconda-ks-cfg-location","text":"After every interactive RHEL installation, a Kickstart file is automatically saved at `/root/anaconda-ks.cfg` and can be reused for future installations.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-automated-deployment-pipeline","text":"Kickstart provides a complete automated deployment pipeline: inst.ks= boot parameter, multiple installation sources (media/CDN/network), syntax validation via ksvalidator, fully unattended operation, and auto-generated template from prior installs.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-cmdline-halts-on-interaction","text":"`cmdline` mode halts the installation if any user interaction is required — all options must be pre-configured in the Kickstart file.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-default-completion-halt","text":"The default Kickstart completion method is `halt` (equivalent to `shutdown -H`) if no completion command is specified.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-eula-agreed-required-unattended","text":"`eula --agreed` is required in Kickstart for unattended installations to skip the EULA acceptance prompt.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-harddrive-supported-filesystems","text":"The `harddrive` Kickstart command supports `ext2`, `ext3`, `ext4`, `vfat`, and `xfs` filesystems for the installation source partition.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-inst-ks-boot-parameter","text":"The `inst.ks=` boot parameter specifies a Kickstart file location, supporting HTTP, HTTPS, FTP, NFS, hard drive, and CDROM sources.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-install-command-removed-rhel9","text":"The `install` Kickstart command has been removed in RHEL 9; installation source commands (`cdrom`, `url`, `nfs`, etc.) are used directly.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-installation-sources","text":"Kickstart installations can pull content from local media (DVD/USB), ISO images, Red Hat CDN, or network servers (HTTP, FTP, NFS).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-logging-tcp-only-port-514","text":"Kickstart `logging` command for remote syslog uses TCP only, with default port 514.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-rhsm-direct-cdn-registration","text":"The `rhsm` Kickstart command allows registering and installing directly from the Red Hat CDN without needing `%post` scripts.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-sources-local-cdn-network","text":"Kickstart supports installation sources: local media, ISO, Red Hat CDN, and network servers (HTTP/HTTPS/FTP/NFS)","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-unattended-install","text":"Kickstart enables fully unattended RHEL installation when all required parameters are provided in the Kickstart file.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null}],"count":36,"limit":20,"offset":0}