Description of problem:
unable to open anaconda generated anaconda-ks.cfg
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open attached file with system-config-kickstart-2.5.16-2
there seems to be two areas wich cause problem. they need to be taken care one
at a time. to see "--onboot no" problems comment out disk lines.
1. "--onboot no" in line 9
2. raid configuration.
Created attachment 113276 [details]
anaconda generated ks.cfg file.
The same explanation on bug 163162 applies here as well, but I'm not marking
this as a duplicate of that since they're on different RHEL versions. Adding to
There are several of these sorts of bugs in system-config-kickstart as shipped
in RHEL3, RHEL4, and their Fedora Core counterparts. The correct fix is
essentially a reimplementation of how kickstart files are handled which is a
very invasive change with lots of potential for creating more bugs. This work
has been done in the form of the pykickstart package for FC5. The next major
RHEL release will pick up these changes and take care of the problem.
This will be fixed in the next major release of RHEL.