> > Specifically to an "OpenSolaris Reference Distribution", which does
> > not exist yet.
>
> The proposal should be retitled then, and should focus on that.

Not, really. It is all part of a whole.

> I think most people think of "OpenSolaris" as the ON consolidation,
> since that really is the primary things around which all other
> consolidations center.

Clearly not everyone agrees on this. You say a majority consider ON =
OpenSolaris. I think actually you would be hard pressed to prove this,
as the view of what OpenSolaris is probably depends on which community
the participant is active in.

> JDS, etc. are part of the OpenSolaris project, but would not think of
> them as "OpenSolaris."
>
> So, you need to define exactly what you mean when you say
> "OpenSolaris" -- there is a difference between the project and the
> code, etc.

I lost you on this one.

> That still doesn't define "weirdness." For example, are you saying you
> don't want to distribute what is in /usr/openwin or /usr/ucb? Or are
> you saying they shouldn't be part of the default path, and so on?

Can we get rid of the deprecated bits of OpenSolaris, that are just
there so Solaris can maintain backwards compatibility? (Those bits
could be viewed as distro specific) My question does not ask the
feasibility or desire to do this, but rather asks, *CAN* the community
decide to do this and implement it even though it is not in Sun's
interests Sun's interests?

> What does "no single log" directory specifically mean?

/var/adm/log/, /var/adm/, /var/log, /var/samba/log, etc..

> Rather than one specific proposal, this seems to be several under the
> guise of one.

Yes, but they are all interrelated, and have dependencies on each
other. (They probably will end up involving multiple projects when it
comes to implementation.

> > Earlier you said that Solaris is just another distro. Now it's the standard?
>
> I think what he's trying to point out is that right now, things are
> unlikely to be integrated unless they maintain compatibility.
>
> Also, you will have a hard time convincing anyone in the community to
> break backwards compatibility.

My question does not ask the feasibility or desire to do this, but
rather asks, *CAN* the community decide to do this and implement it
even though it is not in Sun's interests?

Keep in mind that this is basically a distro specific need. (Solaris)
Most of the other distros do not currently maintain backwards
compatibility.

> I don't know what you're trying to say here.

If we move something from /usr/sfw/bin to /usr/bin the OpenSolaris
favored plan is to put a symlink in /usr/sfw/bin pointing to /usr/bin,
to maintain backwards compatibility with Solaris 10. This is again a
distro specific issue.

> > >
> > > There isn't much non-core stuff there anyway. And I got the impression
> > > that the aim was to enable the easy supply of much more software
> >
> > Ok let me restate. Can we remove all code that was not developed by
> > Sun or the OpenSolaris community. (I am not advocating this, it is
> > just a point of discussion)
>
> No, because some of that code is needed for a "minimal" system. I
> think what you're trying to say is can we remove everything that is
> not the "core" necessary for the base OS. Or, put in a different way,
> can we choose to not include all consolidations that are not
> "absolutely necessary."

It doesn't have to be required for a minimal system. We could just
refactor and remove those dependancies. (Again a distro specific
requirement)

Reply via email to