Language: English. Try using a different matching pattern, or refreshing publisher information Linked progress: pkg: update failed linked image exception s : pkg sync-linked: No solution was found to satisfy constraints Core operating system packages must be the same version in non-global zones as in the global zone. Failed Checkpoints: Checkpoint execution error: The following pattern s did not match any allowable packages.
Try using a different matching pattern, or refreshing publisher information: Installation: Failed. When you start a zone automatically at the time of system booting "true" is specified in "autoboot" at the time of zone configuration , make settings to mount a file system automatically at the time of system booting.
It is possible to use a volume created in global zone as raw device from non-global zones by the following procedure. Specify the path of the device special file of the volume created in step 1 to "match," run "add device.
Example: when the zone name is zone1, the class name is class, and the volume name is volume Building procedure for Solaris 1 0. Copy the device special file of the volume created in the global zone to the non-global zone by the following procedure:. The volume's special files copied in the step 2 will be deleted if the non-global zone is detached and then attached.
This is due to the OS specification. When this occurred, re-perform the step 2 and 3 after attaching the non-global zone. By creating and mounting a file system using the special file added to the non-global zone by " Using a volume as raw device from non-global zones ," you can use the volume created in a global zone from non-global zones. Perform the building procedure of " Using a volume as raw device from non-global zones. When the volume to be used as the raw device form the non-global zone is mounted as a file system in the global zone, unmount it.
Example: when the zone name is zone1, the types of the file system to be used in the non-global zone are hsfs, nfs, ufs, and zfs. For restarting the zone, see the manual of the zoneadm 1M command. Example: when the class name is class, the volume name is volume, and the file system type is ufs. When using the same file system in multiple global zones, you need to perform the method of Using a volume as a file system from a non-global zone setting the share of a file system by creating and changing the zone configuration.
When stopping a node where a file system is mounted in a non-global zone by using a volume created in shared class, stop a node after unmounting a file system or stopping a non-global zone. It is possible to use the file system created on a volume in a global zone as a file system from a non-global zone by setting mount of a file system by creating and changing the zone configuration.
Access to a file system using the directory path mount point in a non-global zone specified by creating and changing zone configuration. When using the file system in multiple non-global zones, you need to perform the method of " Using a volume as a file system from a non-global zone setting the share of a file system by creating and changing the zone configuration.
When stopping node that a file system is mounted in non-global zone by using a volume created in shared class, stop a node after unmounting a file system or stopping non-global zone. See Privileges in a Non-Global Zone. For more information, see Introduction to Oracle Solaris When file systems are mounted from within a zone, the nodevices option applies.
This rule does not apply to mounts specified through a zonecfg configuration. Options for mounting file systems in non-global zones are described in the following table. To mount file system types other than HSFS and NFS from inside the non-global zone, also add the file system type to the configuration by using the zonecfg fs-allowed property.
Note - The quota command, which is documented in the quota 8 man page, cannot be used to retrieve quota information for UFS file systems that are added with the fs resource of the zonecfg command. To use UFS file systems in a non-global zone through the zonecfg command, the package must be installed into the zone after installation or through the AI manifest script.
The ability to unmount a file system will depend on who performed the initial mount. If a file system is specified as part of the zone's configuration using the zonecfg command, then the global zone owns this mount and the non-global zone administrator cannot unmount the file system.
Zones can be NFS clients. NFS version 2, version 3, and version 4 protocols are supported. The default version is NFS version 4. You can enable other NFS versions on a client by using one of the following methods:. Manually create a version mount — This method overrides the sharectl setting.
A zone's file system namespace is a subset of the namespace accessible from the global zone. Unprivileged processes in the global zone are prevented from traversing a non-global zone's file system hierarchy through the following means:. Specifying that the zone root's parent directory is owned, readable, writable, and executable by root only. Note that attempting to access AutoFS nodes mounted for another zone will fail. The global administrator must not have auto maps that descend into other zones.
Mounting certain file systems from within a zone presents a security risk. Non-default file systems exhibit special behavior when mounted in a zone.
The list of modified file systems follows. AutoFS is a client-side service that automatically mounts the appropriate file system. AutoFS mounts established within a zone are local to that zone and cannot be accessed from other zones, including the global zone.
The mounts are removed when the zone is halted or rebooted. Each zone runs its own copy of automountd. The auto maps and timeouts are controlled by the zone administrator. An AutoFS mount that is created in the kernel when another mount is triggered cannot be removed by using the regular umount interface.
0コメント