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: 2 small changes to nightly(1)

Date: Tue, 10 Jul 2007 15:39:29 -0700
From: Mike Kupfer <mike.kupfer at sun dot com>
To: on-all at eng dot sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: heads up: 2 small changes to nightly(1)

My fix for 

    6570962 nightly -O should include closed binaries in BFU archives

changed the name of the BFU tarballs that are generated by the -O
flag.  Because the tarballs now have closed binaries baked into them
(i.e., they are no longer just open source), the new names are

    on-bfu-nightly-osol.$MACH.tar.bz2
    on-bfu-nightly-osol-nd.$MACH.tar.bz2

Also, mail from nightly(1) has changed slightly: the "cpio archives
build errors" section will only appear in the mail message if there
were actually errors.

Sorry for any disruption.

mike