Bug 60652

Summary:	Kickstart fails when floppy is write-protected
Product:	[Retired] Red Hat Linux	Reporter:	Nick (Gunnar) Bluth <bluth>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-04-01 23:07:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nick (Gunnar) Bluth 2002-03-04 08:51:23 UTC

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?

Comment 1 Jeremy Katz 2002-03-04 20:41:31 UTC

No reason I can think of to not mount read-only by default

Comment 2 Jeremy Katz 2002-03-05 21:50:39 UTC

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.

Comment 3 Nick (Gunnar) Bluth 2002-03-06 06:42:23 UTC

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.