From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0; T312461) Description of problem: When using HDD kickstart(ex. ks=hd:hda/ks.cfg), it fails sometimes. Because anaconda mounts HDD with read-write option. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.prepare kickstart file on floppy disk, in IDE-floopy drive etc. 2.turned on the protect notch(readonly). 3.kickstart install with ks=hd:hda/ks.cfg Actual Results: /tmp/ks.cfg can't be found. Installation is stopped Expected Results: /tmp/ks.cfg can be found, and installation is continued. Additional info: Almost this is not a problem, but especially for floppy device, it might be serious issue. Now we have many abnormal floopy device, IDE-floppy, USB-floppy etc. These are behaving /dev/hd[a-z] or /dev/sd[a-z], like a normal fixed disk. Anaconda can't treat them as a floopy, so we must specify it is fixed disk when kickstart installation. The mount option of anaconda for fixed disk doesn't have "-r", then mount command of bussy box brings mount error when the floopy disk can't be writen. Just add "-r" option into anaconda's "mount".
This is fixed in our current trees