1native(5) Standards, Environments, and Macros native(5)
2
3
4
6 native - native branded zone
7
9 The native brand uses the branded zones framework described in
10 brands(5) to run zones installed with the same software as is installed
11 in the global zone. The system software must always be in sync with the
12 global zone when using a native brand.
13
15 The following native brand-specific subcommand options are supported in
16 zoneadm(1M).
17
18 attach [-u] [-b patchid]...
19
20 For native zones, zoneadm checks package and patch levels on the
21 machine to which the zone is to be attached. If the pack‐
22 ages/patches that the zone depends on from the global zone are dif‐
23 ferent (have different revision numbers) from the dependent pack‐
24 ages/patches on the source machine, zoneadm reports these conflicts
25 and does not perform the attach. If the destination system has only
26 newer dependent packages/patches (higher revision numbers) than
27 those on the source system, you can use the -u option to update the
28 attached zone to match the -revision packages and patches that
29 exist on the new system. With -u, as in the default behavior,
30 zoneadm does not perform an attach if outdated packages/patches are
31 found on the target system.
32
33 For native zones, one or more -b options can be used to specify a
34 patch ID for a patch installed in the zone. These patches will be
35 backed out before the zone is attached or, if -u was also speci‐
36 fied, updated.
37
38
39 install [-a archive] | [-d path] [-p] [-s] [-u] [-v] [-b patchid]...
40
41 The native brand installer supports installing the zone from either
42 the software already installed on the system or from an image of an
43 installed system running the same release. This can be a full
44 flash archive (see flash_archive(4)) or a cpio(1) or pax(1) "xus‐
45 tar" archive. The cpio archive be compressed with gzip or bzip2.
46 The image can also be a level 0 ufsdump(1M), a path to the top-
47 level of a system's root tree, or a pre-existing zone path.
48
49 With no options the zone is installed using same software as is
50 running the global zone.
51
52 To install the zone from a system image either the -a or -d is
53 required. Either the -u or -p option is also required in this
54 case.
55
56 -a archive
57
58 The path to a flash_archive(4), cpio(1), or pax(1) "xustar" ar‐
59 chive, or a level0 ufsdump(1M), of an installed system. cpio
60 archives may be compressed using gzip or bzip2.
61
62
63 -b patchid
64
65 One or more -b options can be used to specify a patch ID for a
66 patch installed in the system image. These patches will be
67 backed out during the installation process.
68
69
70 -d path
71
72 The path to the root directory of an installed system. If path
73 is a hyphen (-), the zonepath is presumed to be already popu‐
74 lated with the system image.
75
76
77 -p
78
79 Preserve the system configuration after installing the zone.
80
81
82 -s
83
84 Install silently.
85
86
87 -u
88
89 Run sys-unconfig(1M) on the zone after installing it.
90
91
92 -v
93
94 Verbose output from the install process.
95
96
97
99 See attributes(5) for a description of the following attributes:
100
101
102
103
104 ┌─────────────────────────────┬─────────────────────────────┐
105 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
106 ├─────────────────────────────┼─────────────────────────────┤
107 │Availability │SUNWzoneu │
108 ├─────────────────────────────┼─────────────────────────────┤
109 │Interface Stability │Uncommitted │
110 └─────────────────────────────┴─────────────────────────────┘
111
113 cpio(1), pax(1), zlogin(1), zonename(1), sys-unconfig(1M), ufsdump(1M),
114 zoneadm(1M), zonecfg(1M), flash_archive(4), attributes(5), brands(5),
115 privileges(5), zones(5), lx_systrace(7D)
116
117
118
119SunOS 5.11 13 Feb 2009 native(5)