Red Hat Bugzilla – Bug 862442
kickstart script files are lost after reboot
Last modified: 2013-01-09 22:36:32 EST
When kickstart scripts don't use --logfile, they get written to /tmp/ either outside the chroot or inside. When done outside the chroot they are lost upon reboot. When done inside the chroot they are written to /tmp/ which is tmpfs and thus lost on reboot.
They need to be written elsewhere, and copied to /var/log/anaconda/ on the installed system. However the facility to copy the logs is itself a kickstart script, chicken/egg.
We can always write out the log file to the out of chroot location of /tmp/ but we need a better solution for copying them in.
Maybe the ks script that copies the logs can use a --logfile option, and we'd just hardcode that to /mnt/sysimage/<somewhere>. That seems dangerous. Or we can just not worry about the log messages from this file?