##archives associated with it.

##The "no select" sw_source is a no-op source since it is "cmd"

##format, and does not have any scripts specified. Every sw_sel needs

##a sw_source.

########################################################################

sw_source "no select" { source_format = cmd

}

init sw_sel "English" {

description = "English Language Environment" sw_source = "no select"

sw_category = "Languages"

locale = { "SET_NULL_LOCALE:English", "C:English" } } = TRUE

If you wish to be able to select, for example, Japanese locales during installation, you would have to customize the configuration file to describe the locales available in the golden image. For example, you could replace the locale line above with the following configuration:

locale = { "ja_JP.SJIS:Japanese", "ja_JP.eucJP:Japanese",

"ja_JP.utf8:Japanese", "SET_NULL_LOCALE:English", "C:English" }

This would allow you to select any of the Japanese or English locales available on the system. Note that the "English" description can be misleading. The locale SET_NULL_LOCALE means the default system locale (POSIX/C) and C are explicitly the POSIX/C locale.

The locale line in the configuration file should not be wrapped; rather, it should be on one contiguous line. You should never add locales that do not exist in the golden image to the configuration.

The format of a entry in the locale list is:

"<locale>:<description>"

Where <locale> is the name of the locale shown in the output of the "locale -a"command on the system on which the golden image was created (for example ja_JP.SJIS). This is followed immediately by a colon and then by a description of the locale. The description cannot contain white space; if you need more than one word in the description, replace any white space by the underscore ("_") character. For example "ja_JP.SJIS:Japanese_SJIS" has the space between Japanese and SJIS replaced with an underscore. Remember that the locale list entry must be enclosed by double quotes, as seen above, when placed into a configuration file.

You should also be aware that even though a locale might not be listed, it only means that it cannot be selected via the Ignite-UX GUI. Any locale that was present when the golden image was created will still be available on any system installed using the golden image.

The next section defines default keyboards. You could add other keyboards depending on your environment or replace the defaults with those applicable to you.

########################################################################

##Keyboards

##Newer machines use USB as the keyboard interface. This example

##shows a way to handle both older (PS2) and newer (USB) keyboards.

##There are many other keyboard types available, see itemap(1m).

200