Bug 103355

Summary: text option in ks.cfg is ignored
Product: Red Hat Enterprise Linux 2.1 Reporter: Pancrazio `ezio' de Mauro <pdemauro>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: low Docs Contact:
Priority: medium    
Version: 2.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-10-16 01:03:28 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:
Attachments:
Description Flags
Example ks.cfg none

Description Pancrazio `ezio' de Mauro 2003-08-29 08:58:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
For kickstart installations, the

        text

option in ks.cfg is ignored and the installation takes place in X

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. create a ks.cfg containing "text" in the first line and place it on the root
directory of a FAT floppy
2. boot off the RHEL AS 2.1 CD-ROM
3. choose 'linux ks=floppy' or 'linux ks=hd:fd0/ks.cfg'
    

Actual Results:  The installation takes place in X

Expected Results:  According to the documentation, the installation should
happen in text mode

Additional info:

As a workaround, it is possible to type 'text ks=hd:fd0/ks.cfg' at the boot
prompt and the installation takes place in text mode

Comment 1 Michael Fulbright 2003-09-02 21:55:38 UTC
We use this for testing routinely so its odd it didn't work for you. Please
attach the ks.cfg file you were using.

Comment 2 Pancrazio `ezio' de Mauro 2003-09-03 09:06:03 UTC
Created attachment 94164 [details]
Example ks.cfg

Comment 3 Jeremy Katz 2003-10-16 01:03:28 UTC
Closing due to inactivity.  Please reopen if you have any further information to
add to this bug report