Score:0

Kickstart %ksappend Filepath

ng flag

I'm trying to modularize my kickstart file; in particular, I'd like the %pre section to live in a separate file brought in using the %ksappend statement. However, this consistently fails with the installer saying '/run/install/ks.cfg is missing'; I'll note that my actual kickstart file is called ks_system.cfg, so I assume the ks.cfg being asked for is the one that results from initial parsing of the kickstart file. %ks_append is definitely the cause here; removing it gets rid of the error - but of course I don't have my pre-file included if I do that, and must include its contents directly in the master kickstart file.

I can't find any documentation on how to reference this file during the initial processing phase. The intent is to include it in the installation ISO file alongside the other kickstart files - the master ks_system.cfg, and other components that are successfully included using %include statements after pre-processing has finished.

I've tried as many variations of the file path I can think of but continue receiving this failure. How do I reference a file alongside the master ks_system.cfg kickstart file in the ISO with %ksappend?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.