Bug 51892 - language screen still displayed on kickstart install
language screen still displayed on kickstart install
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Brent Fox
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-08-16 12:11 EDT by Michael E Brown
Modified: 2007-04-18 12:35 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-16 14:59:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Kickstart file (5.56 KB, text/plain)
2001-08-16 12:13 EDT, Michael E Brown
no flags Details

  None (edit)
Description Michael E Brown 2001-08-16 12:11:51 EDT
Description of Problem:
The kickstart language screen is still displayed, even though the 
kickstart file contains the directive: 
	lang en_US

How Reproducible:
Floppy-based kickstart install

Actual Results:
Anaconda asks the user for the language specification.

Expected Results:
Anaconda should not display any questions for the user
Comment 1 Michael E Brown 2001-08-16 12:13:37 EDT
Created attachment 28134 [details]
Kickstart file
Comment 2 Glen Foster 2001-08-16 14:59:34 EDT
This defect is considered SHOULD-FIX for Fairfax.
Comment 3 Brent Fox 2001-08-16 15:26:37 EDT
You need a line in your kickstart file for language support.  Here's a snippet
from the new Kickstart documentation:

langsupport -- Sets the language(s) to install on the system. The same language
codes used with lang can be used with langsupport.

    --default [1]

        Sets the default language to use for any language-specific aspect of the
installed system.

    An example to install English and French and use English as the default

languagesupport --default en_US fr_FR

So, add a line like:
languagesupport --default en_US

and then the kickstart should proceed without questioning you.

Note You need to log in before you can comment on or make changes to this bug.