|
|
|
Unsupported. AI does not install from flash archives.
|
|
Unsupported. The backup_media keyword is used only with the
upgrade option of install_type. AI does not
support the upgrade install type; AI supports only initial install.
|
Example:
boot_device c1t0d0
|
Example:
<target>
<disk whole_disk="true">
<disk_name name="c1t0d0" name_type="ctd"/>
</disk>
<logical nodump="true" noswap="false"/>
</target>
|
boot_device device
eeprom
Example:
boot_device c0t0d0s0 update
|
The value for the eeprom keyword
(update for SPARC systems and preserve for
x86 systems) is not supported in AI. In AI, the EEPROM on SPARC systems is always
updated to the specified target device so that the installed system automatically
boots from that device. On x86 systems, the firmware is never updated.
|
|
Unsupported. AI creates a boot environment and installs the Oracle Solaris 11 OS
into that boot environment.
|
|
Unsupported. The client architecture to be installed is defined by the AI
install service, not in the AI manifest.
|
|
Unsupported. You can specify the type, vendor, and size of the target disk. You
cannot specify the amount of root space on the target disk. See the ai_manifest(4) man page.
|
|
Unsupported. By default, AI creates a swap volume in the root pool. You can
specify a swap slice. See the ai_manifest(4) man page.
|
|
The Oracle Solaris 11 OS uses group packages as defined in the pkg(5) man page. Group packages are specified just as any other
package is specified in the manifest. The default AI manifest includes the packages
needed for a standard Oracle Solaris 11 installation. You can customize this list of
packages.
|
cluster cluster-name delete
|
Unsupported. The delete switch is used only with the
upgrade option of install_type. AI does not
support the upgrade install type; AI supports only initial install.
|
|
Unsupported.
|
fdisk disk-name
type
size
Example:
fdisk c0t3d0 solaris all
|
Example:
<target>
<disk>
<disk_name name="c0t3d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191"/>
</disk>
<logical nodump="true" noswap="false"/>
</target>
For a full list of the disk and partition attributes supported by AI, see the
ai_manifest(4) man page.
Translation by js2ai:
For js2ai translation, the value of
disk-name must be a device. A device of
all is not supported. The fdisk
type must be solaris. A size of 0 or
delete is not supported. If partitioning is
default and the rootdisk has not been set,
js2ai sets the first fdisk
solaris partition encountered as the root disk.
|
|
UFS file systems are not supported. AI installs ZFS file systems.
Translation by js2ai:
-
If there is no other way to determine the device to be used for root, the
device from the filesys line with the /
mount point is used for the root pool.
-
The local and mirrored file systems are supported when the mount point
specified is / or swap.
-
If the mount point is not / or swap,
the line is logged and then ignored. JumpStart
fsoptions are not supported.
-
No validation of the size is performed. You might need to adjust the size
specified in the resulting AI manifest to achieve a successful installation with
this manifest.
|
Example:
filesys c1t0d0s0 10000 /
|
The following partial AI manifest is for x86 platforms.
<target>
<disk>
<disk_name name="c1t0d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true"
in_vdev="rpool_vdev" in_zpool="rpool" name="0">
<size val="10000mb"/>
</slice>
</partition>
</disk>
<logical nodump="true" noswap="false">
<zpool is_root="true" name="rpool">
<vdev name="rpool_vdev" redundancy="none"/>
</zpool>
</logical>
</target>
Translation by js2ai:
The js2ai command supports translations only of the root file
system (/) and swap.
|
Example:
filesys mirror:rpool c6t0d0s0 c6t1d0s0 60048 /
|
The following partial AI manifest is for x86 platforms. For SPARC platforms, no
partition element is specified.
<target>
<disk>
<disk_name name="c6t1d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true"
in_vdev="rpool_vdev" in_zpool="rpool" name="0">
<size val="60048mb"/>
</slice>
</partition>
</disk>
<disk>
<disk_name name="c6t0d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true"
in_vdev="rpool_vdev" in_zpool="rpool" name="0">
<size val="60048mb"/>
</slice>
</partition>
</disk>
<logical nodump="true" noswap="false">
<zpool is_root="true" name="rpool">
<vdev name="rpool_vdev" redundancy="mirror"/>
</zpool>
</logical>
</target>
|
filesys
server:path
|
Unsupported. AI does not support remote file systems.
|
|
Unsupported. AI does not install from flash archives.
|
|
|
|
AI supports only initial_install.
|
|
Unsupported. AI supports only initial_install.
|
|
Unsupported. AI does not install from flash archives.
|
|
|
|
Unsupported.
|
|
Unsupported. AI does not install from flash archives.
|
|
Unsupported. AI does not install from flash archives.
|
|
Unsupported.
|
Example:
package SUNWpampkcs11 add
|
Example:
<software type="IPS">
<software_data action="install">
<name>pkg:/SUNWpampkcs11</name>
</software_data>
</software>
|
package package add nfs
server:path
|
In an AI manifest, all software is retrieved from IPS (Image Packaging System)
package repositories. IPS repository locations can be a URL or file name. You can
specify multiple IPS repositories as software sources. See the ai_manifest(4) man page for information about how to specify
publishers.
Translation by js2ai:
The js2ai command ignores the
retrieval-type location
argument.
|
package package delete
|
Example:
<software type="IPS">
<software_data action="uninstall">
<name>pkg:/SUNWpampkcs11</name>
</software_data>
</software>
Because AI only supports initial installations, you should not need to use an AI
manifest to delete packages.
|
partitioning explicit
|
If no target installation device is specified, AI determines a default
installation device and a default partitioning. To specify custom partitioning, see
the ai_manifest(4) man page.
Translation by js2ai:
For js2ai, partitioning must be default or
explicit. For explicit, only
swap and / are supported
|
partitioning existing
|
Unsupported. For js2ai, partitioning must be
default or explicit.
|
|
Unsupported. AI supports only initial_install.
To update your system or specific packages, use the pkg
update command on the installed system.
|
pool newpool auto auto auto
device
|
Example:
<target>
<disk>
<disk_name name="c1t0d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true"
in_vdev="rpool_vdev" in_zpool="newpool" name="0"/>
</partition>
</disk>
<logical nodump="false" noswap="false">
<zpool is_root="true" name="newpool">
<vdev name="rpool_vdev" redundancy="none"/>
</zpool>
</logical>
</target>
Translation by js2ai:
If a pool is specified in a profile, js2ai creates the ZFS
root pool using the specified devices. The pool keyword
supersedes all other keywords when js2ai determines which devices
to use for the ZFS root pool.
The js2ai command does not perform any validation of the pool
size, swap size, or dump size. You might need to adjust these sizes in the resulting
AI manifest to achieve a successful installation with this manifest.
|
pool newpool auto auto auto any
|
For js2ai, if you specify any instead of a
physical device name, you must provide device information prior to the specification
that includes the any parameter. For example, you could provide a
root_device or usedisk specification before
this pool specification. See Example 6, Fixing mirrorpool.profile Errors for an example.
|
|
Example:
<target>
<disk>
<disk_name name="c1t0d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true"
in_vdev="rpool_vdev" in_zpool="rpool" name="0"/>
</partition>
</disk>
<logical nodump="true" noswap="false">
<zpool is_root="true" name="rpool">
<vdev name="rpool_vdev" redundancy="none"/>
</zpool>
</logical>
</target>
Translation by js2ai:
When root_device is specified, js2ai sets
the rootdisk to the specified device.
|
|
AI manifests do not differentiate system types.
Translation by js2ai:
Only the value standalone is supported.
|
|
Translation by js2ai:
The js2ai command might use the specified device or devices
to resolve subsequent any or rootdisk
specifications. Devices specified that are not used for this purpose are added to
the ZFS root pool by js2ai when that pool is not mirrored.
|