JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Oracle Solaris 9 Containers     Oracle Solaris Legacy Containers
search filter icon
search icon

Document Information

Preface

1.  Introduction to Solaris 9 Containers

About Branded Zones

Components Defined by the Brand

Processes Running in a Branded Zone

General Zones Characteristics

General Zones Concepts

About Oracle Solaris 9 Branded Zones

Oracle Solaris 10 Features Available to Zones

Limitations

General Non-Global Zone Limitations

Limitations Specific to solaris9 Branded Zones

Using ZFS

Adding Components

Ability to Directly Migrate Installed Systems Into Zones

2.  Obtaining and Installing the Software

3.  Assessing a Solaris 9 System and Creating an Archive

4.  Configuring a Solaris9 Zone

5.  Installing the solaris9 Zone

6.  Booting a Zone and Zone Migration

7.  About Zone Login and Post-Installation Configuration

A.  solaris9(5) Man Page

Index

About Oracle Solaris 9 Branded Zones

A Solaris 9 branded zone (solaris9) is a complete runtime environment for Solaris 9 applications on SPARC machines running the Oracle Solaris 10 8/07 Operating System or later. The brand supports the execution of 32-bit and 64-bit Solaris 9 applications.

solaris9 branded zones are based on the whole root zone model. Each zone's file system contains a complete copy of the software that comprises the operating system. However, solaris9 zones are different from native whole root zones in that central patching is not applied.

Oracle Solaris 10 Features Available to Zones

Many Oracle Solaris 10 capabilities are available to the solaris9 zones, including the following:

Limitations

Some functionality available in Solaris 9 is not available inside of zones.

General Non-Global Zone Limitations

The following features cannot be configured in a non-global zone on the Oracle Solaris 10 release:

In addition, a non-global zone cannot be an NFS server, and dynamic reconfiguration (DR) operations can only be done from the global zone.

Limitations Specific to solaris9 Branded Zones

The following limitations apply to solaris9 branded zones:

The following DTrace providers do not work:

Using ZFS

Although the zone cannot use a delegated ZFS dataset, the zone can reside on a ZFS file system. You can add a ZFS file system to share with the global zone through the zonecfg fs resource. See Step 7 in How to Configure a solaris9 Branded Zone.

Note that the setfacl and getfacl commands cannot be used with ZFS. When a cpio archive with ACLs set on the files is unpacked, the archive will receive warnings about not being able to set the ACLs, although the files will be unpacked successfully. These commands can be used with UFS.

Adding Components

You can add the following components to a solaris9 branded zone through the zonecfg command: