Here is another minor bug with system-config-kickstart:
During the opening of an existing kickstart configuration file, the application fails to read or load the bootloader configuration. If this isn't reconfigured within kickstart, saving the file will set the bootloader directive to:
bootloader --location=none --boot-drive=<disk device=>
During the opening of an existing kickstart configuration file, the application fails to read or load the bootloader configuration. If this isn't reconfigured within kickstart, saving the file will set the bootloader directive to:
bootloader --location=none --boot-drive=<disk device=>
The location option should have been populated with those from the original file when it was read.
Best thing to do is to double check all of the basic settings once the kickstart config file is created (and saved) and manually edit whatever needs to be adjusted.
No comments:
Post a Comment