All pastes #2122268 Raw Edit

Miscellany

public text v1 · immutable
#2122268 ·published 2012-02-28 00:48 UTC
rendered paste body
     be-policy

         (string) Specify when a boot environment is created dur-
         ing  packaging  operations.  The  following  values  are
         allowed:

         default               Apply the default BE creation pol-
                               icy, currently 'create-backup'.

         always-new            Requires a reboot for all  package
                               operations by performing them in a
                               new BE set as active on  the  next
                               boot.  A  backup  BE will never be
                               created     unless      explicitly
                               requested.

                               This policy is the safest, but  is
                               more  strict than most sites need,
                               as  no  packages  can   be   added
                               without a reboot.



         create-backup         For   package   operations    that
                               require a reboot, a new BE will be
                               created and set as active  on  the

SunOS 5.11          Last change: 28 Jul 2011                   25

User Commands                                              pkg(1)

                               next  boot.  If packages are modi-
                               fied or content that could  affect
                               the  kernel  are installed and the
                               operation affects the live  BE,  a
                               backup BE will be created but will
                               not be set as active. A backup  BE
                               may also be explicitly requested.

                               This policy is  potentially  risky
                               only  if  newly installed software
                               causes system  instability,  which
                               is possible, but relatively rare.

         when-required         For   package   operations    that
                               require a reboot, a new BE will be
                               created and set as active  on  the
                               next  boot. A backup BE will never
                               be   created   unless   explicitly
                               requested.

                               This policy carries  the  greatest
                               risk  since  if a packaging change
                               to  the  live  BE  makes   further
                               changes  impossible,  there may be
                               no recent  BE  to  which  one  can
                               fallback.