Desktop Features

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Sun Microsystems, Inc.UBRM05-104

500 Eldorado Blvd.Broomfield, CO 80021

U.S.A.

Sun Proprietary: Internal Use Only Revision A

StudentGuide

Changes in Other Solaris™ 10OS Desktop Features

WZI-SS-3603

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

October 15, 2004 4:08 pmaadd

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Sun Proprietary: Internal Use OnlyPlease

Recycle

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, anddecompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization ofSun and its licensors, if any.

Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

Sun, Sun Microsystems, the Sun logo,Sun Blade, Sun Fire, Sun Ray, Solaris, Netra, OpenBoot, Java, Javadoc, and Java Card are trademarksor 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. andother countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.

Federal Acquisitions: Commercial Software – Government Users Subject to Standard License Terms and Conditions

Export Laws. Products, Services, and technical data delivered by Sun may be subject to U.S. export controls or the trade laws of othercountries. You will comply with all such laws and obtain all licenses to export, re-export, or import as may be required after delivery toYou. 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. embargoor terrorist controls as specified in the U.S. export laws. You will not use or provide Products, Services, or technical data for nuclear, missile,or chemical biological weaponry end uses.

DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, ANDWARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSEOR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BELEGALLY INVALID.

THIS MANUAL IS DESIGNED TO SUPPORT AN INSTRUCTOR-LED TRAINING (ILT) COURSE AND IS INTENDED TO BEUSED FOR REFERENCE PURPOSES IN CONJUNCTION WITH THE ILT COURSE. THE MANUAL IS NOT A STANDALONETRAINING TOOL. USE OF THE MANUAL FOR SELF-STUDY WITHOUT CLASS ATTENDANCE IS NOT RECOMMENDED.

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

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Sun Proprietary: Internal Use Only

PleaseRecycle

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.

Sun, Sun Microsystems, le logo Sun, Sun Blade, Sun Fire, Sun Ray, Solaris, Netra, OpenBoot, Java, Javadoc, et Java Card sont des marquesde fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.

Toutes les marques SPARC sont utilisées sous licence sont des marques de fabrique ou des marques déposées de SPARC International, Inc.aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par SunMicrosystems, Inc.

UNIX est une marques déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.

Législation en matière dexportations. Les Produits, Services et données techniques livrés par Sun peuvent être soumis aux contrôlesaméricains sur les exportations, ou à la législation commerciale dautres pays. Nous nous conformerons à lensemble de ces textes et nousobtiendrons toutes licences dexportation, de ré-exportation ou dimportation susceptibles dêtre requises après livraison à Vous. Vousnexporterez, ni ne ré-exporterez en aucun cas à des entités figurant sur les listes américaines dinterdiction dexportation les plus courantes,ni vers un quelconque pays soumis à embargo par les Etats-Unis, ou à des contrôles anti-terroristes, comme prévu par la législationaméricaine en matière dexportations. Vous nutiliserez, ni ne fournirez les Produits, Services ou données techniques pour aucune utilisationfinale liée aux armes nucléaires, chimiques ou biologiques ou aux missiles.

LA DOCUMENTATION EST FOURNIE “EN L’ETAT” ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIESEXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, YCOMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNEUTILISATION 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 UNINSTRUCTEUR (ILT). IL NE S’AGIT PAS D’UN OUTIL DE FORMATION INDÉPENDANT. NOUS VOUS DÉCONSEILLONS DEL’UTILISER DANS LE CADRE D’UNE AUTO-FORMATION.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Sun Proprietary: Internal Use Onlyv

Copyright 2004 Sun Microsystems, Inc. All Rights Reserved. SunU, Revision A

Table of Contents

About This Course ..............................................................Preface-viiCourse Goals......................................................................... Preface-viiHow Prepared Are You?....................................................... Preface-ixIntroductions ........................................................................... Preface-xHow to Use Course Materials .............................................. Preface-xiConventions ...........................................................................Preface-xii

Typographical Conventions ......................................Preface-xiii

Changes in Other Solaris™ 10 OS Desktop Features...................1-1Objectives ........................................................................................... 1-1Locale Data Editor Utility ................................................................. 1-2

What Is It? .................................................................................. 1-2How to Use the localeadm Command ................................. 1-3Command Options ................................................................... 1-4Changed Packages and Files ................................................. 1-15Requirements, Dependencies, and Limitations.................. 1-16FAQs ......................................................................................... 1-17Bugs and Common User Errors ............................................ 1-17For More Information............................................................ 1-18

Changes to the Solaris Smartcard Feature.................................... 1-19What Is It? ................................................................................ 1-19Configuring the T=1 Smart Card.......................................... 1-21Changed Packages and Files ................................................. 1-28Requirements, Dependencies, and Limitations.................. 1-29FAQ ........................................................................................... 1-30Bugs and Common User Errors ........................................... 1-31For More Information............................................................ 1-32

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Sun Proprietary: Internal Use OnlyPreface-vii


Preface

About This Course

Course Goals

Upon completion of this course, you should be able to identify changes toother desktop features for the Solaris 10 OS.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Course Goals

Sun Proprietary: Internal Use OnlyPreface-viii Changes in Other Solaris™ 10 OS Desktop Features


Course Map

The following course map enables you to see what you haveaccomplished and where you are going in reference to the course goals.

Changes in OtherSolaris™ 10 OSDesktop Features

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

How Prepared Are You?

Sun Proprietary: Internal Use OnlyAbout This Course Preface-ixCopyright 2004 Sun Microsystems, Inc. All Rights Reserved. SunU, Revision A

How Prepared Are You?

To be sure you are prepared to take this course, can you answer yes to thefollowing questions?

● Can you support the Solaris 9 Operating System?

● Can you create and edit text files using a text editor?

● Can you use a World Wide Web (WWW) browser?

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Introductions

Sun Proprietary: Internal Use OnlyPreface-x Changes in Other Solaris™ 10 OS Desktop Features


Introductions

Now that you have been introduced to the course, introduce yourself tothe other students and the instructor, addressing the following items:

● Name

● Company affiliation

● Title, function, and job responsibility

● Experience related to topics presented in this course

● Reasons for enrolling in this course

● Expectations for this course.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

How to Use Course Materials

Sun Proprietary: Internal Use OnlyAbout This Course Preface-xiCopyright 2004 Sun Microsystems, Inc. All Rights Reserved. SunU, Revision A

How to Use Course Materials

To enable you to succeed in this course, these course materials contain alearning module that is composed of the following components:

● Goals – You should be able to accomplish the goals after finishingthis course and meeting all of its objectives.

● Objectives – You should be able to accomplish the objectives aftercompleting a portion of instructional content. Objectives supportgoals and can support other higher-level objectives.

● Lecture – The instructor presents information specific to the objectiveof the module. This information helps you learn the knowledge andskills necessary to succeed with the activities.

● Activities – The activities take various forms, such as reviewquestions, exercises, self-checks, discussion, and demonstrations.Activities help you facilitate the mastery of an objective.

● Visual aids – The instructor might use several visual aids to convey aconcept, such as a process, in a visual form. Visual aids commonlycontain graphics, animation, and video.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Conventions

Sun Proprietary: Internal Use OnlyPreface-xii Changes in Other Solaris™ 10 OS Desktop Features


Conventions

The following conventions are used in this course to represent varioustraining elements and alternative learning resources.

Icons

Note – Indicates additional information that can help students but is notcrucial to their understanding of the concept being described. Studentsshould be able to understand the concept or complete the task withoutthis information. Examples of notational information include keywordshortcuts and minor system adjustments.

Caution – Indicates that there is a risk of personal injury from anonelectrical hazard, or risk of irreversible damage to data, software, orthe operating system. A caution indicates that the possibility of a hazard(as opposed to certainty) might happen, depending on the action of theuser.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Conventions

Sun Proprietary: Internal Use OnlyAbout This Course Preface-xiiiCopyright 2004 Sun Microsystems, Inc. All Rights Reserved. SunU, Revision A

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.system% You have mail .

Courier is also used to indicate programming constructs, such as classnames, methods, and keywords; for example:

The getServletInfo method is used to get author information.The java.awt.Dialog class contains Dialog constructor.

Courier bold is used for characters and numbers that you type; forexample:

To list the files in this directory, type:# ls

Courier bold is also used for each line of programming code that isreferenced in a textual description; for example:

1 import java.io.*;2 import javax.servlet.*;3 import javax.servlet.http.*;

Notice the javax.servlet interface is imported to allow access to itslife cycle methods (Line 2).

Courier italics is used for variables and command-line placeholdersthat 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 tobe entered by the student as part of an activity; for example:

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

Palatino italics is used for book titles, new words or terms, or words thatyou want to emphasize; for example:

Read Chapter 6 in the User’s Guide.These are called class options.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Sun Proprietary: Internal Use Only1-1


Module 1

Changes in Other Solaris™ 10 OS DesktopFeatures

Objectives

This module provides an overview of the new desktop features includedin the Solaris 10 OS.

Upon completion of this module, you should be able to:

● Identify features of the locale data editor utility

● Identify changes to the Solaris 10 OS Smartcard feature

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Locale Data Editor Utility

Sun Proprietary: Internal Use Only1-2 Changes in Other Solaris™ 10 OS Desktop Features



This section describes the new locale data editor feature in the Solaris10 OS.

What Is It?

The locale data editor is a utility that allows you to query and configurethe locales for a Solaris OS through a command-line interface. Using thelocaleadm tool, you can display information about locale packages thatare installed on the system or that reside on a particular device ordirectory. The super-user can also add and remove locales on the currentsystem on a per-region basis.

Brief Description

Previously in Solaris there was no easy way to change locales on amachine after installation. The only option available for choosing localeswas provided during the Solaris install process. After this, you had to addand remove individual packages to change the locales on the machine.This was cumbersome and prone to error because there was no definitivelist of the packages needed for each locale, and it was easy to overlooka package.

Features

The locale data editor provides the new localeadm command, anapplication for adding and removing locales on a running machine on aper-region basis (for example, Western European locales) based on thestructure of Solaris packages. The application reads the list of locales thatare currently on the system, and, optionally, reads the list of packagesavailable for install on specified media (for example, a Solaris CD ornetwork drive). It then offers the choice to add or remove locale regionsbased on these lists. You also have the option to add support for a localeand to exclude any translated-message support packages that wouldnormally be included for that locale. If you choose to exclude the optionalmessage support packages, you can to use the tool to add them at alater time.

This tool is a supplement to the locale selection logic in the Solarisinstaller. The installer is still the primary application for the correctinstallation of Solaris locales.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.


Sun Proprietary: Internal Use OnlyChanges in Other Solaris™ 10 OS Desktop Features 1-3Copyright 2004 Sun Microsystems, Inc. All Rights Reserved. SunU, Revision A

Configuration Procedure

This feature does not require any configuration procedure. Twoconfiguration files do exist:

● /usr/sadm/lib/localeadm/Locale_config_S10.txt

● /usr/sadm/lib/localeadm/admin

The utility creates log files of the following form:

● /var/sadm/install/logs/localeadmin_install. date

● /var/sadm/install/logs/localeadmin_uninstall. date

The date field has this format: YYYY_MM_DD. If multiple installs are donein one day, the date has a number appended to it; for example,2004_10_20.1 , 2004_10_20.2 .

How to Use the localeadm Command

You can use the localeadm command in query or list modes, or to addand remove locales on a Solaris system.

In the query or list modes, the localeadm command displays informationabout locale packages that are installed on the system or that reside on aspecified device or directory. The output is given as a list of country orregion names rather than a list of packages, to make it easier to pick thelocales to change. You can then use this output to determine which localesor regions you want to add or remove.

When you specify a locale or region to add or remove using the namegiven by the output of the list mode, the localeadm command calculateswhat locale packages need to be changed and adds or removes themusing the pkgadd or pkgrm commands as appropriate.

If the locales changed are Asian locales, then extra processes—such asinput method server daemons—might need to be started before the newlocale(s) work properly. When the locales are installed, you are promptedto do this by either rebooting the machine or manually startingthe daemons.

The localeadm command should be run with root or super-userprivileges to add or remove locales or regions.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




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 aninstall media, sorted by geographic region. If used with the -doption, the localeadm command lists all locales and regionsavailable on the device pointed to by the option argument(s) of the-d option. If used without the -d option, it lists all locales/regionsinstalled on the current system.

● -q locale | region

Queries the system to see if locale locale or geographic regionregion is already installed. The expected input for a locale or regionname is the name displayed by the -l option.

● -a locale | region

Adds the packages for a locale locale or geographic region regionto the system. The expected input for a locale or region name is theshort name displayed by the -l option. For example, for the listingoutput "Australasia (aua) " from the -l option, the argument for-a would be aua . This option requires the -d option, with argumentsto specify the device where the installation media is located. Ifnecessary packages are already installed, the localeadm commanddoes not overwrite them but simply skips them.

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

Installs or lists locales from packages located in device . The devicevariable can be a full path name to a directory containing Solarispackages or the path to the top directory of a complete Solaris image.It can also be a device alias such as /cdrom/cdrom0 , a devicenickname as defined by the eject command, or an alternativedevice nickname such as cdrom , dvd , or dvdrom .

● -r locale | region

Removes the packages for a locale locale or geographic regionregion from the system. The expected input for a locale or regionname is the name displayed by the -l option.

● -R root_path

Defines the full path name of a directory to use as the root path. Allfiles, including package system information files, are relocated to adirectory tree starting in the specified root_path . You can specifythe root_path when installing to a client from a server.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



Additional command options are described in the localeadm commandman page.

The locale and region Option Arguments

The following is a more detailed explanation of the locale and regionoption arguments:

● The locale argument – The name of a locale to be added to orremoved from the system. The expected input for a locale name isthe name displayed by the -l option in list mode with the -c flag(-lc ). For example, to install Spanish, use es_ES.ISO8859-1 or justes_ES.

Note – To allow differentiation between full and partial locales, es is not avalid locale choice.

If a locale name is given for the option, you receive a warning that alllocales for the region of which the locale is a member will beadded/removed. For example, if you choose to install Swedish, thenall of the locales for the Northern Europe region (of which Sweden isa member) will be installed. The locale option is only given forbackward compatibility.

● The region argument – The name of a geographic region to beadded to or removed from the system. The expected input format ofa region name is the name displayed by the -l option with the -sflag (-ls ). For example, to install the South American locales, uselocaleadm -a sam . All of the locales listed for a given geographicregion will be installed with the region. Region is the preferred formof reference.

Command Examples

The following examples show commands used to:

● List locales available on installation media

● Add a locale

● Use the query option

● Display the install log file

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




Listing locales available on the /export/install directory:

# localeadm -l -d /export/install

Devices are /export/installChecking for installed packages. This could take a while.

Checking for Australasia region (aua)(of2c packages)|...|All packages found.

Checking for Australasia region (aua)(1of2 packages)|.....|All packages found.

Checking for Australasia region (aua)(2of2 packages)|..|All packages found.

Checking for Australasia region (aua)(langcd1 packages)||All packages found.

Checking for Central America region (cam)(of2c packages)|.........|All packages found.

Checking for Central America region (cam)(1of2 packages)|..................|All packages found.

Checking for Central America region (cam)(2of2 packages)|.......|All packages found.

Checking for Central America region (cam)(langcd1 packages)|........................................|All packages found.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



Checking for Central Europe region (ceu)(of2c packages)|.......|All packages found.

[many lines deleted for brevity]

Checking for Hindi region (hi_in)(langcd1 packages)||All packages found.

-----------------The following regions are installed on proto144 on Sat Jul 24 18:29:28MDT 2004

POSIX (C)

Australasia (aua)[ Australia, New Zealand ]

Central America (cam)[ Costa Rica, Guatemala, Nicaragua, Panama, El Salvador ]

Central Europe (ceu)[ Austria, Czech Republic, Germany, Hungary, Poland, Slovakia,Switzerland (German), Switzerland (French) ]

Eastern Europe (eeu)[ Albania, Bosnia, Bulgaria, Estonia, Croatia, Lithuania, Latvia,Macedonia, Romania, Russia, Serbia, Slovenia, Turkey ]

Middle East (mea)[ Israel ]

Northern Africa (naf)[ Egypt ]

North America (nam)[ Canada (English), Canada (French), United States, Mexico ]

Northern Europe (neu)

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




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

South America (sam)[ Argentina, Bolivia, Brazil, Chile, Columbia, Ecuador, Paraguay, Peru,Uraguay, Venezuela ]

Southern Europe (seu)[ Italy, Greece, Portugal, Spain (Catalan), Spain (Spanish) ]

Western Europe (weu)[France, Holland, Belgium (French), Belgium (Flemish), Ireland, England ]

Japanese (ja)

Korean (ko)

Simplified Chinese (zh_cn)

Traditional Chinese (Hong Kong) (zh_hk)

Traditional Chinese (zh_tw)

Thai (th_th)

Hindi (hi_in)

Done.A copy of this report can be found in/usr/sadm/lib/localeadm/locales.list#

Adding a locale:

# localeadm -a aua -d /export/installLog file is /var/sadm/install/logs/localeadmin_install.2004-07-24

locale/region name is auaAdding packages for Australasia (aua) Region aua will be installed.installing 1of2Operating System is Solaris 10Checking for a valid disk image:Devices are /export/installChecking for a 1of2 image|.....|

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



We have a 1of2:/export/install/Solaris_10/ProductChecking package SUNWauadt......Adding package SUNWauadtProcessing package instance <SUNWauadt> from</export/install/Solaris_10/Product>Australasia CDE Support(sparc) 1.0,REV=2001.03.06.18.03Using </usr> as the package base directory.## Processing package information.## Processing system information. 2 package pathnames are already properly installed.## Verifying disk space requirements.Installing Australasia CDE Support as <SUNWauadt>## Installing part 1 of 1./usr/dt/config/en_AU <symbolic link>[ verifying class <none> ]Installation of <SUNWauadt> was successful.Checking package SUNWauaow......Adding package SUNWauaowProcessing package instance <SUNWauaow> from</export/install/Solaris_10/Product>Australasia OW Support(sparc) 1.0,REV=2004.03.03.14.07Using </usr> as the package base directory.## Processing package information.## Processing system information. 5 package pathnames are already properly installed.## Verifying disk space requirements.Installing Australasia OW Support as <SUNWauaow>## Executing preinstall script.## Installing part 1 of 1./usr/openwin/lib/locale/en_AU <symbolic link>/usr/openwin/lib/locale/en_AU.ISO8859-1/libs <symbolic link>/usr/openwin/lib/locale/en_AU.ISO8859-1/xview/.text_extras_menu <symboliclink>/usr/openwin/lib/locale/en_NZ <symbolic link>/usr/openwin/lib/locale/en_NZ.ISO8859-1/libs <symbolic link>/usr/openwin/lib/locale/en_NZ.ISO8859-1/xview/.text_extras_menu <symboliclink>[ verifying class <none> ]Installation of <SUNWauaow> was successful.Checking package SUNWi1cs......Adding package SUNWi1csProcessing package instance <SUNWi1cs> from</export/install/Solaris_10/Product>

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




X11 ISO8859-1 Codeset Support(sparc) 2.0,REV=2002.07.15.14.45Using </> as the package base directory.## Processing package information.## Processing system information. 8 package pathnames are already properly installed.## Verifying disk space requirements.Installing X11 ISO8859-1 Codeset Support as <SUNWi1cs>## Installing part 1 of 1.Installation of <SUNWi1cs> was successful.Checking package SUNWplow......Adding package SUNWplowProcessing package instance <SUNWplow> from</export/install/Solaris_10/Product>OpenWindows enabling for Partial Locales(sparc) 1.0,REV=2004.03.31.10.36Using </usr> as the package base directory.## Processing package information.## Processing system information. 5 package pathnames are already properly installed.## Verifying disk space requirements.Installing OpenWindows enabling for Partial Locales as <SUNWplow>## Executing preinstall script.## Installing part 1 of 1.[ verifying class <none> ][ verifying class <Xupdate> ]Installation of <SUNWplow> was successful.Checking package SUNWplow1......Adding package SUNWplow1Processing package instance <SUNWplow1> from</export/install/Solaris_10/Product>OpenWindows enabling for Supplementary Partial Locales(sparc) 1.0,REV=2004.03.01.09.49Using </usr> as the package base directory.## Processing package information.## Processing system information. 4 package pathnames are already properly installed.## Verifying disk space requirements.Installing OpenWindows enabling for Supplementary Partial Locales as<SUNWplow1>## Installing part 1 of 1.[ verifying class <none> ]Installation of <SUNWplow1> was successful.installing 2of2Operating System is Solaris 10Checking for a valid disk image:

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



Devices are /export/installChecking for a 2of2 image|..|We have a 2of2:/export/install/Solaris_10/ProductChecking package SUNWauaos......Adding package SUNWauaosProcessing package instance <SUNWauaos> from</export/install/Solaris_10/Product>Australasia OS Support(sparc) 11.10.0,REV=2003.12.08.12.05Using </> as the package base directory.## Processing package information.## Processing system information. 3 package pathnames are already properly installed.## Verifying disk space requirements.Installing Australasia OS Support as <SUNWauaos>## Installing part 1 of 1.Installation of <SUNWauaos> was successful.Checking package SUNWlocaledefsrc......Adding package SUNWlocaledefsrcProcessing package instance <SUNWlocaledefsrc> from</export/install/Solaris_10/Product>EMEA localedef source files(sparc) 11.10.0,REV=2002.10.09.11.28Using </> as the package base directory.## Processing package information.## Processing system information. 4 package pathnames are already properly installed.## Verifying disk space requirements.Installing EMEA localedef source files as <SUNWlocaledefsrc>## Installing part 1 of 1.Installation of <SUNWlocaledefsrc> was successful.installing langcd1Operating System is Solaris 10Checking for a valid disk image:Devices are /export/installChecking for a langcd imageWe don't need a langcdregion name is AusiGEOS=Ausi,LOCALES=en_NZ,en_AU,Checking for Australasia region (aua)(of2c packages)|...|All packages found.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




Checking for Central America region (cam)(of2c packages)|.........|Not all packages found (1 out of 9).

Checking for Central Europe region (ceu)(of2c packages)|.......|Not all packages found (1 out of 7).

[truncated output]

Note – Note that the command apparently checks for installed regionseven if only an add operation was requested.

-----------------

The following regions are installed on proto144 on Sat Jul 24 18:34:12MDT 2004

POSIX (C)

Australasia (aua)

One or more locales have been added. To update the list of localesavailable at the login screen's "Options->Language" menu, please restartthe dtlogin daemon (WARNING: this will terminate any active dtloginsessions)

Please log out and login again to use the new locale(s) at your desktop.If you are not intending to use the new locale(s) with the GUI desktop,you can start using the new locale(s) immediately by setting the LC_*environment variables.

#

Using the query option:

# localeadm -q aua

locale/region name is auaChecking for Australasia region (aua)(of2c packages)

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



|...|All packages found.

Checking for Australasia region (aua)(1of2 packages)|.....|All packages found.

Checking for Australasia region (aua)(2of2 packages)|..|All packages found.

Checking for Australasia region (aua)(langcd1 packages)||All packages found.

The Australasia region (aua) is installed on this system

# cat /var/sadm/install/logs/localeadmin_install.2004-07-24Sat Jul 24 18:33:33 MDT 2004Operation=installlocale/region name is auaAdding packages for Australasia (aua) Region aua will be installed.Install_Dir=Region=aua

Checking for a valid disk image:Checking for a 1of2 imageWe have a 1of2:/export/install/Solaris_10/ProductAdding package SUNWauadtAdding package SUNWauaowAdding package SUNWi1csAdding package SUNWplowAdding package SUNWplow1Checking for a valid disk image:Checking for a 2of2 imageWe have a 2of2:/export/install/Solaris_10/ProductAdding package SUNWauaosAdding package SUNWlocaledefsrcChecking for a valid disk image:Checking for a langcd image

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




We don't need a langcdChecking for Australasia region (aua)(of2c packages)Checking for Australasia region (aua)(1of2 packages)Checking for Australasia region (aua)(2of2 packages)Checking for Australasia region (aua)(langcd1 packages)Checking for Central America region (cam)(of2c packages)Checking for Central Europe region (ceu)(of2c packages)Checking for Eastern Europe region (eeu)(of2c packages)Checking for Middle East region (mea)(of2c packages)Checking for Northern Africa region (naf)(of2c packages)Checking for North America region (nam)(of2c packages)Checking for Northern Europe region (neu)(of2c packages)Checking for South America region (sam)(of2c packages)Checking for Southern Europe region (seu)(of2c packages)Checking for Western Europe region (weu)(of2c packages)Checking for Japanese region (ja)(of2c packages)Checking for Korean region (ko)(of2c packages)Checking for Simplified Chinese region (zh_cn)(of2c packages)Checking for Traditional Chinese (Hong Kong) region (zh_hk)(of2c packages)Checking for Traditional Chinese region (zh_tw)(of2c packages)Checking for Thai region (th_th)(of2c packages)Checking for Hindi region (hi_in)(of2c packages)#

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



Changed Packages and Files

● New package: SUNWladm

● Configuration file:/usr/sadm/lib/localeadm/Locale_config_S10.txt

This file contains the actual list of packages included for each region.The first part of the file is shown below:

# LOCALE CONFIG FILE# ==================## Solaris 10, Australasia partial locales## ( en_AU, en_AU.ISO8859-1, en_NZ, en_NZ.ISO8859-1 )## loc name field is of format:# loc name <region name for locales_installed file> <pkg region name><locale name>[,<locale name>...]

locname Ausi aua en_AU, en_NZ,

SUNWauadt aua 1of2SUNWauaos aua 2of2cSUNWauaow aua 1of2cSUNWi1cs aua 1of2cSUNWplow aua 1of2SUNWplow1 aua 1of2SUNWlocaledefsrc aua 2of2

## Solaris 10, Central America partial locales## ( 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)#

locname C_America cam es_CR, es_GT, es_PA, es_SV, es,

SUNW5ttf cam 1of2SUNWcamdt cam 1of2SUNWcamos cam 2of2cSUNWcamow cam 1of2c

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




SUNWcttf cam 1of2SUNWesiso1 cam 1of2cSUNWeuluf cam 1of2cSUNWgttf cam 2of2SUNWi15cs cam 1of2cSUNWi1cs cam 1of2cSUNWi7cs cam 1of2cSUNWiiimr cam 1of2

● Configuration file: /usr/sadm/lib/localeadm/admin.

This file is the response file for the pkgadd command functionscalled by the localeadm command with the add option. Thecontents of this file are shown below:

mail=instance=uniquepartial=nocheckrunlevel=quitidepend=nocheckrdepend=nocheckspace=quitsetuid=nocheckconflict=nocheckaction=nocheckbasedir=default

Requirements, Dependencies, and Limitations

The locale data editor utility is available with Solaris 10 on both Intel andSPARC platforms.

Disk space is required for the installation of locale packages when the addoption is used.

You cannot remove the C (POSIX) locale from the system using thisapplication. The application also refuses to remove the locale in which thecurrent user is running.

Be aware that you need both Solaris 10 installation CDs and the languageCD(s) to fully install the North American (nam) region. If a required CDimage is not found in the path listed with the -d argument, the scriptprompts for it. If the image prompted for is not found, you must exit thescript with ^c , and manually delete the /tmp/lock file before you can runthe localeadm command again. Also, the aborted installation will not becomplete.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



FAQs

Question: Does the localeadm command work on Intel platforms as wellas on SPARC?

Answer: Yes.

Question: Can the localeadm command be used to remove any locale?

Answer: No, the C (POSIX) locale and the user’s current geographicallocale cannot be removed.

Question: Is there a record of the localeadm command actions?

Answer: Yes, log files are stored in the /var/sadm/install/logsdirectory.

Bugs and Common User Errors

There are no known bugs or common user errors.

For a current list of bugs, see the following bugtraq category andsubcategories:

● localeadm/add_rem

● localeadm/admin

● localeadm/list-query

● localeadm/locales

● localeadm/packages

Each time the command is used to add or remove locale packages, itcreates a log file in the /var/sadm/install/logs directory. You canexamine the log files to view the specific package changes.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




For More Information

The following references provide additional information on the Solarislocale data editor:

● ARC case: PSARC 2002/571

https://central.sun.net/http://sac.sfbay.sun.com/Archives/CaseLog/arc/PSARC/2002/571/

● Project documentation:

https://central.sun.net/http://globalization.ireland/Status/Development/LocaleAdmin/

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.

Changes to the Solaris Smartcard Feature



Solaris Smartcard interfaces are a set of public interfaces for smart cardterminals. Card-terminal vendors can implement these interfaces in auser-level shared library to provide device-level support for theirSmartcard terminals in Solaris. The set of Solaris Smartcard terminalinterfaces is based on card terminal interfaces that are available as part ofthe Linux Smartcard framework.

What Is It?

This section describes four new Solaris Smartcard software enhancementsthat have been implemented in the SolarisTM 9 Operating System (Solaris 9OS) through the Solaris 10 OS:

● Support for T=1 smart cards added

● Smartcard middleware added

● Dependence on SCM Microsystems proprietary software eliminated

● Standardized storage location for the Javadoc™ tool provided

Support for T=1 Smart Cards

The T=1 protocol is defined in the ISO/IEC standard 7816-4 that specifieshow data is transferred between the card and the reader. Some cards havebeen designed to use the T=1 protocol as in improvement over the olderT=0 protocol. The Solaris 9 OS supported T=1 cards only on external cardreaders. This new integration of the T=1 protocol makes it possible toupgrade to Sun BladeTM workstations with internal card readers and stilluse existing T=1 cards.

Smartcard Middleware Application Programming Interfaces(APIs)

The Solaris Smartcard Framework (SCF) in Solaris 10 includes a set ofpublic SCF Application Programming Interfaces (APIs) called SmartcardMiddleware APIs. The set includes both C and Java™ APIs, which enablesoftware developers to write Smartcard software for the Solaris OS.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




The previous Solaris-specific interfaces to the Smartcard have notchanged. As a result, any applications using the SCF (for example, theSolaris Smartcard Administration GUI and CDE) continue to function asthey did in the Solaris 9 OS. The Smartcard Middleware APIs are used toexchange data with a Smartcard by using a Smartcard reader. The APIspermit an application to communicate with the Smartcard at the lowestlevel. This is done by allowing the application to send and receive bytes,or application protocol data units (APDUs), directly to or from theSmartcard in a Smartcard reader. Any applications written in the Javalanguage or in the C language can use these low-level interfaces tocommunicate with a Smartcard in hardware platforms such as Sun Bladesand Sun Ray™ systems.

SCM Dependence

Previously the Solaris 9 OS Smartcard processing was restricted to usingonly SmartOS with SCM readers (by contractual agreement with SCM).That dependence has been eliminated.

Standardized Javadoc™ Storage Location

The Javadoc tool was previously stored in project-related directories. Thenew standard directory is:

/usr/share/javadoc/

The Smartcard middleware API directory is:

/usr/share/javadoc/smartcard/

The Smartcard middleware API directory contains HTML files anddirectories created by the Javadoc tool for Smartcard APIs.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



Interface Device Handler

Most of these changes were implemented by creating an Interface Device(IFD) handler for internal SCM card readers. The scmi2c device driversupports 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 showsthe original Solaris Smartcard features on the left (which are unchanged),and the new IFD features on the right.

Figure 1-1 IFD Changes to Smartcard Software

Configuring the T=1 Smart Card

You can configure the T=1 smart card either graphically using theSmartcard Console or on the command line using the smartcardcommand. You can also use the command line to add an internalcard reader.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




Configuration Procedure Using the Smartcard Console

Note – When configuring Java cards, you will be asked for the default pin.It is $$$$java.

You can configure the T=1 smart card using the Solaris Smartcard Consoleas follows:

1. Start the Solaris Smartcard Console.

As root , run the sdtsmartcardadmin command from the commandline or select sdtsmartcardadmin from the CDE Workspace Toolsmenu.

2. Click Card Readers in the Navigation pane.

The Add Reader and IFD Terminal icons are displayed in theConsole pane (see Figure 1-2). Icons for any other enabled cardreader types are also displayed.

Figure 1-2 Console Pane

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



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

The Add Reader dialog box is displayed (see Figure 1-3). You canalso display the Add Reader dialog box by selecting Add Reader inthe Console pane and choosing Properties in the Action menu.

Figure 1-3 Add Reader Dialog Box

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




4. Double-click the IFD Card Terminal Reader to select the Card Readerand click OK.

The IFD Card Terminal window is displayed (see Figure 1-4):

Figure 1-4 IFD Card Terminal Window

5. Select the Basic Configuration tab (default selection).

6. Type a name for the reader in the Unique Card Terminal Namefield.

Leave the current name if you do not want to change the name. Donot include any spaces in the name.

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

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



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

This is the full-path location of the IFD handler. The IFD handler forthe 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 berestarted to complete the operation (see Figure 1-5):

Figure 1-5 Restart OCF Dialog Box

10. Click Restart OCF Now to add the Internal Reader.

The Internal Reader is not added until OCF is killed and restarted(see Figure 1-6).

Figure 1-6 OCF Restarted Dialog Box

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




The new IFD Terminal is displayed in the Console pane (seeFigure 1-7):

Figure 1-7 IFD Terminal Configured Window

Configuration Procedure Using the smartcard Command

You can also configure the T=1 Smart Card on the command line using thesmartcard command. The smartcard command has the followingsyntax:

smartcard -c admin -t terminal -H IFD_handler_location -x add \-d device_name -r user_friendly_reader_name -n card_reader_mode_name

The command line options for the smartcard command are:

● The -c admin option – Indicates that you are viewing or modifyingOCF properties

● The -t terminal option – Indicates that you are configuring a cardreader

● -H IFD_handler_location option – Specifies the location of theIFD handler

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



● The -x add option – Indicates that you are adding a card reader

● The -d device_name option – Specifies the device port where youhave connected the card reader

● The -r user_friendly_reader_name option – Specifies a uniquename for the reader

● The -n card_reader_model_name option – Designates the modelname of the card reader

Table 1-1 shows the card readers supplied with Sun hardware and thecorresponding model names.

Refer to the smartcard (1M) man page for more information.

A smartcard Command Example to Add an Internal CardReader

The Solaris Smartcard software supports an internal card reader, using theIFD handler to configure the reader. To add an internal card reader fromthe command line, follow these steps.

1. Log in as root on the system where you are attaching the cardreader.

2. Add the Sun Internal Card Reader by typing, for example, thefollowing command:

# smartcard -c admin -t terminal -H /usr/lib/smartcard/ifdh_scmi2c.so \-x add -d /dev/scmi2c0 -r MyInternalReader -n SunISCRI

Table 1-1 Sun Smartcard Reader Model Names

Reader Type Card Terminal Factory Name Reader ModelName

Sun SCRI ExternalCard Reader 1

com.sun.opencard.terminal.scm.SCMStc.SCMStcCardTerminalFactory

SunSCRI

IButton com.ibutton.oc.terminal.jib.iButtonCardTerminalFactory

DS1402

Sun SCRI InternalCard Reader 1

com.sun.opencard.terminal.scm.SCMI2c.SCMI2cCardTerminalFactory

SunISCRI

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




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 wherethe card reader is attached. For example, /dev/scmi2c n, wheren is the nth Sun internal card reader on the system. Note that allcurrent systems have only one internal reader. So/dev/scmi2c0 is currently the only valid choice.

● The -r MyInternalReader option – Specifies a unique namefor the Sun internal card reader.

● The -n SunISCRI option – Indicates the model name for theSun internal card reader.

3. Stop ocfserv .

# pkill ocfserv

The ocfserv process is restarted automatically by the inetd daemon.

Changed Packages and Files

Table 1-2 lists the packages needed to support smart card operations withthe Solaris 10 OS.

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

Package, File,or Structure Description

SUNWjcom Java Communications API for smart card support –Java code and native code

SUNWjib Dallas Semiconductor serial iButton OCF cardterminal driver

SUNWocf Open Card Framework – Core libraries and utilities

SUNWocfr Open Card Framework – Configuration files

SUNWocfh Open Card Framework – Header files

SUNWpamsc Pluggable Authentication Module (PAM) for smartcard authentication

SUNWscgui Solaris Smartcard Console

SUNWscmhdlr IFD handler for the internal reader

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



Table 1-3 lists the smart card packages that were used in the Solaris 9 OSbut have been eliminated with the Solaris 10 OS. Some of these packageshave been combined with other packages listed in Table 1-2.

Requirements, Dependencies, and Limitations

Two different internal card readers are used on workstations:

● The SCR403 reader is installed in the Sun Blade 100 and Sun Blade1000.

● The SCR443 reader is installed in the Sun Blade 150.

Only the SCR443 Internal Smart Card Reader can support the T=1protocol, so T=1 cards are not supported on Sun Blade 100 and Sun Blade1000 workstations.

Table 1-3 Solaris 9 OS Smartcard Packages Eliminated in Solaris 10 OS

PackageName Description

SUNWjcomx Java Communications API for Smartcard support –Native code (64-bit)

SUNWocfx Open Card Framework – Core libraries (64-bit)

SUNWpamsx PAM for Smartcard authentication (64-bit)

SUNWscmos SmartOS used by SCM terminal driver

SUNWscmsc SunTM SCRI OCF card terminal driver

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




Following are requirements and dependencies regarding card readers:

● Any other card reader that is supplied with its own IFD handler canbe used with the Solaris 10 OS.

● All SPARC platforms are supported. The Smartcard feature is notsupported on Intel platforms.

● A Smartcard reader (internal or external) and a Smartcard arerequired for this feature.

● The Sun Blade 100, 150, 1000, and 2000 workstations have an internalSmartcard reader that is supported by the existing Solaris SCF.

● The Sun Ray™ server software 2.0 release includes a terminal devicedriver to allow the use of the integrated Smartcard reader on all SunRay appliances.

● Generally, any Smartcard, (including Java Card™ technology-compliant Smartcards) can be used. Previously only Payflex,Cyberflex, and iButton cards were supported.

FAQ

Question: Can T=1 protocol Smartcards be used with Sun Blade 1000?

Answer: No, because the Sun Blade 1000 uses the SCR403 Internal Reader,which is not compatible with the T=1 protocol.

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.



Bugs and Common User Errors

To troubleshoot Solaris Smartcard software operations and for a list ofcurrent bugs, see the appropriate bugtraq category and subcategories:

Category:

● smartcard

● Subcategories:

● cardapplets

● cardterminals

● commpackage

● doc

● gui

● i18n

● install

● ocf_api

● ocf_commands

● ocfserv

● other

● pam

● scf_api

● scf_api_test

Do not duplic

ate or d

istrib

ute with

out per

miss

ion from

Sun M

icrosy

stem

s, In

c. Use

Subjec

t to L

icense

.




For More Information

The following references provide additional information on the SolarisSmartcard feature:

● Smartcard changes: http://sac.eng.sun.com/PSARC/2002/505

● The Solaris Smartcard Project is covered by PSARC cases 1999/219,1999/222, and 2002/220

● Solaris Smartcard Framework Group: http://smartcard.eng

● MUSCLE PC/SC IFD Driver Development Kit:

http://smartcard.eng/docs/ifdhandler-2.12.pdf

● PC/SC Specifications Part 3 (describes IFD handler interface):

http://smartcard.eng/docs/p3v10_ps.pdf

● External sites containing other specifications and documents:

● Linux MUSCLE Project:

http://www.linuxnet.com

● PC/SC Workgroup:

http://www.pcscworkgroup.com/

● Opencard Standards Group:

http://www.opencard.org/

● Sun Microsystems, Inc., Solaris Smartcard Administration Guide [betaversion for Solaris 10 System Administration Collection], partnumber 816-5182

Documents

Desktop Features