Sun Microsystems 10 manual Optional settings, Starting zones automatically

Version 3.1-enSolaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009

5.1.10. Configuration and installation of a Solaris 8/Solaris 9 container

[ug] Solaris 8 containers and Solaris 9 containers can be created using 4 simple steps.

1.Planning how the data areas and network interfaces of the sources under Solaris 8 (or Solaris 9) can be represented in the Solaris 10 system.

2.Then the Solaris 8 system is archived. The P2V tool supplied can be used for this, but also any other archiving tool such as tar or cpio.

3.Next, the zone is configured as a Solaris 8 container (or a Solaris 9 container).

4.The archived system is installed with zoneadm install.

5.Data directories are transported to the new storage architecture.

6.The system is ready for testing.

5.1.11. Optional settings

[dd]Once the zone is configured, changes can be made to the configuration. Some examples are listed in the following sections based on the sparse-root zone zone1. Modifications to the zone configuration are activated by restarting the zone.

5.1.11.1. Starting zones automatically

[dd]Zones can be configured such that they are started up immediately after booting the system. In the original configuration, zones must be started manually by the administrator.

global# zonecfg -z zone1 zonecfg:zone1> set autoboot=true zonecfg:zone1> commit zonecfg:zone1> exit

global#

5.1.11.2. Changing the set of privileges of a zone

[dd]The set of privileges of a local zone can be extended by certain privileges. In this example, the privileges dtrace_proc and dtrace_user are additionally required within a zone to apply DTrace to local processes within the own zone (see 4.5.6 DTrace of processes within a zone).

global# ppriv -l zone wc -l global# 68

zone1# ppriv -l zone wc -l zone1# 34

global# zonecfg -z zone1

zonecfg:zone1> set limitpriv=default,dtrace_proc,dtrace_user zonecfg:zone1> commit

zonecfg:zone1> exit

zone1# ppriv -l zone wc -l zone1# 36

73