Description of Problem:
A. mkkickstart fails to properly detect existing partitioning of disk
B. Even when proper partitioning info is manually added to ks.cfg file
and a kickstart install (linux ks=floppy) fails with error message:
Error opening: kicktart file /tmp/ks.cfg: no such file
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. build system manually with customized partitioning
2. run 'mkkickstart > /mnt/floppy/ks.cfg
a. open ks.cfg in editor (or use less) to verify
partioning info is incorrect
b. manually correct all partitioning info
3. boot new system off cdrom with 'linux ks=floppy'
4. watch it break
Total and complete failure to install OS on system
Er, a working system maybe?
You might want to check out Sun's JumpStart, it works.
Created attachment 34902 [details]
mkkickstart by default creates incorrect partitioning information. This is
what I ended up for partitioning info with before manually correcting it:
part swap --size 245
part /home --size 488
I don't understand why this is so broken, it should be trivial to figure
out what the exising partitioning scheme is. I've attached a simple perl
script you can use to figure this stuff out if you want it.
Created attachment 34941 [details]
perl script to write out ks.cfg partition info
Tested this same ks.cfg file on a new 7.2 install and it failed with
the same /tmp/ks.cfg: No such file or directory error as 7.1 does.
Thump, Thump, Thump. Hey, this thing working? Testing 1...2...3...
Anyone here? Anyone. Is thing on?
Bueller? Bueller? Bueller?
Hmmm, maybe there's a minimum incubation period of 2 weeks before bug fixes hatch?
Outstanding! So now I've even succeeded to prove that 7.2 has the same bug.
I used the anaconda-ks.cfg file created during 7.2 install, saved it to a
floppy, booted an identical system using the 7.2 install CD and specified
and I get an error stating:
Error opening: kickstart file /tmp/ks.cf: No such file ir directory
By the way, is anyone there even reading bug reports anymore? I have yet to
even get an acknowledgement that anyone is receiving these reports.
*** Bug 55043 has been marked as a duplicate of this bug. ***
*** Bug 55044 has been marked as a duplicate of this bug. ***
Did you rename anaconda-ks.cfg ks.cfg?
And, mkkickstart is gone now, replaced by anaconda-ks.cfg being generated.