OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads Up: BFU and ACR need to be in sync following 6535942

Date: Mon, 2 Apr 2007 16:05:33 -0700
From: Dan Price <dp at eng dot sun dot com>
To: onnv-gate at onnv dot sfbay dot sun dot com, on-all at sun dot com
Subject: Heads Up: BFU and ACR need to be in sync following 6535942


If you use BFU and ACR, but only the /ws/onnv-gate/public/bin copies of 
these tools (and no others), you can ignore this message.

My putback to fix

        6535942 bfu and acr don't tolerate non-native zones other than 'lx'

means that project gatekeepers and those running private copies of BFU
need to ensure that they are using BFU and ACR which are in sync with
each other.  If not, zones may not be ACR'd.  To be clear:

        - Old ACR does not work with new BFU
        - New ACR does not work with old BFU

The issue here is that BFU copies down ACR to your local machine
before it runs (potentially from onnv-gate), and so you could get
the wrong version.

If things go wrong, you can always run the correct version of ACR upon
rebooting the system, and it should then ACR your zones.

        -dp

-- 
Daniel Price - Solaris Kernel Engineering - dp at eng dot sun dot com - blogs.sun.com/dp