Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend

Case Study: Minimizing Sun Validation Test Suite 5.1

This section provides a case study demonstrating how to get Sun Validation Test Suite 5.1 software functional on a minimized Solaris 9 OE domain.

The purpose of this section is to provide a detailed example of how to apply the minimization methodology to an application in a realistic scenario. (See Part I, "Minimization Methodology.")

Although you are probably minimizing another application, you can use this case study to extrapolate how to apply the process to your application or any other supported application covered in this two-part article.

The first part of qualification involves reviewing the documentation of Sun Validation Test Suite 5.1 for any special requirements.

Sun Validation Test Suite 5.1 is available at http://www.sun.com/oem/products/vts and comes as three compressed tar files that need to be decompressed and extracted. These are the packages SUNWvts, SUNWvtsx, and SUNWvtsmn. There is also a user guide available that has installation instructions for Sun Validation Test Suite 5.1. We follow the installation procedure, which says to do a pkgadd with the packages.


There is a note on the download Web site that XML packages SUNWlxml and SUNWlxmlx are required for Solaris 8 OE only. These packages are included as part of Solaris 9 OE, so no download is necessary for these packages.

The package SUNWvtsmn contains manual pages that are not installed in this example. For this case study, manual pages should not be installed on the minimized domain. The 64-bit version of the SUNWvtsx package is needed, because domains always run in 64-bit mode.

The user guide says to use pkgadd to add the packages.

The documentation makes no reference to setting the dynamic library location using crle(1) or LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 environmental variables. Also, according to the user guide, the metacluster installed must be at least SUNWCall. Because this is a subset of SUNWCXall, this condition is satisfied when installing to the full system.

Following the methodology, the next task is to install Sun Validation Test Suite 5.1 on a domain previously installed with SUNWCXall. Because we know the packages that are being added, there is no need to run script to capture a snapshot of the before and after pkginfo listings to figure out what these are.

Installation proceeds with the following, and Kerberos is not selected.

# pkgadd -d .
The following packages are available:
 1 SUNWvts   SunVTS
         (sparc) 5.1,REV=,OE=5.8,5.9
 2 SUNWvtsx   64-bit SunVTS
         (sparc) 5.1,REV=,OE=5.8,5.9

Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: 
SunVTS supports Kerberos V5 network authentication protocol, included in SEAM (Sun Enterprise 
Authentication Mechanism). This protocol is designed to provide strong authentication for client/server 
applications by using secret-key cryptography. In order to use this feature, a SEAM-based Security enabled 
network must be present.

Do you want to enable the Kerberos V5 based security? [y,n,?] n

The next task of the methodology involves running pkg.ksh against the application packages SUNWvts and SUNWvtsx to identify the Solaris package requirements.

# pkg.ksh SUNWvts SUNWvtsx
Unique packages needed:

Here, libraries are flagged that do not belong to a package. The "64" suggests these are 64-bit libraries. This assumption is confirmed by using the following command, showing a symbolic link to sparcv9.

# ls -l /usr/lib/64
lrwxrwxrwx  1 root   root      7 Dec 19 09:05 /usr/lib/64 -> sparcv9

Setting LD_LIBRARY_PATH_64 to /usr/lib/sparcv9 before running pkg.ksh causes the shell to resolve these libraries to that library path. Running pkg.ksh again resolves the library problem.

# LD_LIBRARY_PATH_64=/usr/lib/sparcv9
# export LD_LIBRARY_PATH_64
# pkg.ksh SUNWvts SUNWvtsx


The same result can be achieved by running pkg.ksh with the -s option to search for dynamic libraries in packages or directories, to set LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 appropriately.

The next task of the methodology is to build the minimized profile with the packages reported as needed by pkg.ksh. This profile will be used to install the minimized domain.

Next, the minimized Solaris configuration is installed on the domain via JumpStart installation using the minimized profile.

After the JumpStart install, the installation of the application occurs as it did on the fully installed system. During the pkgadd of SUNWvts and SUNWvtsx, the following warning is displayed.

NOTE: SUNWcpc(x) and SUNWcpcu(x) packages not installed. Performance counters for certain CPU and 
[ccc]y tests will not be displayed.

Only SUNWcpcu is already installed, so the other three packages need to be added to the minimized profile and the JumpStart installation of the domain performed again, or functionality will be missing from Sun Validation Test Suite 5.1. Performing the pkgadd step again will succeed.


The install process for an application might execute scripts that do logic checking on the packages already installed, like the previous example. These cannot be found using automated scripts, but can be found when testing the minimized configuration, hence the importance of testing the minimized configuration.

TABLE 34 lists the missing packages.

TABLE 34 Missing Packages

Package Type



CPU performance counter driver


CPU performance counter libraries and utilities (64-bit)


CPU performance counter driver (64-bit)

As seen on the fully installed domain, LD_LIBRARY_PATH_64 needs to be set before running the pkg.ksh, as on the fully installed system, against SUNWvts and SUNWvtsx.

On a Sun Fire V1280, 6800, 12K, or 15K domain, there is no smartcard hardware, so the SUNWocf package (open card framework) can be removed.

Sun Validation Test Suite 5.1 requires X-packages to be installed as seen from the output of pkg.ksh. This requirement means that the packages for supporting Sun Validation Test Suite 5.1 have to be added to the profile for applications requiring X-based executables.

TABLE 35 lists only the packages that were needed by Sun Validation Test Suite 5.1.

TABLE 35 Packages Needed for Sun Validation Test Suite 5.1

Package Type



CPU performance counter driver


CPU performance counter libraries and utilities


CPU performance counter libraries and utilities (64-bit)


CPU performance counter driver (64-bit)


Solaris cpp


CDE application basic runtime environment


Federated naming system






The XML library


The XML library (64-bit)


Modular debugger


Modular debugger (64-bit)




ToolTalk runtime


WCI RSM commands and libraries (64-bit)


X-Windows system common (not required) fonts


X-Windows system window drivers


X-Windows system platform required fonts


X-Windows system inter-client exchange (ICE) component


X-Windows system ICE library (64-bit)


X-Windows system optional clients


X-Windows system platform software


X-Windows system library software (64-bit)


X-Windows system and graphics runtime library links in /usr/lib


X-Windows system runtime compatibility package (64-bit)

Functionality testing of Sun Validation Test Suite 5.1 is carried out by executing sunvts and running the various functional tests.

The next section illustrates what happens when you attempt to install Sun Validation Test Suite 5.1 software on a domain installed with a non-X JumpStart profile; it demonstrates the reason why Sun Validation Test Suite 5.1 has a dependency on X-packages. This example points out an issue that customers might have to deal with when defining minimized systems for their applications.

Minimizing Sun Validation Test Suite 5.1 for Non-X Profile

Sun Validation Test Suite 5.1 has a console interface. In an attempt to get Sun Validation Test Suite 5.1 to be installed as part of the non-X minimal profile, by ignoring the X functionality, the packages SUNWvts and SUNWvtsx were added to a Solaris 9 OE minimized domain installed with the non-X minimal profile, which has no X-packages.

When doing a pkgadd of SUNWvts, the following is observed.

## Processing system information.
## Verifying package dependencies.
  The <SUNWxwdv> package "XWindows Window Drivers" is a
  prerequisite package and should be installed.
  The <SUNWxwplt> package "X Windows platform software"
  is a prerequisite package and should be installed.
  The <SUNWxwcft> package "X Windows common (not
  required) fonts" is a prerequisite package and should
  be installed.

Do you want to continue with the installation of <SUNWvts> [y,n,?] 

Ignoring these warnings by selecting y appears to continue the installation successfully. However, upon running sunvts, the following is displayed.

iutest: fatal: libX11.so.4: open failed: No such file

Examining this file shows that X-dynamic libraries are linked at compile time.

# ldd.ksh -s 'which iutest'
Couldn't find package for
    libX11.so.4 =>  (file not found)

The following table lists all the X-packages that are needed just to get Sun Validation Test Suite 5.1 installed from the non-X profile and run a simple test. It does not account for the additional testing that is needed to find the other packages required for corner-case functionality.

TABLE 36 Packages Required to Run Sun Validation Test Suite 5.1 From Non-X Profile

Package Type



X-Windows system common (not required) fonts


X-Windows system window drivers


X-Windows system platform software


X-Windows system library software (64-bit)


X-Windows system and graphics runtime library links in /usr/lib


X-Windows system runtime compatibility package (64-bit)

Due to the X-dynamic libraries requirement, Sun Validation Test Suite 5.1 has to be part of the X-applications profile.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020