284 safely be installed on the machine. Following is a break-down of the
285 checks by resource/property type:
286
287 zonepath
288 zonepath and its parent directory exist and are owned by root
289 with appropriate modes . The appropriate modes are that
290 zonepath is 700, its parent is not group or world-writable and
291 so forth. zonepath is not over an NFS mount. A sub-directory of
292 the zonepath named "root" does not exist.
293
294 If zonepath does not exist, the verify does not fail, but
295 merely warns that a subsequent install will attempt to create
296 it with proper permissions. A verify subsequent to that might
297 fail should anything go wrong.
298
299 zonepath cannot be a symbolic link.
300
301
302 fs
303 Any fs resources have their type value checked. An error is
304 reported if the value is one of proc, mntfs, autofs, cachefs,
305 or nfs or the filesystem does not have an associated mount
306 binary at /usr/lib/fs/<fstype>/mount.
307
308 It is an error for the directory to be a relative path.
309
310 It is an error for the path specified by raw to be a relative
311 path or if there is no fsck binary for a given filesystem type
312 at /usr/lib/fs/<fstype>/fsck. It is also an error if a
313 corresponding fsck binary exists but a raw path is not
314 specified.
315
316
317 net
318 All physical network interfaces exist. All network address
319 resources are one of:
320
321 o a valid IPv4 address, optionally followed by "/" and
322 a prefix length;
323
324 o a valid IPv6 address, which must be followed by "/"
325 and a prefix length;
326
417
418
419
420 Administrative actions on this service, such as enabling, disabling, or
421 requesting restart, can be performed using svcadm(1M). The service's
422 status can be queried using the svcs(1) command.
423
424
425 The act of installing a new non-global zone is a fresh installation of
426 the Solaris operating system. A new installation of Solaris must not
427 require interaction with the user (that is, it must be "hands off").
428 Because of this, packages installed in the global zone and all non-
429 global zones cannot contain request scripts (see pkgask(1M)). If a
430 package did have a request script, then the creation of a non-global
431 zone could not be done without user intervention. Any package that
432 contains a request script is added to the global zone only. See
433 pkgadd(1M).
434
435
436
437 December 26, 2014 ZONEADM(1M)
|
284 safely be installed on the machine. Following is a break-down of the
285 checks by resource/property type:
286
287 zonepath
288 zonepath and its parent directory exist and are owned by root
289 with appropriate modes . The appropriate modes are that
290 zonepath is 700, its parent is not group or world-writable and
291 so forth. zonepath is not over an NFS mount. A sub-directory of
292 the zonepath named "root" does not exist.
293
294 If zonepath does not exist, the verify does not fail, but
295 merely warns that a subsequent install will attempt to create
296 it with proper permissions. A verify subsequent to that might
297 fail should anything go wrong.
298
299 zonepath cannot be a symbolic link.
300
301
302 fs
303 Any fs resources have their type value checked. An error is
304 reported if the value is one of proc, mntfs, autofs, or nfs or
305 the filesystem does not have an associated mount binary at
306 /usr/lib/fs/<fstype>/mount.
307
308 It is an error for the directory to be a relative path.
309
310 It is an error for the path specified by raw to be a relative
311 path or if there is no fsck binary for a given filesystem type
312 at /usr/lib/fs/<fstype>/fsck. It is also an error if a
313 corresponding fsck binary exists but a raw path is not
314 specified.
315
316
317 net
318 All physical network interfaces exist. All network address
319 resources are one of:
320
321 o a valid IPv4 address, optionally followed by "/" and
322 a prefix length;
323
324 o a valid IPv6 address, which must be followed by "/"
325 and a prefix length;
326
417
418
419
420 Administrative actions on this service, such as enabling, disabling, or
421 requesting restart, can be performed using svcadm(1M). The service's
422 status can be queried using the svcs(1) command.
423
424
425 The act of installing a new non-global zone is a fresh installation of
426 the Solaris operating system. A new installation of Solaris must not
427 require interaction with the user (that is, it must be "hands off").
428 Because of this, packages installed in the global zone and all non-
429 global zones cannot contain request scripts (see pkgask(1M)). If a
430 package did have a request script, then the creation of a non-global
431 zone could not be done without user intervention. Any package that
432 contains a request script is added to the global zone only. See
433 pkgadd(1M).
434
435
436
437 September 8, 2015 ZONEADM(1M)
|