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

Flag Day - PSARC 2005/583 VHCI Driven Device Enumeration

Date: Thu, 10 Nov 2005 07:17:26 -0800
From: Ramaswamy Tummala <ramaswamy dot tummala at sun dot com>
To: on-all at eng dot sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Flag Day - PSARC 2005/583 VHCI Driven Device Enumeration

If you use bfu to update your machine and do not use iscsi storage, you may
ignore this message.

The putback of 4938301 represents a flag day for Cap-Eye Install users, and
people using iscsi storage.  Other BFU users are not affected.

If you use Cap-Eye Install, you'll be a missing a few other pieces,
in particular devfsadm, and filelist.ramdisk file. If you just install a
genunix module, you'll also miss scsi_vhci and devinfo modules.
To not suffer ill effects, install all these objects or just use
bfu to be safe.

This putback is also a flag day for users of iscsi storage who
have updated their system with bfu or Cap-Eye Install. Regular install
users are not affected. After the system is rebooted following bfu or
Cap-Eye Install, you need to run devfsadm once. Otherwise you may not
be able to access iscsi storage. Note that running of devfsadm is necessary
only after the first reboot. There is no need to run on every reboot.

(bfu also causes the system to run devfsadm by doing reconfig boot.
But this devfsadm runs too early. For iscsi storage access, devfsadm
must be run after the network stack is plumbed.)

Ramaswamy.