Desktop Features

e.
rom
ns f
ce on
Li si
o is
t t rm
ec e
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
Changes in Other Solaris™ 10

st d
OS Desktop Features
sy or
WZI-SS-3603
ro e
ic at
M lic
Student Guide
n p
Su t du
no
o
D
Sun Microsystems, Inc.

UBRM05-104
500 Eldorado Blvd.
Broomfield, CO 80021
U.S.A.
Sun Proprietary: Internal Use Only Revision A
aadd
D
o
no
October 15, 2004 4:08 pm
Su t du
n p
M lic
ic at
ro e
sy or
st d
em ist
s, rib
In ut
c. e w
U
se ith
Su ou
bj t p
ec e
t t rm
o is
Li si
ce on
ns f
e. rom
Copyright 2004 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.
This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and
decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of
Sun and its licensors, if any.
Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.
e. rom
Sun, Sun Microsystems, the Sun logo,Sun Blade, Sun Fire, Sun Ray, Solaris, Netra, OpenBoot, Java, Javadoc, and Java Card are trademarks
or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and
ns f
other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
ce on
UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.
Li si
Federal Acquisitions: Commercial Software – Government Users Subject to Standard License Terms and Conditions
o is
t t rm
Export Laws. Products, Services, and technical data delivered by Sun may be subject to U.S. export controls or the trade laws of other
countries. You will comply with all such laws and obtain all licenses to export, re-export, or import as may be required after delivery to
You. You will not export or re-export to entities on the most current U.S. export exclusions lists or to any country subject to U.S. embargo
ec e
or terrorist controls as specified in the U.S. export laws. You will not use or provide Products, Services, or technical data for nuclear, missile,
bj t p
or chemical biological weaponry end uses.
Su ou
DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND
WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
se ith
OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE
LEGALLY INVALID.
c. e w
THIS MANUAL IS DESIGNED TO SUPPORT AN INSTRUCTOR-LED TRAINING (ILT) COURSE AND IS INTENDED TO BE
USED FOR REFERENCE PURPOSES IN CONJUNCTION WITH THE ILT COURSE. THE MANUAL IS NOT A STANDALONE
TRAINING TOOL. USE OF THE MANUAL FOR SELF-STUDY WITHOUT CLASS ATTENDANCE IS NOT RECOMMENDED.
In ut
U
Export Commodity Classification Number (ECCN) assigned: 2 July 2004

s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D
Sun Proprietary: Internal Use Only

Please
Recycle
Copyright 2004 Sun Microsystems Inc. 4150 Network Circle, Santa Clara, California 95054, Etats-Unis. Tous droits réservés.
Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution,
et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit,
sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a.
Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié
par des fournisseurs de Sun.
e. rom
Sun, Sun Microsystems, le logo Sun, Sun Blade, Sun Fire, Sun Ray, Solaris, Netra, OpenBoot, Java, Javadoc, et Java Card sont des marques
de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.
ns f
Toutes les marques SPARC sont utilisées sous licence sont des marques de fabrique ou des marques déposées de SPARC International, Inc.
ce on
aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun
Microsystems, Inc.
Li si
UNIX est une marques déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.
o is
t t rm
Législation en matière dexportations. Les Produits, Services et données techniques livrés par Sun peuvent être soumis aux contrôles
américains sur les exportations, ou à la législation commerciale dautres pays. Nous nous conformerons à lensemble de ces textes et nous
obtiendrons toutes licences dexportation, de ré-exportation ou dimportation susceptibles dêtre requises après livraison à Vous. Vous
ec e
nexporterez, ni ne ré-exporterez en aucun cas à des entités figurant sur les listes américaines dinterdiction dexportation les plus courantes,
bj t p
ni vers un quelconque pays soumis à embargo par les Etats-Unis, ou à des contrôles anti-terroristes, comme prévu par la législation
américaine en matière dexportations. Vous nutiliserez, ni ne fournirez les Produits, Services ou données techniques pour aucune utilisation
Su ou
finale liée aux armes nucléaires, chimiques ou biologiques ou aux missiles.
se ith
LA DOCUMENTATION EST FOURNIE “EN L’ETAT” ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES
EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y
COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE
c. e w
UTILISATION PARTICULIERE OU A L’ABSENCE DE CONTREFAÇON.
CE MANUEL DE RÉFÉRENCE DOIT ÊTRE UTILISÉ DANS LE CADRE D’UN COURS DE FORMATION DIRIGÉ PAR UN
In ut
INSTRUCTEUR (ILT). IL NE S’AGIT PAS D’UN OUTIL DE FORMATION INDÉPENDANT. NOUS VOUS DÉCONSEILLONS DE
U
L’UTILISER DANS LE CADRE D’UNE AUTO-FORMATION.

s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

Please
Recycle
e. rom
ns f
ce on
Table of Contents
Li si
o is
t t rm
About This Course ..............................................................Preface-vii
Course Goals......................................................................... Preface-vii
ec e
How Prepared Are You?....................................................... Preface-ix
bj t p
Introductions ........................................................................... Preface-x
Su ou
How to Use Course Materials .............................................. Preface-xi
Conventions ...........................................................................Preface-xii
se ith
Typographical Conventions ......................................Preface-xiii
c. e w
Changes in Other Solaris™ 10 OS Desktop Features...................1-1
Objectives ........................................................................................... 1-1
In ut
Locale Data Editor Utility ................................................................. 1-2

U
What Is It? .................................................................................. 1-2

s, rib
How to Use the localeadm Command ................................. 1-3

Command Options ................................................................... 1-4
em ist
Changed Packages and Files ................................................. 1-15

st d
Requirements, Dependencies, and Limitations.................. 1-16

sy or
FAQs ......................................................................................... 1-17

Bugs and Common User Errors ............................................ 1-17
ro e
For More Information............................................................ 1-18

ic at
Changes to the Solaris Smartcard Feature.................................... 1-19

M lic
What Is It? ................................................................................ 1-19

n p
Configuring the T=1 Smart Card .......................................... 1-21

Su t du
Changed Packages and Files ................................................. 1-28

Requirements, Dependencies, and Limitations.................. 1-29
FAQ ........................................................................................... 1-30
no
Bugs and Common User Errors ........................................... 1-31

For More Information............................................................ 1-32
o
D

v
Copyright 2004 Sun Microsystems, Inc. All Rights Reserved. SunU, Revision A
Preface
e. rom
About This Course
ns f
ce on
Li si
Course Goals
o is
t t rm
Upon completion of this course, you should be able to identify changes to
ec e
other desktop features for the Solaris 10 OS.
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

Preface-vii
Course Goals
Course Map
The following course map enables you to see what you have
accomplished and where you are going in reference to the course goals.
e. rom
Changes in Other
ns f
Solaris™ 10 OS
ce on
Desktop Features
Li si
o is
t t rm
ec e
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

Preface-viii Changes in Other Solaris™ 10 OS Desktop Features
How Prepared Are You?
How Prepared Are You?

To be sure you are prepared to take this course, can you answer yes to the
following questions?
● Can you support the Solaris 9 Operating System?
e. rom
● Can you create and edit text files using a text editor?
ns f
● Can you use a World Wide Web (WWW) browser?
ce on
Li si
o is
t t rm
ec e
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

About This Course Preface-ix
Introductions
Introductions
Now that you have been introduced to the course, introduce yourself to
the other students and the instructor, addressing the following items:
● Name
e. rom
● Company affiliation
ns f
● Title, function, and job responsibility
ce on
● Experience related to topics presented in this course
Li si
● Reasons for enrolling in this course
o is
Expectations for this course.
t t rm
●
ec e
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

Preface-x Changes in Other Solaris™ 10 OS Desktop Features
How to Use Course Materials
How to Use Course Materials

To enable you to succeed in this course, these course materials contain a
learning module that is composed of the following components:
● Goals – You should be able to accomplish the goals after finishing
e. rom
this course and meeting all of its objectives.
● Objectives – You should be able to accomplish the objectives after
ns f
completing a portion of instructional content. Objectives support
ce on
goals and can support other higher-level objectives.
Li si
● Lecture – The instructor presents information specific to the objective
o is
of the module. This information helps you learn the knowledge and
t t rm
skills necessary to succeed with the activities.
ec e
● Activities – The activities take various forms, such as review
bj t p
questions, exercises, self-checks, discussion, and demonstrations.
Su ou
Activities help you facilitate the mastery of an objective.
Visual aids – The instructor might use several visual aids to convey a
se ith
●
concept, such as a process, in a visual form. Visual aids commonly
c. e w
contain graphics, animation, and video.
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

About This Course Preface-xi
Conventions
Conventions
The following conventions are used in this course to represent various
training elements and alternative learning resources.
e. rom
Icons
ns f
ce on
Note – Indicates additional information that can help students but is not
Li si
crucial to their understanding of the concept being described. Students
o is
should be able to understand the concept or complete the task without
t t rm
this information. Examples of notational information include keyword
shortcuts and minor system adjustments.
ec e
bj t p
Caution – Indicates that there is a risk of personal injury from a
Su ou
nonelectrical hazard, or risk of irreversible damage to data, software, or
se ith
the operating system. A caution indicates that the possibility of a hazard
(as opposed to certainty) might happen, depending on the action of the
c. e w
user.
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

Preface-xii Changes in Other Solaris™ 10 OS Desktop Features
Conventions
Typographical Conventions
Courier is used for the names of commands, files, directories,
programming code, and on-screen computer output; for example:
Use ls -al to list all files.
e. rom
system% You have mail.
ns f
Courier is also used to indicate programming constructs, such as class
ce on
names, methods, and keywords; for example:
Li si
The getServletInfo method is used to get author information.
o is
The java.awt.Dialog class contains Dialog constructor.
t t rm
Courier bold is used for characters and numbers that you type; for
ec e
bj t p
example:
To list the files in this directory, type:
Su ou
# ls
se ith
Courier bold is also used for each line of programming code that is
c. e w
referenced in a textual description; for example:
In ut
1 import java.io.*;
U
2 import javax.servlet.*;
s, rib
3 import javax.servlet.http.*;
em ist
Notice the javax.servlet interface is imported to allow access to its

st d
life cycle methods (Line 2).

sy or
Courier italics is used for variables and command-line placeholders

ro e
that are replaced with a real name or value; for example:

ic at
M lic
To delete a file, use the rm filename command.

n p
Courier italic bold is used to represent variables whose values are to

Su t du
be entered by the student as part of an activity; for example:

Type chmod a+rwx filename to grant read, write, and execute
no
rights for filename to world, group, and users.

o
D
Palatino italics is used for book titles, new words or terms, or words that
you want to emphasize; for example:
Read Chapter 6 in the User’s Guide.
These are called class options.

About This Course Preface-xiii
Module 1
e. rom
Changes in Other Solaris™ 10 OS Desktop
Features
ns f
ce on
Li si
o is
t t rm
Objectives
ec e
bj t p
This module provides an overview of the new desktop features included
in the Solaris 10 OS.
Su ou
se ith
Upon completion of this module, you should be able to:
c. e w
● Identify features of the locale data editor utility
● Identify changes to the Solaris 10 OS Smartcard feature
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

1-1
Locale Data Editor Utility

This section describes the new locale data editor feature in the Solaris
10 OS.
e. rom
What Is It?
ns f
ce on
The locale data editor is a utility that allows you to query and configure
the locales for a Solaris OS through a command-line interface. Using the
Li si
localeadm tool, you can display information about locale packages that
o is
are installed on the system or that reside on a particular device or
t t rm
directory. The super-user can also add and remove locales on the current
system on a per-region basis.
ec e
bj t p
Brief Description
Su ou
se ith
Previously in Solaris there was no easy way to change locales on a
machine after installation. The only option available for choosing locales
c. e w
was provided during the Solaris install process. After this, you had to add
and remove individual packages to change the locales on the machine.
In ut
This was cumbersome and prone to error because there was no definitive
U
s, rib
list of the packages needed for each locale, and it was easy to overlook
a package.
em ist
st d
Features
sy or
The locale data editor provides the new localeadm command, an

ro e
application for adding and removing locales on a running machine on a

ic at
per-region basis (for example, Western European locales) based on the

M lic
structure of Solaris packages. The application reads the list of locales that
n p
are currently on the system, and, optionally, reads the list of packages
Su t du
available for install on specified media (for example, a Solaris CD or

network drive). It then offers the choice to add or remove locale regions
based on these lists. You also have the option to add support for a locale
no
and to exclude any translated-message support packages that would

normally be included for that locale. If you choose to exclude the optional
o
D
message support packages, you can to use the tool to add them at a
later time.
This tool is a supplement to the locale selection logic in the Solaris

installer. The installer is still the primary application for the correct
installation of Solaris locales.

1-2 Changes in Other Solaris™ 10 OS Desktop Features
Configuration Procedure
This feature does not require any configuration procedure. Two

configuration files do exist:
● /usr/sadm/lib/localeadm/Locale_config_S10.txt
e. rom
● /usr/sadm/lib/localeadm/admin
ns f
The utility creates log files of the following form:
ce on
● /var/sadm/install/logs/localeadmin_install.date
Li si
● /var/sadm/install/logs/localeadmin_uninstall.date
o is
t t rm
The date field has this format: YYYY_MM_DD. If multiple installs are done
ec e
in one day, the date has a number appended to it; for example,
bj t p
2004_10_20.1, 2004_10_20.2.
Su ou
How to Use the localeadm Command
se ith
c. e w
You can use the localeadm command in query or list modes, or to add
and remove locales on a Solaris system.
In ut
U
s, rib
In the query or list modes, the localeadm command displays information

about locale packages that are installed on the system or that reside on a
em ist
specified device or directory. The output is given as a list of country or

st d
region names rather than a list of packages, to make it easier to pick the
locales to change. You can then use this output to determine which locales
sy or
or regions you want to add or remove.

ro e
ic at
When you specify a locale or region to add or remove using the name
M lic
given by the output of the list mode, the localeadm command calculates
n p
what locale packages need to be changed and adds or removes them

Su t du
using the pkgadd or pkgrm commands as appropriate.
If the locales changed are Asian locales, then extra processes—such as

no
input method server daemons—might need to be started before the new

locale(s) work properly. When the locales are installed, you are prompted
o
D
to do this by either rebooting the machine or manually starting

the daemons.
The localeadm command should be run with root or super-user

privileges to add or remove locales or regions.

Changes in Other Solaris™ 10 OS Desktop Features 1-3
Command Options
Some of the localeadm command options are as follows:
● -l [-d device [,device2 ...]]
Lists all the locales that are installed on the system or available on an
e. rom
install media, sorted by geographic region. If used with the -d
option, the localeadm command lists all locales and regions
ns f
available on the device pointed to by the option argument(s) of the
ce on
-d option. If used without the -d option, it lists all locales/regions
Li si
installed on the current system.
o is
● -q locale | region
t t rm
Queries the system to see if locale locale or geographic region
ec e
region is already installed. The expected input for a locale or region
bj t p
name is the name displayed by the -l option.
Su ou
● -a locale | region
se ith
Adds the packages for a locale locale or geographic region region
to the system. The expected input for a locale or region name is the
c. e w
short name displayed by the -l option. For example, for the listing
output "Australasia (aua)" from the -l option, the argument for
In ut
-a would be aua. This option requires the -d option, with arguments

U
s, rib
to specify the device where the installation media is located. If

necessary packages are already installed, the localeadm command
em ist
does not overwrite them but simply skips them.

st d
● -d device [, device2, ...]

sy or
Installs or lists locales from packages located in device. The device

ro e
variable can be a full path name to a directory containing Solaris

ic at
packages or the path to the top directory of a complete Solaris image.

M lic
It can also be a device alias such as /cdrom/cdrom0, a device

nickname as defined by the eject command, or an alternative
n p
device nickname such as cdrom, dvd, or dvdrom.

Su t du
● -r locale | region
no
Removes the packages for a locale locale or geographic region

region from the system. The expected input for a locale or region
o
name is the name displayed by the -l option.

D
● -R root_path
Defines the full path name of a directory to use as the root path. All
files, including package system information files, are relocated to a
directory tree starting in the specified root_path. You can specify
the root_path when installing to a client from a server.

Additional command options are described in the localeadm command

man page.
The locale and region Option Arguments
The following is a more detailed explanation of the locale and region
e. rom
option arguments:
The locale argument – The name of a locale to be added to or
ns f
●
ce on
removed from the system. The expected input for a locale name is
the name displayed by the -l option in list mode with the -c flag
Li si
(-lc). For example, to install Spanish, use es_ES.ISO8859-1 or just
o is
es_ES.
t t rm
ec e
bj t p
Note – To allow differentiation between full and partial locales, es is not a
valid locale choice.
Su ou
If a locale name is given for the option, you receive a warning that all
se ith
locales for the region of which the locale is a member will be
c. e w
added/removed. For example, if you choose to install Swedish, then
all of the locales for the Northern Europe region (of which Sweden is
In ut
a member) will be installed. The locale option is only given for

U
backward compatibility.
s, rib
● The region argument – The name of a geographic region to be

em ist
added to or removed from the system. The expected input format of

st d
a region name is the name displayed by the -l option with the -s

flag (-ls). For example, to install the South American locales, use
sy or
localeadm -a sam. All of the locales listed for a given geographic

ro e
region will be installed with the region. Region is the preferred form
ic at
of reference.
M lic
n p
Command Examples
Su t du
The following examples show commands used to:

no
● List locales available on installation media

o
● Add a locale
D
● Use the query option

● Display the install log file

Listing locales available on the /export/install directory:

# localeadm -l -d /export/install
Devices are /export/install

Checking for installed packages. This could take a while.
e. rom
Checking for Australasia region (aua)
(of2c packages)
ns f
|...|
ce on
All packages found.
Li si
o is
(1of2 packages)
t t rm
|.....|
ec e
All packages found.
bj t p
Su ou
(2of2 packages)
se ith
|..|
All packages found.
c. e w
In ut
(langcd1 packages)
U
||
s, rib
All packages found.

em ist
Checking for Central America region (cam)

st d
(of2c packages)
sy or
|.........|
All packages found.
ro e
ic at

M lic
(1of2 packages)
n p
|..................|
Su t du
All packages found.

no

(2of2 packages)
o
|.......|
D
All packages found.

(langcd1 packages)
|........................................|
All packages found.

Checking for Central Europe region (ceu)

(of2c packages)
|.......|
All packages found.
e. rom
[many lines deleted for brevity]
ns f
Checking for Hindi region (hi_in)
ce on
(langcd1 packages)
Li si
||
o is
All packages found.
t t rm
-----------------
ec e
The following regions are installed on proto144 on Sat Jul 24 18:29:28
bj t p
MDT 2004
Su ou
POSIX (C)
Australasia (aua)
se ith
c. e w
[ Australia, New Zealand ]
In ut
Central America (cam)

U
s, rib
[ Costa Rica, Guatemala, Nicaragua, Panama, El Salvador ]

em ist
Central Europe (ceu)

[ Austria, Czech Republic, Germany, Hungary, Poland, Slovakia,
st d
Switzerland (Germ
sy or
an), Switzerland (French) ]

ro e
ic at
Eastern Europe (eeu)

M lic
[ Albania, Bosnia, Bulgaria, Estonia, Croatia, Lithuania, Latvia,

Macedonia, Rom
n p
ania, Russia, Serbia, Slovenia, Turkey ]

Su t du
Middle East (mea)

no
[ Israel ]
o
Northern Africa (naf)

D
[ Egypt ]
North America (nam)

[ Canada (English), Canada (French), United States, Mexico ]
Northern Europe (neu)

[ Denmark, Finland, Iceland, Norway (Bokmal), Norway (Nyorsk), Sweden ]
South America (sam)

[ Argentina, Bolivia, Brazil, Chile, Columbia, Ecuador, Paraguay, Peru,
Uraguay,
Venezuela ]
e. rom
Southern Europe (seu)
[ Italy, Greece, Portugal, Spain (Catalan), Spain (Spanish) ]
ns f
ce on
Western Europe (weu)
Li si
[France, Holland, Belgium (French), Belgium (Flemish), Ireland, England ]
o is
t t rm
Japanese (ja)
ec e
Korean (ko)
bj t p
Su ou
Simplified Chinese (zh_cn)
se ith
Traditional Chinese (Hong Kong) (zh_hk)
c. e w
Traditional Chinese (zh_tw)
In ut
Thai (th_th)
U
s, rib
Hindi (hi_in)
em ist
st d
Done.
A copy of this report can be found in
sy or
/usr/sadm/lib/localeadm/locales.list
ro e
#
ic at
M lic
Adding a locale:
n p
# localeadm -a aua -d /export/install

Su t du
Log file is /var/sadm/install/logs/localeadmin_install.2004-07-24

no
locale/region name is aua

Adding packages for Australasia (aua)
o
Region aua will be installed.

D
installing 1of2
Operating System is Solaris 10
Checking for a valid disk image:
Checking for a 1of2 image
|.....|

We have a 1of2:
/export/install/Solaris_10/Product
Checking package SUNWauadt......
Adding package SUNWauadt
Processing package instance <SUNWauadt> from
</export/install/Solaris_10/Product>
e. rom
Australasia CDE Support
(sparc) 1.0,REV=2001.03.06.18.03
Using </usr> as the package base directory.
ns f
ce on
## Processing package information.
## Processing system information.
Li si
2 package pathnames are already properly installed.
o is
## Verifying disk space requirements.
t t rm
Installing Australasia CDE Support as <SUNWauadt>
## Installing part 1 of 1.
ec e
/usr/dt/config/en_AU <symbolic link>
bj t p
[ verifying class <none> ]
Su ou
Installation of <SUNWauadt> was successful.
Checking package SUNWauaow......
se ith
Adding package SUNWauaow
Processing package instance <SUNWauaow> from
c. e w
Australasia OW Support
In ut
(sparc) 1.0,REV=2004.03.03.14.07
U
s, rib

em ist

st d

sy or
Installing Australasia OW Support as <SUNWauaow>

ro e
## Executing preinstall script.

ic at
M lic
/usr/openwin/lib/locale/en_AU <symbolic link>

/usr/openwin/lib/locale/en_AU.ISO8859-1/libs <symbolic link>
n p
Su t du
/usr/openwin/lib/locale/en_AU.ISO8859-1/xview/.text_extras_menu <symbolic
link>
/usr/openwin/lib/locale/en_NZ <symbolic link>
no
/usr/openwin/lib/locale/en_NZ.ISO8859-1/libs <symbolic link>

/usr/openwin/lib/locale/en_NZ.ISO8859-1/xview/.text_extras_menu <symbolic
o
link>
D

Installation of <SUNWauaow> was successful.
Checking package SUNWi1cs......
Adding package SUNWi1cs
Processing package instance <SUNWi1cs> from

X11 ISO8859-1 Codeset Support

(sparc) 2.0,REV=2002.07.15.14.45
Using </> as the package base directory.
e. rom
Installing X11 ISO8859-1 Codeset Support as <SUNWi1cs>
ns f
ce on
Installation of <SUNWi1cs> was successful.
Checking package SUNWplow......
Li si
Adding package SUNWplow
o is
Processing package instance <SUNWplow> from
t t rm
OpenWindows enabling for Partial Locales
ec e
(sparc) 1.0,REV=2004.03.31.10.36
bj t p
Su ou
se ith
c. e w
Installing OpenWindows enabling for Partial Locales as <SUNWplow>
## Executing preinstall script.
In ut
U
s, rib

[ verifying class <Xupdate> ]
em ist
Installation of <SUNWplow> was successful.

st d
Checking package SUNWplow1......

Adding package SUNWplow1
sy or
Processing package instance <SUNWplow1> from

ro e
ic at
OpenWindows enabling for Supplementary Partial Locales

M lic
(sparc) 1.0,REV=2004.03.01.09.49
n p
Su t du

no

Installing OpenWindows enabling for Supplementary Partial Locales as
o
<SUNWplow1>
D
Installation of <SUNWplow1> was successful.
installing 2of2


|..|
We have a 2of2:
Checking package SUNWauaos......
e. rom
Adding package SUNWauaos
Processing package instance <SUNWauaos> from
ns f
ce on
Australasia OS Support
(sparc) 11.10.0,REV=2003.12.08.12.05
Li si
o is
t t rm
ec e
bj t p
Installing Australasia OS Support as <SUNWauaos>
Su ou
Installation of <SUNWauaos> was successful.
se ith
Checking package SUNWlocaledefsrc......
Adding package SUNWlocaledefsrc
c. e w
Processing package instance <SUNWlocaledefsrc> from
In ut
EMEA localedef source files

U
s, rib
(sparc) 11.10.0,REV=2002.10.09.11.28
em ist

st d

sy or

ro e
Installing EMEA localedef source files as <SUNWlocaledefsrc>

ic at
M lic
Installation of <SUNWlocaledefsrc> was successful.

installing langcd1
n p
Su t du

no
Checking for a langcd image

We don't need a langcd
o
region name is Ausi

D
GEOS=Ausi,
LOCALES=en_NZ,en_AU,
(of2c packages)
|...|
All packages found.


(of2c packages)
|.........|
Not all packages found (1 out of 9).
e. rom
(of2c packages)
|.......|
ns f
ce on
Not all packages found (1 out of 7).
Li si
[truncated output]
o is
t t rm
Note – Note that the command apparently checks for installed regions
ec e
even if only an add operation was requested.
bj t p
Su ou
-----------------
se ith
c. e w
The following regions are installed on proto144 on Sat Jul 24 18:34:12
MDT 2004
In ut
U
POSIX (C)
s, rib
Australasia (aua)
em ist
st d
One or more locales have been added. To update the list of locales
sy or
available at the login screen's "Options->Language" menu, please restart

the dtlogin daemon (WARNING: this will terminate any active dtlogin
ro e
sessions)
ic at
M lic
Please log out and login again to use the new locale(s) at your desktop.
n p
If you are not intending to use the new locale(s) with the GUI desktop,
Su t du
you can start using the new locale(s) immediately by setting the LC_*
environment variables.
no
#
o
D
Using the query option:

# localeadm -q aua

(of2c packages)

|...|
All packages found.

(1of2 packages)
|.....|
e. rom
All packages found.
ns f
ce on
(2of2 packages)
|..|
Li si
All packages found.
o is
t t rm
(langcd1 packages)
ec e
||
bj t p
All packages found.
Su ou
The Australasia region (aua) is installed on this system
se ith
# cat /var/sadm/install/logs/localeadmin_install.2004-07-24
c. e w
Sat Jul 24 18:33:33 MDT 2004
Operation=install
In ut

U
s, rib
Adding packages for Australasia (aua)

Region aua will be installed.
em ist
Install_Dir=
st d
Region=aua
sy or

ro e

ic at
We have a 1of2:
M lic
Adding package SUNWauadt
n p
Su t du
Adding package SUNWauaow

Adding package SUNWi1cs
Adding package SUNWplow
no
Adding package SUNWplow1

o

D
We have a 2of2:
Adding package SUNWauaos
Adding package SUNWlocaledefsrc
Checking for a langcd image

We don't need a langcd

(of2c packages)
(1of2 packages)
e. rom
(2of2 packages)
(langcd1 packages)
ns f
ce on
(of2c packages)
Li si
o is
(of2c packages)
t t rm
Checking for Eastern Europe region (eeu)
(of2c packages)
ec e
Checking for Middle East region (mea)
bj t p
(of2c packages)
Su ou
Checking for Northern Africa region (naf)
(of2c packages)
se ith
Checking for North America region (nam)
(of2c packages)
c. e w
Checking for Northern Europe region (neu)
(of2c packages)
In ut
Checking for South America region (sam)

U
s, rib
(of2c packages)
Checking for Southern Europe region (seu)
em ist
(of2c packages)
st d
Checking for Western Europe region (weu)

(of2c packages)
sy or
Checking for Japanese region (ja)

ro e
(of2c packages)
ic at
Checking for Korean region (ko)

M lic
(of2c packages)
Checking for Simplified Chinese region (zh_cn)
n p
Su t du
(of2c packages)
Checking for Traditional Chinese (Hong Kong) region (zh_hk)
(of2c packages)
no
Checking for Traditional Chinese region (zh_tw)

(of2c packages)
o
Checking for Thai region (th_th)

D
(of2c packages)
Checking for Hindi region (hi_in)
(of2c packages)
#

Changed Packages and Files

● New package: SUNWladm
● Configuration file:
/usr/sadm/lib/localeadm/Locale_config_S10.txt
e. rom
This file contains the actual list of packages included for each region.
The first part of the file is shown below:
ns f
# LOCALE CONFIG FILE
ce on
# ==================
Li si
#
o is
# Solaris 10, Australasia partial locales
t t rm
#
# ( en_AU, en_AU.ISO8859-1, en_NZ, en_NZ.ISO8859-1 )
ec e
#
bj t p
# loc name field is of format:
Su ou
# loc name <region name for locales_installed file> <pkg region name>
<locale na
se ith
me>[,<locale name>...]
c. e w
locname Ausi aua en_AU, en_NZ,
In ut
SUNWauadt aua 1of2

U
s, rib
SUNWauaos aua 2of2c

SUNWauaow aua 1of2c
em ist
SUNWi1cs aua 1of2c

st d
SUNWplow aua 1of2

SUNWplow1 aua 1of2
sy or
SUNWlocaledefsrc aua 2of2

ro e
ic at
#
M lic
# Solaris 10, Central America partial locales

#
n p
Su t du
# ( es_CR, es_CR.ISO8859-1, es_GT, es_GT.ISO8859-1, es_MX, es_MX.ISO8859-

1,
# es_NI, es_NI.ISO8859-1, es_PA, es_PA.ISO8859-1, es_SV, es_SV.ISO8859-1
no
)
#
o
D
locname C_America cam es_CR, es_GT, es_PA, es_SV, es,
SUNW5ttf cam 1of2

SUNWcamdt cam 1of2
SUNWcamos cam 2of2c
SUNWcamow cam 1of2c

SUNWcttf cam 1of2

SUNWesiso1 cam 1of2c
SUNWeuluf cam 1of2c
SUNWgttf cam 2of2
SUNWi15cs cam 1of2c
SUNWi1cs cam 1of2c
e. rom
SUNWi7cs cam 1of2c
SUNWiiimr cam 1of2
ns f
● Configuration file: /usr/sadm/lib/localeadm/admin.
ce on
This file is the response file for the pkgadd command functions
Li si
called by the localeadm command with the add option. The
o is
contents of this file are shown below:
t t rm
mail=
instance=unique
ec e
bj t p
partial=nocheck
runlevel=quit
Su ou
idepend=nocheck
rdepend=nocheck
se ith
space=quit
c. e w
setuid=nocheck
conflict=nocheck
action=nocheck
In ut
U
basedir=default
s, rib
em ist
Requirements, Dependencies, and Limitations

st d
sy or
The locale data editor utility is available with Solaris 10 on both Intel and
SPARC platforms.
ro e
ic at
M lic
Disk space is required for the installation of locale packages when the add
option is used.
n p
Su t du
You cannot remove the C (POSIX) locale from the system using this
application. The application also refuses to remove the locale in which the
no
current user is running.

o
Be aware that you need both Solaris 10 installation CDs and the language
D
CD(s) to fully install the North American (nam) region. If a required CD

image is not found in the path listed with the -d argument, the script
prompts for it. If the image prompted for is not found, you must exit the
script with ^c, and manually delete the /tmp/lock file before you can run
the localeadm command again. Also, the aborted installation will not be
complete.

FAQs
Question: Does the localeadm command work on Intel platforms as well
as on SPARC?
e. rom
Answer: Yes.
Question: Can the localeadm command be used to remove any locale?
ns f
ce on
Answer: No, the C (POSIX) locale and the user’s current geographical
Li si
locale cannot be removed.
o is
t t rm
Question: Is there a record of the localeadm command actions?
ec e
bj t p
Answer: Yes, log files are stored in the /var/sadm/install/logs
directory.
Su ou
se ith
Bugs and Common User Errors
c. e w
There are no known bugs or common user errors.
In ut
U
s, rib
For a current list of bugs, see the following bugtraq category and
subcategories:
em ist
● localeadm/add_rem
st d
● localeadm/admin
sy or
● localeadm/list-query
ro e
ic at
● localeadm/locales
M lic
● localeadm/packages
n p
Su t du
Each time the command is used to add or remove locale packages, it

creates a log file in the /var/sadm/install/logs directory. You can
no
examine the log files to view the specific package changes.

o
D

For More Information

The following references provide additional information on the Solaris
locale data editor:
● ARC case: PSARC 2002/571
e. rom
https://central.sun.net/http://sac.sfbay.sun.com/Archiv
es/CaseLog/arc/PSARC/2002/571/
ns f
ce on
● Project documentation:
Li si
https://central.sun.net/http://globalization.ireland/St
o is
atus/Development/LocaleAdmin/
t t rm
ec e
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

Changes to the Solaris Smartcard Feature

Solaris Smartcard interfaces are a set of public interfaces for smart card
terminals. Card-terminal vendors can implement these interfaces in a
user-level shared library to provide device-level support for their
e. rom
Smartcard terminals in Solaris. The set of Solaris Smartcard terminal
interfaces is based on card terminal interfaces that are available as part of
the Linux Smartcard framework.
ns f
ce on
What Is It?
Li si
o is
t t rm
This section describes four new Solaris Smartcard software enhancements
that have been implemented in the SolarisTM 9 Operating System (Solaris 9
ec e
bj t p
OS) through the Solaris 10 OS:
Support for T=1 smart cards added
Su ou
●
● Smartcard middleware added

●
se ith
Dependence on SCM Microsystems proprietary software eliminated
c. e w
● Standardized storage location for the Javadoc™ tool provided
In ut
U
Support for T=1 Smart Cards

s, rib
em ist
The T=1 protocol is defined in the ISO/IEC standard 7816-4 that specifies
how data is transferred between the card and the reader. Some cards have
st d
been designed to use the T=1 protocol as in improvement over the older
sy or
T=0 protocol. The Solaris 9 OS supported T=1 cards only on external card
readers. This new integration of the T=1 protocol makes it possible to
ro e
ic at
upgrade to Sun BladeTM workstations with internal card readers and still
M lic
use existing T=1 cards.

n p
Su t du
Smartcard Middleware Application Programming Interfaces

(APIs)
no
The Solaris Smartcard Framework (SCF) in Solaris 10 includes a set of

public SCF Application Programming Interfaces (APIs) called Smartcard
o
D
Middleware APIs. The set includes both C and Java™ APIs, which enable
software developers to write Smartcard software for the Solaris OS.

The previous Solaris-specific interfaces to the Smartcard have not

changed. As a result, any applications using the SCF (for example, the
Solaris Smartcard Administration GUI and CDE) continue to function as
they did in the Solaris 9 OS. The Smartcard Middleware APIs are used to
exchange data with a Smartcard by using a Smartcard reader. The APIs
permit an application to communicate with the Smartcard at the lowest
e. rom
level. This is done by allowing the application to send and receive bytes,
or application protocol data units (APDUs), directly to or from the
Smartcard in a Smartcard reader. Any applications written in the Java
ns f
language or in the C language can use these low-level interfaces to
ce on
communicate with a Smartcard in hardware platforms such as Sun Blades
Li si
and Sun Ray™ systems.
o is
t t rm
SCM Dependence
ec e
bj t p
Previously the Solaris 9 OS Smartcard processing was restricted to using
only SmartOS with SCM readers (by contractual agreement with SCM).
Su ou
That dependence has been eliminated.
se ith
Standardized Javadoc™ Storage Location
c. e w
The Javadoc tool was previously stored in project-related directories. The

In ut
new standard directory is:

U
s, rib
/usr/share/javadoc/
em ist
The Smartcard middleware API directory is:

st d
sy or
/usr/share/javadoc/smartcard/
ro e
ic at
The Smartcard middleware API directory contains HTML files and

directories created by the Javadoc tool for Smartcard APIs.
M lic
n p
Su t du
no
o
D

Interface Device Handler
Most of these changes were implemented by creating an Interface Device

(IFD) handler for internal SCM card readers. The scmi2c device driver
supports the T=1 protocol cards in addition to the Open Card Framework
(OCF) cards supported in the Solaris 9 OS. Figure 1-1 on page 1-21 shows
e. rom
the original Solaris Smartcard features on the left (which are unchanged),
and the new IFD features on the right.
ns f
ce on
Li si
o is
t t rm
ec e
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
st d
sy or
ro e
Figure 1-1 IFD Changes to Smartcard Software

ic at
M lic
Configuring the T=1 Smart Card

n p
Su t du
You can configure the T=1 smart card either graphically using the
no
Smartcard Console or on the command line using the smartcard

command. You can also use the command line to add an internal
o
card reader.
D

Configuration Procedure Using the Smartcard Console
Note – When configuring Java cards, you will be asked for the default pin.
It is $$$$java.
e. rom
You can configure the T=1 smart card using the Solaris Smartcard Console
as follows:
ns f
ce on
1. Start the Solaris Smartcard Console.
As root, run the sdtsmartcardadmin command from the command
Li si
line or select sdtsmartcardadmin from the CDE Workspace Tools
o is
menu.
t t rm
2. Click Card Readers in the Navigation pane.
ec e
bj t p
The Add Reader and IFD Terminal icons are displayed in the
Console pane (see Figure 1-2). Icons for any other enabled card
Su ou
reader types are also displayed.
se ith
c. e w
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D
Figure 1-2 Console Pane

3. Double-click Add Reader in the Console pane.

The Add Reader dialog box is displayed (see Figure 1-3). You can
also display the Add Reader dialog box by selecting Add Reader in
the Console pane and choosing Properties in the Action menu.
e. rom
ns f
ce on
Li si
o is
t t rm
ec e
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
st d
sy or
Figure 1-3 Add Reader Dialog Box

ro e
ic at
M lic
n p
Su t du
no
o
D

4. Double-click the IFD Card Terminal Reader to select the Card Reader
and click OK.
The IFD Card Terminal window is displayed (see Figure 1-4):
e. rom
ns f
ce on
Li si
o is
t t rm
ec e
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
M lic
Figure 1-4 IFD Card Terminal Window

n p
Su t du
5. Select the Basic Configuration tab (default selection).

6. Type a name for the reader in the Unique Card Terminal Name
no
field.
o
Leave the current name if you do not want to change the name. Do
D
not include any spaces in the name.

7. From the Device Port pull-down menu, select the port to which the
Card Reader is attached.

8. Enter the IFD handler location in the IFD Handler field.

This is the full-path location of the IFD handler. The IFD handler for
the Internal Reader is in /usr/lib/smartcard/ifdh_scmi2c.so.
9. Click Apply or OK.
A dialog box is displayed, stating that the OCF Server must be
e. rom
restarted to complete the operation (see Figure 1-5):
ns f
ce on
Li si
o is
t t rm
ec e
bj t p
Figure 1-5 Restart OCF Dialog Box
Su ou
se ith
10. Click Restart OCF Now to add the Internal Reader.
The Internal Reader is not added until OCF is killed and restarted
c. e w
(see Figure 1-6).
In ut
U
s, rib
em ist
st d
sy or
ro e
ic at
Figure 1-6 OCF Restarted Dialog Box

M lic
n p
Su t du
no
o
D

The new IFD Terminal is displayed in the Console pane (see

Figure 1-7):
e. rom
ns f
ce on
Li si
o is
t t rm
ec e
bj t p
Su ou
se ith
c. e w
In ut
U
s, rib
em ist
Figure 1-7 IFD Terminal Configured Window

st d
sy or
Configuration Procedure Using the smartcard Command

ro e
You can also configure the T=1 Smart Card on the command line using the
ic at
smartcard command. The smartcard command has the following

M lic
syntax:
n p
Su t du
smartcard -c admin -t terminal -H IFD_handler_location -x add \

-d device_name -r user_friendly_reader_name -n card_reader_mode_name
no
The command line options for the smartcard command are:

o
● The -c admin option – Indicates that you are viewing or modifying

D
OCF properties
● The -t terminal option – Indicates that you are configuring a card
reader
● -H IFD_handler_location option – Specifies the location of the
IFD handler

● The -x add option – Indicates that you are adding a card reader
● The -d device_name option – Specifies the device port where you
have connected the card reader
● The -r user_friendly_reader_name option – Specifies a unique
name for the reader
e. rom
● The -n card_reader_model_name option – Designates the model
name of the card reader
ns f
ce on
Table 1-1 shows the card readers supplied with Sun hardware and the
corresponding model names.
Li si
o is
Table 1-1 Sun Smartcard Reader Model Names
t t rm
Reader Model
ec e
Reader Type Card Terminal Factory Name
bj t p
Name
Su ou
Sun SCRI External com.sun.opencard.terminal.scm. SunSCRI
Card Reader 1 SCMStc.SCMStcCardTerminalFactory
IButton
se ith
com.ibutton.oc.terminal.jib. DS1402
c. e w
iButtonCardTerminalFactory
Sun SCRI Internal SunISCRI
In ut
com.sun.opencard.terminal.scm.
U
Card Reader 1 SCMI2c.SCMI2cCardTerminalFactory
s, rib
em ist
Refer to the smartcard(1M) man page for more information.

st d
sy or
A smartcard Command Example to Add an Internal Card

Reader
ro e
ic at
The Solaris Smartcard software supports an internal card reader, using the
M lic
IFD handler to configure the reader. To add an internal card reader from
n p
the command line, follow these steps.

Su t du
1. Log in as root on the system where you are attaching the card
reader.
no
2. Add the Sun Internal Card Reader by typing, for example, the
o
following command:
D
# smartcard -c admin -t terminal -H /usr/lib/smartcard/ifdh_scmi2c.so \

-x add -d /dev/scmi2c0 -r MyInternalReader -n SunISCRI

The options used in this example are:

● The -H /usr/lib/smartcard/ifdh_scmi2c.so option –
Specifies the location of the IFD handler.
● The -d /dev/scmi2c0 option – Defines the device port where
the card reader is attached. For example, /dev/scmi2cn, where
e. rom
n is the nth Sun internal card reader on the system. Note that all
current systems have only one internal reader. So
/dev/scmi2c0 is currently the only valid choice.
ns f
ce on
● The -r MyInternalReader option – Specifies a unique name
for the Sun internal card reader.
Li si
o is
● The -n SunISCRI option – Indicates the model name for the
t t rm
Sun internal card reader.
3. Stop ocfserv.
ec e
bj t p
# pkill ocfserv
Su ou
The ocfserv process is restarted automatically by the inetd daemon.
se ith
c. e w
Changed Packages and Files
In ut
U
Table 1-2 lists the packages needed to support smart card operations with
s, rib
the Solaris 10 OS.

em ist
Table 1-2 Affected Packages, Files, and Data Structures

st d
sy or
Package, File,
Description
or Structure
ro e
ic at
SUNWjcom Java Communications API for smart card support –

M lic
Java code and native code

n p
SUNWjib Dallas Semiconductor serial iButton OCF card

Su t du
terminal driver
SUNWocf Open Card Framework – Core libraries and utilities
no
SUNWocfr Open Card Framework – Configuration files

o
D
SUNWocfh Open Card Framework – Header files

SUNWpamsc Pluggable Authentication Module (PAM) for smart
card authentication
SUNWscgui Solaris Smartcard Console
SUNWscmhdlr IFD handler for the internal reader

Table 1-3 lists the smart card packages that were used in the Solaris 9 OS
but have been eliminated with the Solaris 10 OS. Some of these packages
have been combined with other packages listed in Table 1-2.
Table 1-3 Solaris 9 OS Smartcard Packages Eliminated in Solaris 10 OS
e. rom
Package
Description
Name
ns f
SUNWjcomx Java Communications API for Smartcard support –
ce on
Native code (64-bit)
Li si
SUNWocfx Open Card Framework – Core libraries (64-bit)
o is
t t rm
SUNWpamsx PAM for Smartcard authentication (64-bit)
SUNWscmos SmartOS used by SCM terminal driver
ec e
bj t p
SUNWscmsc SunTM SCRI OCF card terminal driver
Su ou
se ith
Requirements, Dependencies, and Limitations
c. e w
Two different internal card readers are used on workstations:
In ut
● The SCR403 reader is installed in the Sun Blade 100 and Sun Blade
U
s, rib
1000.
em ist
● The SCR443 reader is installed in the Sun Blade 150.

st d
Only the SCR443 Internal Smart Card Reader can support the T=1
sy or
protocol, so T=1 cards are not supported on Sun Blade 100 and Sun Blade
1000 workstations.
ro e
ic at
M lic
n p
Su t du
no
o
D

Following are requirements and dependencies regarding card readers:

● Any other card reader that is supplied with its own IFD handler can
be used with the Solaris 10 OS.
● All SPARC platforms are supported. The Smartcard feature is not
supported on Intel platforms.
e. rom
● A Smartcard reader (internal or external) and a Smartcard are
required for this feature.
ns f
The Sun Blade 100, 150, 1000, and 2000 workstations have an internal
ce on
●
Smartcard reader that is supported by the existing Solaris SCF.
Li si
● The Sun Ray™ server software 2.0 release includes a terminal device
o is
driver to allow the use of the integrated Smartcard reader on all Sun
t t rm
Ray appliances.
ec e
Generally, any Smartcard, (including Java Card™ technology-
bj t p
●
compliant Smartcards) can be used. Previously only Payflex,
Su ou
Cyberflex, and iButton cards were supported.
FAQ se ith
c. e w
In ut
Question: Can T=1 protocol Smartcards be used with Sun Blade 1000?
U
s, rib
Answer: No, because the Sun Blade 1000 uses the SCR403 Internal Reader,
em ist
which is not compatible with the T=1 protocol.

st d
sy or
ro e
ic at
M lic
n p
Su t du
no
o
D

Bugs and Common User Errors

To troubleshoot Solaris Smartcard software operations and for a list of
current bugs, see the appropriate bugtraq category and subcategories:
e. rom
Category:
● smartcard
ns f
● Subcategories:
ce on
● cardapplets
Li si
o is
● cardterminals
t t rm
● commpackage
ec e
● doc
bj t p
● gui
Su ou
● i18n
se ith
● install
c. e w
● ocf_api
● ocf_commands
In ut
U
● ocfserv
s, rib
● other
em ist
● pam
st d
● scf_api
sy or
● scf_api_test
ro e
ic at
M lic
n p
Su t du
no
o
D

For More Information

The following references provide additional information on the Solaris
Smartcard feature:
● Smartcard changes: http://sac.eng.sun.com/PSARC/2002/505
e. rom
● The Solaris Smartcard Project is covered by PSARC cases 1999/219,
1999/222, and 2002/220
ns f
ce on
● Solaris Smartcard Framework Group: http://smartcard.eng
MUSCLE PC/SC IFD Driver Development Kit:
Li si
●
o is
http://smartcard.eng/docs/ifdhandler-2.12.pdf
t t rm
● PC/SC Specifications Part 3 (describes IFD handler interface):
ec e
http://smartcard.eng/docs/p3v10_ps.pdf
bj t p
● External sites containing other specifications and documents:
Su ou
● Linux MUSCLE Project:
se ith
http://www.linuxnet.com
c. e w
● PC/SC Workgroup:
http://www.pcscworkgroup.com/
In ut
U
Opencard Standards Group:

s, rib
http://www.opencard.org/
em ist
● Sun Microsystems, Inc., Solaris Smartcard Administration Guide [beta

st d
version for Solaris 10 System Administration Collection], part

sy or
number 816-5182
ro e
ic at
M lic
n p
Su t du
no
o
D


Desktop Features

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Desktop Features

Загружено:

Авторское право:

Доступные форматы

e.

Changes in Other Solaris™ 10

Sun Microsystems, Inc.

Export Commodity Classification Number (ECCN) assigned: 2 July 2004

Sun Proprietary: Internal Use Only

L’UTILISER DANS LE CADRE D’UNE AUTO-FORMATION.

Sun Proprietary: Internal Use Only

Locale Data Editor Utility ................................................................. 1-2

What Is It? .................................................................................. 1-2

How to Use the localeadm Command ................................. 1-3

Changed Packages and Files ................................................. 1-15

Requirements, Dependencies, and Limitations.................. 1-16

FAQs ......................................................................................... 1-17

For More Information............................................................ 1-18

Changes to the Solaris Smartcard Feature.................................... 1-19

What Is It? ................................................................................ 1-19

Configuring the T=1 Smart Card .......................................... 1-21

Changed Packages and Files ................................................. 1-28

Bugs and Common User Errors ........................................... 1-31

Sun Proprietary: Internal Use Only

Sun Proprietary: Internal Use Only

Sun Proprietary: Internal Use Only

How Prepared Are You?

Sun Proprietary: Internal Use Only

Sun Proprietary: Internal Use Only

How to Use Course Materials

Sun Proprietary: Internal Use Only

Sun Proprietary: Internal Use Only

Notice the javax.servlet interface is imported to allow access to its

life cycle methods (Line 2).

Courier italics is used for variables and command-line placeholders

that are replaced with a real name or value; for example:

To delete a file, use the rm filename command.

Courier italic bold is used to represent variables whose values are to

be entered by the student as part of an activity; for example:

rights for filename to world, group, and users.

Sun Proprietary: Internal Use Only

Sun Proprietary: Internal Use Only

Locale Data Editor Utility

The locale data editor provides the new localeadm command, an

application for adding and removing locales on a running machine on a

per-region basis (for example, Western European locales) based on the

available for install on specified media (for example, a Solaris CD or

and to exclude any translated-message support packages that would

This tool is a supplement to the locale selection logic in the Solaris

Sun Proprietary: Internal Use Only

This feature does not require any configuration procedure. Two

In the query or list modes, the localeadm command displays information

specified device or directory. The output is given as a list of country or

or regions you want to add or remove.

what locale packages need to be changed and adds or removes them

using the pkgadd or pkgrm commands as appropriate.

If the locales changed are Asian locales, then extra processes—such as

input method server daemons—might need to be started before the new

to do this by either rebooting the machine or manually starting

The localeadm command should be run with root or super-user

Sun Proprietary: Internal Use Only

-a would be aua. This option requires the -d option, with arguments

to specify the device where the installation media is located. If

does not overwrite them but simply skips them.

● -d device [, device2, ...]

Installs or lists locales from packages located in device. The device

variable can be a full path name to a directory containing Solaris

packages or the path to the top directory of a complete Solaris image.