Skip Navigation Links | |
Exit Print View | |
Transitioning From Oracle Solaris 10 to Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
1. Transitioning From Oracle Solaris 10 to an Oracle Solaris 11 Release (Overview)
2. Transitioning to an Oracle Solaris 11 Installation Method
6. Managing Software and Boot Environments
7. Managing Network Configuration
8. Managing System Configuration
Comparing Oracle Solaris 10 System Configuration to Oracle Solaris 11 System Configuration
System Configuration Changes and Migration of System Configuration to SMF
System Console, Terminal Services, and Power Management Changes
System Console and Terminal Services Changes
Power Management Configuration Changes
System Configuration Tools Changes
System Registration and System Support Changes
System Boot, Recovery, and Platform Changes
GRUB, Firmware, and Disk Labeling Changes
How to Boot From a Backup BE for Recovery Purposes
How to Boot the System For Recovery Purposes
Boot, Platform, and Hardware Changes
Printer Configuration and Management Changes
Removal of the LP Print Service
How to Set Up Your Printing Environment After Installing Oracle Solaris 11
10. Managing Oracle Solaris Releases in a Virtual Environment
Oracle Solaris 11 introduces the following internationalization and localization changes:
Language and locale support – Oracle Solaris 11 supports over 200 locales. By default, only a core set of locales is installed on the system. Core locales typically provide better support at the level of localized messages than locales that are available for additional installation. Specific Oracle Solaris components, such as the installers or Package Manager, are localized for core locales only. Note that localized messages for third-party software, for example GNOME and Firefox, include additional locales.
The core set of locales support the following languages:
Chinese – Simplified (zh_CN.UTF-8)
Chinese – Traditional (zh_TW.UTF-8)
English (en_US.UTF-8)
French (fr_FR.UTF-8)
German (de_DE.UTF-8)
Italian (it_IT.UTF-8)
Japanese (ja_JP.UTF-8)
Korean (ko_KR.UTF-8)
Portuguese – Brazilian (pt_BR.UTF-8)
Spanish (es_ES.UTF-8)
Notable core locale changes include the addition of the Portuguese – Brazilian locale and the removal of the Swedish locale.
Oracle Solaris 11.1 locale changes – The following locale changes are introduced in this release:
Japanese (ja_JP.UTF-8@cldr) locale – This locale is a new variant of the Japanese UTF-8 locale (ja_JP.UTF-8) that conforms to the Unicode Common Locale Data Repository (CLDR) for the Japanese locale. The locale is an optional component that is installable from the system/locale/extra package.
Local data for Simplified Chinese, Traditional Chinese, Korean, and Thai UTF-8 locales has been updated to support Unicode 6.0.
Language and locale packaging – The locale facet mechanism replaces the localeadm command in Oracle Solaris 11. In Oracle Solaris 10, optional package components, such as documentation, localization, or debug files are split into separate packages. In Oracle Solaris 11, IPS enables you to store these various package components in the same package by using special tags that are called facets. Facets simplify the packaging process, as well as minimize disk space usage. Locale facets are used to mark files or actions that are language or locale-specific.
Display the status of the facets on a system as follows:
$ pkg facet
The following example shows how to install the Danish locale and any available translations:
# pkg change-facet facet.locale.da=True # pkg change-facet facet.locale.da_DK=True
Note - Non-UTF-8 locales, such as da_DK.ISO8859-1 , are packaged separately. To enable these locales, install the system/locale/extra package.
Setting a system's default locale – In Oracle Solaris 10, the default system locale is configured in /etc/default/init. In Oracle Solaris 11, this file is obsoleted, and the configuration has moved to the corresponding properties of the svc:/system/environment:init SMF service. See Locale and Time Zone Configuration Changes.
Short form locales – Solaris 10 supports a number of short form locale names that do not follow the language_country.encoding[ @modifier] format, for example, ja,de, de_AT, and so on. These locales are not present in Oracle Solaris 11 in their original form, only as aliases to fully qualified locale names through the locale_alias mechanism. See locale_alias(5). In Oracle Solaris 11, it is recommended that the fully qualified locale names be used instead. Or, if possible, use UTF-8 locales. For more information, see the end-of-feature announcements at http://www.oracle.com/technetwork/systems/end-of-notices/eonsolaris11-392732.html.
Locale aliasing – Locale aliases are new in Oracle Solaris 11. Locale name aliases are accepted and mapped to the corresponding canonical locale names. For example, the de locale is mapped to the canonical locale de_DE.ISO8859-1. For all of the locale name mappings, see locale_alias(5).
Keyboard layout setting for the console – In Oracle Solaris 11, the keyboard layout setting for the console has migrated to SMF. To change the keyboard layout in the console, modify the keymap/layout property of the system/keymap:default SMF service. The following example shows how to set the UK-English layout for the console.
# svccfg -s keymap:default setprop keymap/layout = UK-English # svcadm refresh keymap # svcadm restart keymap
Note - The keyboard layout in the graphical interface is set separately.
Locale and time zone configuration is set in the /etc/default/init file in Oracle Solaris 10.
In Oracle Solaris 11, this configuration is managed through the following SMF service properties:
Locale: svc:/system/environment:init
Time zone: svc:/system/timezone:default
For example, to change the default system locale to fr_FR.UTF-8, you would configure the SMF service property as follows:
# svccfg -s svc:/system/environment:init \ setprop environment/LANG = astring: fr_FR.UTF-8 # svcadm refresh svc:/system/environment
The service must be refreshed for changes to take affect.
For the time zone setting, make sure the TZ in the /etc/default/init file is set to localtime.
grep TZ /etc/default/init TZ=localtime
Then, set the time zone SMF property to the required time zone.
# svccfg -s timezone:default setprop timezone/localtime= astring: US/Mountain # svcadm refresh timezone:default
For other date and time configuration changes in this release, see Configuring Date and Time Before and After an Installation.