1 BRANDS(5)             Standards, Environments, and Macros            BRANDS(5)
   2 
   3 
   4 
   5 NAME
   6        brands - alternate operating environments for non-global zones
   7 
   8 DESCRIPTION
   9        The branded zone (BrandZ) framework extends the Solaris Zones
  10        infrastructure described in zones(5) to include the creation of brands,
  11        which provide non-global zones that contain non-native operating
  12        environments.
  13 
  14 
  15        The term "brand" can refer to a wide range of operating environments.
  16        All brand management is performed as extensions to the current zones
  17        structure.
  18 
  19 
  20        Every zone is configured with an associated brand. The brand type is
  21        used to determine which scripts are executed when a zone is installed
  22        and booted. In addition, a zone's brand is used to properly identify
  23        the correct application type at application launch time.  The default
  24        brand is determined by the installed distribution in the global zone.
  25 
  26 
  27        A branded zone will support exactly one brand of non-native binary,
  28        which means that a branded zone provides a single operating
  29        environment. Once a zone has been assigned a brand, that brand cannot
  30        be changed or removed.
  31 
  32 
  33        BrandZ extends the zones tools in the following ways:
  34 
  35            o      A brand is an attribute of a zone, set at zone create time.
  36 
  37            o      The zonecfg tool (see zonecfg(1M)) is used to set a zone's
  38                   brand type and configure the zone.
  39 
  40            o      The zoneadm tool (see zoneadm(1M)) is used to report a
  41                   zone's brand type and administer the zone.
  42 
  43    Device Support
  44        The devices supported by each zone are documented in the man pages and
  45        other documentation for that brand. The zones infrastructure detects
  46        any attempt to add an unsupported device and issues a warning to the
  47        administrator. If the administrator chooses to add an unsupported
  48        device despite that warning, that device might or might not work as
  49        expected. The configuration will be untested and unsupported.
  50 
  51 ATTRIBUTES
  52        See attributes(5) for a description of the following attributes:
  53 
  54 
  55 
  56 
  57        +--------------------+-----------------+
  58        |  ATTRIBUTE TYPE    | ATTRIBUTE VALUE |
  59        +--------------------+-----------------+
  60        |Interface Stability | Evolving        |
  61        +--------------------+-----------------+
  62 
  63 SEE ALSO
  64        mdb(1), zlogin(1), zonename(1), dtrace(1M), in.rlogind(1M), sshd(1M),
  65        zoneadm(1M), zonecfg(1M), kill(2), priocntl(2), getzoneid(3C),
  66        ucred_get(3C), getzoneid(3C), proc(4), attributes(5), lx(5),
  67        privileges(5), zones(5), crgetzoneid(9F)
  68 
  69 
  70 
  71                                  July 29, 2009                       BRANDS(5)