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 106-110
      3. Builds 101-105
      4. Builds 96-100
      5. Builds 91-95
      6. Builds 86-90
      7. Builds 81-85
      8. Builds 76-80
      9. Builds 71-75
      10. Builds 66-70
      11. Builds 61-65
      12. Builds 56-60
      13. Builds 51-55
      14. Builds 46-50
      15. Builds 41-45
      16. Builds 36-40
      17. Builds 31-35
      18. Builds 26-30
      19. 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: pay no attention to the SCCS Noise behind the curtain

Date: Mon, 14 Jul 2008 15:18:46 -0600
From: "Mark J. Nelson" <Mark.J.Nelson at sun dot com>
To: on-all at sun dot com, onnv-gate at onnv dot eng dot sun dot com, tools-discuss at opensolaris dot org,
Subject: heads up: pay no attention to the SCCS Noise behind the curtain


If you're still using Teamware, then your nightly mail_msg will probably 
now contain the following:

> ==== SCCS Noise (non-DEBUG) ====
>
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.11/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.10.1/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.10.1/sparc/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.10/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.10/sparc/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.11/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.10/sparc/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.10/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.10.1/sparc/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.10.1/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.11/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.10.1/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.10.1/sparc/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.10/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.8.4/5.10/sparc/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.11/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.10/sparc/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.10/x86/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.10.1/sparc/SCCS
> sccs get Sun/Solaris/PerlGcc/config/5.6.1/5.10.1/x86/SCCS

This is legitimate SCCS Noise.  It has been in your nightly.log for a 
long, long time.  It has not appeared previously in your mail_msg because 
a regular expression in nightly.sh incorrectly contained an extra space.

If you see OTHER instances of SCCS Noise, they're likely wrong.

But the ones above may be safely ignored, and will magically go away in 
build snv_97.

--Mark