(Originally reported by Hitachi tester)
Test with Wolverine.
Japanese kickstart installation,if set LANG=en_US in ks.cfg file,
system will be installed as English enviroment.
/etc/sysconfig/i18n is set to en_US.
Japanese is not enabled in ksconfig.
So is the problem with ksconfig, anaconda, or both?
Sorry to make you confused.Actually there are problems with both of them.
I will file another bug report pointing to ksconfig.
Actually there should be two options about language:
These two options have been available in anaconda.(CDROM install,NFS install...)
However in ks.cfg file only one language option is used,
another language option should be added for post-install enviroment.
Actually, kickstart was updated to support the environment language.
Unfortunately, however, the change was not documented. The correct tag in the
kickstart file should be:
langsupport en_US (or whatever language you want)
Tammy, can you make sure that this gets rolled into the kickstart documentation
in the future?
So yes, environment language support should be rolled into ksconfig too.
Changing component to Customization Guide.
It is too late to get this in the printed docs for this release, but I will add
it in CVS so that it is fixed for the next release and issue an errata once
everything is released.
Created attachment 15425 [details]
Update to support Japanese installer language and enviroment language
Thanks for that patch! I am reassigning to the ksconfig component.
Thanks, Bill. I have applied the patch and committed it to cvs. The fix should
appear in all post 1.2-1 builds of ksconfig.