Milan Jurik writes:
> > Thus, there's no formal requirement here as such, and C-teams and ARCs
> > don't come into it at all.
> > 
> 
> C-team can ask for it, so I am trying to evaluate all possibilities.

Given the non-trivial fallout from /usr/bin/sleep, I would expect them
to think of possibilities I haven't even imagined.  They have long
memories and generally aren't too shy.

I think the *best* bet in this regard is to be up-front about the
issue.  If it were my project, I'd contact the C-team and say
something like this:

        Dear C-team Members,

        We're working on a project that will replace several common,
        heavily-used and ancient utility programs in /usr/bin with
        equivalents from ksh93.  The exact list of these utilities is
        available <insert reference here>.

        As we know that our previous attempt to replace /usr/bin/sleep
        in a simlar way ended with multiple areas of breakage,
        including BFU and failing PIT tests, we'd like to be a lot
        more careful this time around.  Obviously, we will be doing
        extensive tests with BFU (including upgrading from old,
        upgrading from new, and downgrade scenarios) and will be
        running a selection of DIY PIT tests.

        However, we would like to know in advance if any of the C-team
        members have particular tests that they would like to see run
        as part of this work.  If you know of any such specific tests
        you'd like to see as part of our integration request, please
        reply with a list.

        Thanks!

> > The minimum I would try would be installing OpenSolaris, copying over
> > the binaries, and then doing a pkg image-update and making sure that
> > flies.
> > 
> 
> During way home I went to the some possibility. Manual replacement of
> impacted binaries and then reboot (with changed PATH to UNIX standards),
> plus to try image-update at least. This could exercise ksh93 a bit more
> (with ksh93 to be be /usr/bin/ksh on it, I think).

That sounds good.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

Reply via email to