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. Build 101-105
      3. Builds 96-100
      4. Builds 91-95
      5. Builds 86-90
      6. Builds 81-85
      7. Builds 76-80
      8. Builds 71-75
      9. Builds 66-70
      10. Builds 61-65
      11. Builds 56-60
      12. Builds 51-55
      13. Builds 46-50
      14. Builds 41-45
      15. Builds 36-40
      16. Builds 31-35
      17. Builds 26-30
      18. 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: beware of stale versions of bfu

Date: Wed, 27 Aug 2008 16:15:26 -0400
From: Sebastien Roy <Sebastien.Roy at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at sun dot com
Subject: heads-up: beware of stale versions of bfu

Users of bfu,

Today's ON bfu archives should be installed using a matching bfu script.
Of course, this is always true; one should always use a bfu script that
matches the bfu archives being installed, and today is no exception.

Users who have used old version of bfu
(including /ws/onnv-gate/public/bin dated August 2nd) with today's bfu
archives will run into the following problems at first boot:

Aug 27 03:09:09 svc.startd[7]: svc:/network/datalink-management:default: Method "/lib/svc/method/svc-dlmgmtd" failed with exit status 95.
Aug 27 03:09:09 svc.startd[7]: network/datalink-management:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
...
Requesting System Maintenance Mode

If you've run into this, simply run /usr/sbin/devfsadm manually and
reboot.  Your system will come up fine thereafter.

The ON gatekeeping staff are aware of the problem with stale scripts
in /ws/onnv-gate/public/bin and are working on resolving it.

-Seb