Description of Problem: Trying to do an installation from bootable CD fails when the floppy containing the ks.cfg is write protected (CD uses a boot.img with modified syslinux.cfg). It seems that anaconda just mount()s, but stumbles over the "mounting read.only"-exit-code. Version-Release number of selected component (if applicable): anaconda-7.1-5 Did not have the time to check other releases... How Reproducible: Always. Steps to Reproduce: 1. Get an entry with "ks=hd:fd0/ks.cfg.xxx" into syslinux.cfg on the CD-bootimage 2. Boot, and select the entry Actual Results: Kickstart fails Expected Results: Kickstarts works ;-) Additional Information: Error disappeares when write protection is removed from the floppy. Took me some time and some walks. Luckily, the mistake happened before I gave that CD to the NT admins in the other locations... Guess anaconda should just mount RO, and the problem would disappear. Does it need write access?
No reason I can think of to not mount read-only by default
Note that you can also use ks=floppy which does do read-only mounts But, I've also modified things in CVS so hard drive mounts for kickstart files are read-only by default.
Yup, that's clear.... It's just, I've got about 20 different ks.cfg.<hostname> 's on that floppy, for a bunch of cluster servers to be (re-)installed in case of HW failure.