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: Cap-Eye Install users

Date: Tue, 26 Sep 2006 14:32:34 -0700 (PDT)
From: eiji.ota 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: Cap-Eye Install users

You can safely ignore this message if you don't use (cap-eye) Install.

The putback for

  6311701 /etc/minor_perm is ignored if it contains comments
  6459253 i.nametomajor holds the obsolete shell function
  6460892 add_drv and update_drv can accept the invalid names
  6462571 should clean up duplicate code in update_minor_entry()

requires the user-land library (e.g. libdevinfo, libsvm) and commands (e.g.
add_drv/update_drv/rem_drv) in addition to the kernel change to be in sync.

The use of Install might not be safe. (if you don't care about those bug
fixes and not try them, it's likely OK though) The use of bfu should be fine.

Thanks,

Eiji