1root_archive(1M) System Administration Commands root_archive(1M)
2
3
4
6 root_archive - manage bootable miniroot archives
7
9 /boot/solaris/bin/root_archive pack archive root
10
11
12 /boot/solaris/bin/root_archive unpack archive root
13
14
15 /boot/solaris/bin/root_archive packmedia solaris_image root
16
17
18 /boot/solaris/bin/root_archive unpackmedia solaris_image root
19
20
22 The root_archive utility is used to manipulate boot archives and the
23 bootable miniroot(s) in a Solaris install image. The utility can pack
24 and unpack boot archives and image miniroots. Both ufs and hsfs
25 (iso9660) format archives can be unpacked, although only ufs format is
26 generated when packing.
27
28
29 For normal, boot-related system administration, bootadm(1M) is recom‐
30 mended. root_archive's primary purpose is to enable OEMs to add or
31 update a driver or other component on the Solaris install media.
32
33
34 A miniroot and a boot archive is closely associated with the release it
35 is intended to boot. To ensure that the tools and system services used
36 to construct the miniroot match, miniroot manipulation must be per‐
37 formed only on a system running the same release for which the miniroot
38 is intended to install.
39
41 The root_archive command has the following subcommands:
42
43 pack archive root Pack the contents of the root directory into the
44 boot archive archive.
45
46
47 unpack archive root
48
49 Unpack the contents of the boot archive named archive to the direc‐
50 tory named root.
51
52
53 packmedia solaris_image root
54
55 Create and pack the miniroot(s) in solaris_image from the contents
56 of the directory named root.
57
58
59 unpackmedia solaris_image root
60
61 Unpack the contents of the miniroot(s) in solaris_image to the
62 directory named root.
63
64
65
66 The contents of a miniroot are constructed to need the requirements of
67 the release. When unpacking a miniroot, all the contents of the mini‐
68 root(s) are unpacked. When packing a miniroot, the source directory
69 must contain all the necessary components with which to construct a
70 miniroot. In general, this can only be achieved by first unpacking an
71 existing miniroot.
72
74 Example 1 Unpacking the Miniroots in a Solaris x86 Install Image
75
76
77 The following command unpacks the miniroots in a Solaris image to the
78 root directory in /export/release/latest.
79
80
81 # root_archive unpackmedia \
82 /export/nv/solarisdvd.nvx_dvd/latest /export/release/latest/root
83
84
85
86
87 In the preceding, /export/nv/solarisdvd.nvx_dvd/latest represents a
88 path to a Solaris x86 install image and /export/release/latest/root is
89 a directory that will be purged or created, as necessary.
90
91
92 Example 2 Packing the Miniroots in a Solaris x86 Install Image
93
94
95 The following command creates and packs the miniroot(s) in a Solaris
96 image from the contents of the directory /export/release/latest/root.
97
98
99 # root_archive packmedia \
100 /export/nv/solarisdvd.nvx_dvd/latest /export/release/latest/root
101
102
103
105 The following exit values are returned:
106
107 0 The command completed successfully.
108
109
110 1 The command exited due to an error.
111
112
114 See attributes(5) for descriptions of the following attributes:
115
116
117
118
119 ┌─────────────────────────────┬─────────────────────────────┐
120 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
121 ├─────────────────────────────┼─────────────────────────────┤
122 │Availability │SUNWcsu │
123 ├─────────────────────────────┼─────────────────────────────┤
124 │Interface Stability │Committed │
125 └─────────────────────────────┴─────────────────────────────┘
126
128 cpio(1), bootadm(1M), mount(1M), attributes(5), lofi(7D)
129
130
131
132SunOS 5.11 9 Sep 2009 root_archive(1M)