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: SPARCLE aka Sun Ultra 3 support

Date: Thu, 12 Apr 2007 20:46:35 -0700
From: "Garrett D'Amore" <Garrett.Damore at sun dot com>
To: on-all at sun dot com
Subject: Heads Up: SPARCLE aka Sun Ultra 3 support

Heads Up: SPARCLE aka Sun Ultra 3 support got committed today

(Thought I'd join on the HEADS UP bandwagon...)

Seriously, if you have one of these systems running Nevada, you cannot 
use BFU to pick up my changes on it, until you first do a full install 
with sources that include my putback.  (You could full install earlier 
versions of Nevada, but they were not BFU compatible.)

The problem is due to a bug (bad assumption) in BFU, where if uname -m 
== uname -i, it does not install any platform specific modules (apart 
from uname -m.)  Older Nevada releases lacked the bits for uname -i to 
be recognized properly, so uname -i always was just "sun4u" instead of 
"TAD,SPARCLE".

Anyway, just to be safe, I recommend you do a fresh install from today's 
bits.

Note that this problem is going to be true of other Tadpole platforms as 
well, but I've not put those support bits back yet.