ipkg man page on OpenIndiana

Man page or keyword search:  
man Server   20441 pages
apropos Keyword Search (all sections)
Output format
OpenIndiana logo
[printable version]

ipkg(5)		      Standards, Environments, and Macros	       ipkg(5)

NAME
       ipkg - ipkg branded zone

DESCRIPTION
       The  ipkg brand uses the branded zones framework described in brands(5)
       to run zones installed with the same software as is  installed  in  the
       global zone. The system software must always be in sync with the global
       zone when using a ipkg brand. The system software packages  within  the
       zone are managed using the image packaging system. See pkg(5).

   Configuration and Administration
       The  ipkg  brand	 supports the whole root non-global zone model. All of
       the required system software and any additional packages are  installed
       into  the private file systems of the zone. The zone must reside on its
       own zfs(1M) dataset and only ZFS is supported. The ZFS dataset is  cre‐
       ated  automatically  when  the  zone is installed or attached. If a ZFS
       dataset cannot be created, the zone is not installed or attached.

SUB-COMMANDS
       The following ipkg brand-specific subcommand options are	 supported  by
       zoneadm(1M).

       attach [-a archive | -d path] [-u]

	   Attach the specified ipkg branded zone image into the zone. If nei‐
	   ther -a or -d is specified,	the  zone's  zonepath  is  assumed  to
	   already be properly installed with the zone's files. zoneadm checks
	   package levels on the machine to which the zone is to be  attached.
	   If  the  packages that the zone depends on from the global zone are
	   different (have different  revision	numbers)  from	the  dependent
	   packages on the source machine, zoneadm reports these conflicts and
	   does not perform the attach. If the	destination  system  has  only
	   newer  dependent  packages  (higher revision numbers) than those on
	   the source system, you can use the -uoption to update the  attached
	   zone	 to  match  the revision of the packages that exist on the new
	   system. With -u, as in the default behavior, zoneadm does not  per‐
	   form an attach if outdated packages are found on the target system.

	   -a archive

	       The  path to a cpio(1) or pax(1) xustar archive of an installed
	       ipkg branded zone's zonepath. cpio archives can	be  compressed
	       using gzip or bzip2.

	   -d path

	       The  path  to  the  zonepath directory of a ipkg branded zone's
	       zonepath.

	   -u

	       Update the packages for the zone's system software to match the
	       global zone.

       install [-c certificate_file] [-k key_file] [-P publisher=uri] [-e
       extrapkg [...]]
       install [-a archive] | [-d path] [-p] [-s] [-u] [-v]

	   The ipkg brand installer supports installing the zone  from	either
	   the	software  repository  or  from an image of an installed system
	   running the same release. This can be a cpio(1)  or	pax(1)	xustar
	   archive. The cpio archive can be compressed with gzip or bzip2. The
	   image can also be a path to the top-level of a system's root	 tree,
	   or a pre-existing zone path.

	   If  neither the -a or -d option is used, the zone is installed from
	   the repository.

	   To install the zone from a system image either  the	-a  or	-d  is
	   required. Either the -u or -p option is also required in this case.

	   -a archive		  The  path  to	 a cpio(1) or pax(1) xustarar‐
				  chive of an installed system. cpio  archives
				  may be compressed using gzip or bzip2.

	   -c certificate_file	  The  path to the certificate file needed for
				  accessing the repository.

	   -d path		  The  path  to	 the  root  directory  of   an
				  installed  system.  If path is a hyphen (-),
				  the zonepath is presumed to be already popu‐
				  lated with the system image

	   -e package_name	  The  name  of	 a package to install into the
				  zone. The -e option is used  to  specify  an
				  additional  package  to install, in addition
				  to the base set of software which is	always
				  installed into the zone. Multiple -e options
				  can be used

	   -k key_file		  The path to the key file needed for  access‐
				  ing the repository.

	   -P publisher=uri	  The  name of a software repository publisher
				  and its associated URI to use to install the
				  zone	instead	 of  the default global zone's
				  repository.

	   -p			  Preserve  the	 system	 configuration	 after
				  installing the zone.

	   -s			  Install silently

	   -u			  Run	sys-unconfig(1M)  on  the  zone	 after
				  installing it.

	   -v			  Verbose output from the install process.

ATTRIBUTES
       See attributes(5) for a description of the following attributes:

       ┌─────────────────────────────┬─────────────────────────────┐
       │      ATTRIBUTE TYPE	     │	    ATTRIBUTE VALUE	   │
       ├─────────────────────────────┼─────────────────────────────┤
       │Availability		     │system/zones		   │
       ├─────────────────────────────┼─────────────────────────────┤
       │Interface Stability	     │Uncommitted		   │
       └─────────────────────────────┴─────────────────────────────┘

SEE ALSO
       cpio(1), pax(1),	 zfs(1M),  zlogin(1),  zonename(1),  sys-unconfig(1M),
       zoneadm(1M),  zonecfg(1M),,  attributes(5),  brands(5),	privileges(5),
       zones(5)

       pkg(5), available in the IPS consolidation

SunOS 5.11			  30 Nov 2009			       ipkg(5)
[top]

List of man pages available for OpenIndiana

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net