Hi Eric,

On Thu, 2006-08-10 at 16:42 -0500, Eric Boutilier wrote:
> I'm not sure I agree completely with the way you've scoped
> the problem.

Ok - unless I'm misunderstanding you, we're talking about different
problems I think.

You're talking about the problem of /usr/sfw/ containing material that
was classified as External, and now as a result of PSARC/2005/185,
moving it into /usr/bin where a namespace clash doesn't result,
and /usr/gnu otherwise.


I'm talking about doing something for users of different
OpenSolaris-based systems, with perhaps different software delivery
strategies & locations, to have an easy way to feel comfortable when
they encounter a distribution they're not (yet) familiar with.


An OpenSolaris Standards Base - based not on statically delivered
software in a location that all distributions must to agree on, but
instead based on a dynamic configuration file, which can be defined as
required. Each distro can do it's own thing wrt. software delivery but
it's then in each distros best interests to play well with others.

For example, I'm the author of TimiX, a fictional OpenSolaris-based
distribution. I have thousands of users, some of whom have to login to
Solaris boxes from time to time. This makes them feel uncomfortable, so
in order to help them out, I craft a TimiX.conf file for Solaris which
they can install there and feel more comfortable. They'd also need a
(possibly different) TimiX.conf file for each other distribution.


TimiX scripts that need run on those different distributions could avail
of the #! aliasing feature I was mentioning previously (thanks for the
hint Casper!) where during execution, we lookup the personality.conf
file for their OS to work out what they /really/ mean when they say
#!/bin/foo.

As I say, perhaps I'm over-complicating the problem, and if so, I'll
happily shut up :-)

        cheers,
                        tim

-- 
Tim Foster, Sun Microsystems Inc, Operating Platforms Group
Engineering Operations            http://blogs.sun.com/timf

_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to