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: automountd/autofs comm via doors

Date: Fri, 09 Jun 2006 23:39:21 -0600
From: Evan Layton <Evan dot Layton 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: automountd/autofs comm via doors


    If you use 'bfu' or net-install to install/upgrade your system(s),
    you can safely ignore this message (incremental builds should also
    be fine). Otherwise, if you use anything else (ie. Cap-eye Install,
    direct 'cp', etc.), read on:

    The putback of...

    PSARC 2005/714 Automounter Scalability Enhancements
    6224343 autofs should use doors to talk to automountd

    ...changes the way the kernel autofs module communicates with
    automountd(1m). After this change if you need to upgrade your systems
    you'll need to have a matching autofs kernel module and automountd(1m)
    daemon. If these do not match the automounter will no longer work.

    If you somehow end up with a kernel and userland mis-match you will see
    autofs failing with an "automountd not running" error message on the
    console and "No such file or directory" will be returned to the user.

    If you have any questions/comments/concerns, please send e-mail to
    "nfs-eng at sun dot com". Bugs should be filed to kernel/autofs for the
    kernel module and network/automounter for automountd.

Thanks,
-evan