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

Clarification on "Heads up: Movement of /usr/ccs/bin utilities to /usr/bin"

Date: Mon, 25 Jun 2007 16:09:10 -0700
From: Lee Damico <lee.damico at sun dot com>
To: on-all at eng dot sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Clarification on "Heads up: Movement of /usr/ccs/bin utilities to /usr/bin"

Because a couple of folks have asked, I just want to clarify that symbolic
links remain for everything that was previously in /usr/ccs/bin.  The
exception is the text files used by gprof, lex, and yacc.  These are the
ones that were moved to /usr/share/lib/ccs.  There was no need to
maintain links as these are called directly by the utilities.

Lee

Lee Damico wrote:
> PSARC 2005/420 -- the movement of /usr/ccs/bin utilities to /usr/bin
> -- has been resurrected and integrated in Nevada build 68. This latest
> putback is specific to the ON portion of the project (see 6319687).
> The compiler owned portion integrated in build 42 (see 6249724).
>
> With this update, it is no longer necessary to include /usr/ccs/bin
> in your path. The exception is if you call either "admin" or "help"
> directly rather than via "sccs admin" or "sccs help".  These two
> commands, owned by the compiler team, were not migrated to
> /usr/bin with their putback."
>
> How else will this affect you? It shouldn't unless you have an 
> identically
> named utility included in your search path that was previously before
> /usr/ccs/bin but after /usr/bin. The ld command in /usr/ucb/bin is one
> possibility. Another is gnu yacc in /opt/csw/bin.
>
> In terms of ON builds, unless you do a full clobber build, you will also
> need to remove the following files from your proto area to avoid
> packaging warnings:
>
>        ./usr/ccs/bin/gprof.callg.blurb
>        ./usr/ccs/bin/gprof.flat.blurb
>        ./usr/ccs/bin/nceucform
>        ./usr/ccs/bin/ncform
>        ./usr/ccs/bin/nrform
>        ./usr/ccs/bin/yaccpar
>
> These now live in the newly created /usr/share/lib/ccs.  The bfu utility
> has been updated to account for these as well. If you use a version other
> than that provided in /ws/onnv-gate/public/bin or the latest onbld
> package, you may want to manually remove the above files from the
> old path, though there is no harm in leaving them in place.
>
> Lee
>