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 96-100
      3. Builds 91-95
      4. Builds 86-90
      5. Builds 81-85
      6. Builds 76-80
      7. Builds 71-75
      8. Builds 66-70
      9. Builds 61-65
      10. Builds 56-60
      11. Builds 51-55
      12. Builds 46-50
      13. Builds 41-45
      14. Builds 36-40
      15. Builds 31-35
      16. Builds 26-30
      17. 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: new driver class scsi-self-identifying

Date: Tue, 03 Jun 2008 11:07:25 +0800
From: Javen Wu <Javen.Wu at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at eng dot sun dot com
Subject: Heads up: new driver class scsi-self-identifying

My putback of

PSARC 2008/337 scsi-self-identifying
6637648 new class scsi-self-identifying needed

adds a new driver class "scsi-self-identifying" for HBA drivers which are
self-identifying but do not belong to class "scsi".

For BFU users:

The change is a minor flag day for X86 BFU users. If you are going to 
BFU with
these changes before /ws/onnv-gate/public/bin/bfu is updated, E.g.,if `grep
chk_update_drv_class /ws/onnv-gate/public/bin/bfu` reports no output, 
then it is
still old version. To ensure you use correct /kernel/drv/sd.conf., you 
should
use the bfu from your own updated workspace.
`acr` is needed after BFU on both SPARC and X86,please make sure your 
following
files are updated:

/etc/driver_classes
/kernel/drv/sd.conf (X86/SPARC)
/kernel/drv/ssd.conf(SPARC)

This putback affects (Cap-Eye) Install users due to CR6682564: The putback
requires matching kernel code and sd.conf/ssd.conf.

-Javen