Dan Mick <[EMAIL PROTECTED]> wrote:
> Dan Mick wrote:
>
> > and for the record, /dev/xsvc is coming. I'm working on it personally now.
>
> BTW, examining the source for aperture, it looks very much like programs
> designed to use /dev/xsvc (like the afore-argued-about iasl) would work
> fine if /
Dan Mick wrote:
and for the record, /dev/xsvc is coming. I'm working on it personally now.
BTW, examining the source for aperture, it looks very much like programs
designed to use /dev/xsvc (like the afore-argued-about iasl) would work
fine if /dev/xsvc were a link to /dev/fbs/aperture.
I Ha
Dan Mick <[EMAIL PROTECTED]> wrote:
> and for the record, /dev/xsvc is coming. I'm working on it personally now.
Good news
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni)
[EMAIL PROTECTED](work) Blog: ht
Keith M Wesolowski <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 17, 2005 at 01:01:09AM +0200, Joerg Schilling wrote:
>
> > > No, Nevada is the engineering name for the development version of the
> > > whole Sun-Solaris.
> >
> > Then it is currently impossible to be binary compatible with it.
>
> That
Keith M Wesolowski wrote:
On Sun, Jul 17, 2005 at 01:01:09AM +0200, Joerg Schilling wrote:
No, Nevada is the engineering name for the development version of the
whole Sun-Solaris.
Then it is currently impossible to be binary compatible with it.
That should not be true, as concerns public
On Sun, Jul 17, 2005 at 01:01:09AM +0200, Joerg Schilling wrote:
> > No, Nevada is the engineering name for the development version of the
> > whole Sun-Solaris.
>
> Then it is currently impossible to be binary compatible with it.
That should not be true, as concerns public interfaces.
What you
Eric Boutilier <[EMAIL PROTECTED]> wrote:
> > > That is, if someone develops an application for "Sun's Nevada release",
> > > *should* we expect it to, at a binary compatable level, just run
> > > correctly on any other OpenSolaris-based distro?
> >
> > You cannot :-(
>
> Don't you mean: until Sun
On Mon, 18 Jul 2005, Joerg Schilling wrote:
> John Plocher <[EMAIL PROTECTED]> wrote:
>
> > Is it important (as an architectural goal...) that we could say
> > "runs on OpenSolaris[1]"
> > in the face of multiple "OpenSolaris based" distros?
> >
> > That is, if someone develops an application f
John Plocher <[EMAIL PROTECTED]> wrote:
> Is it important (as an architectural goal...) that we could say
> "runs on OpenSolaris[1]"
> in the face of multiple "OpenSolaris based" distros?
>
> That is, if someone develops an application for "Sun's Nevada release",
> *should* we expect it to,
Dennis Clarke <[EMAIL PROTECTED]> wrote:
> On 7/15/05, Eric Boutilier <[EMAIL PROTECTED]> wrote:
> > Because these forums are surely being read by many (probably thousands)
> > of people who are far less familiar with Solaris/OpenSolaris than the
> > people who post here, I'd like to strongly caut
Joerg Schilling wrote:
> Eric Boutilier <[EMAIL PROTECTED]> wrote:
> >
> > But I think we can minimize the problem by doing (at least start
> > planning) an base reference distro ASAP...
> We cannot cover the whole Sun Solaris as Sun Solaris includes things that
> may never become OpenSource.
Of
Eric Boutilier <[EMAIL PROTECTED]> wrote:
> On Sun, 17 Jul 2005, Joerg Schilling wrote:
> > Eric Boutilier <[EMAIL PROTECTED]> wrote:
> >
> > > But I think we can minimize the problem by doing (at least start
> > > planning) an base reference distro ASAP.
> >
> > If we like to talk about a referen
On 7/16/05, Eric Boutilier <[EMAIL PROTECTED]> wrote:
> On Sun, 17 Jul 2005, Joerg Schilling wrote:
> > Eric Boutilier <[EMAIL PROTECTED]> wrote:
> >
> > > But I think we can minimize the problem by doing (at least start
> > > planning) an base reference distro ASAP.
> >
> > If we like to talk abou
On Sun, 17 Jul 2005, Joerg Schilling wrote:
> Eric Boutilier <[EMAIL PROTECTED]> wrote:
>
> > But I think we can minimize the problem by doing (at least start
> > planning) an base reference distro ASAP.
>
> If we like to talk about a reference distro, we first need to talk about
> the extent it sh
Eric Boutilier <[EMAIL PROTECTED]> wrote:
> On Sun, 17 Jul 2005, Joerg Schilling wrote:
> >
> > ...
> > P.S. I assume that Nevada is the name for the new version of the Solaris O/N
> > consolidation and not a name for the whole Sun-Solaris.
>
> No, Nevada is the engineering name for the developmen
Joerg Schilling wrote:
P.S. I assume that Nevada is the name for the new version of the Solaris O/N
consolidation and not a name for the whole Sun-Solaris.
Nope, it's the code name for the next release of the entire Solaris WOS,
including all the consolidations.
--
-Alan Coopersmith-
On Sun, 17 Jul 2005, Joerg Schilling wrote:
>
> ...
> P.S. I assume that Nevada is the name for the new version of the Solaris O/N
> consolidation and not a name for the whole Sun-Solaris.
No, Nevada is the engineering name for the development version of the
whole Sun-Solaris.
Eric
__
Eric Boutilier <[EMAIL PROTECTED]> wrote:
> But I think we can minimize the problem by doing (at least start
> planning) an base reference distro ASAP.
If we like to talk about a reference distro, we first need to talk about
the extent it should cover.
Jörg
--
EMail:[EMAIL PROTECTED] (home) J
Scott Howard <[EMAIL PROTECTED]> wrote:
> I strongly suspect that binary compatibility is something which
> certain distributions are going to lose. In fact, so far we seem to
> be running zero from one as far as binary compability - the one and
> only non-Sun distribution (deliberately) breaks bi
On Sat, 16 Jul 2005, Shawn Walker wrote:
> On 7/16/05, Eric Boutilier <[EMAIL PROTECTED]> wrote:
> > On Sat, 16 Jul 2005, Scott Howard wrote:
> > > Unless every kernel/library change in every distro goes through an
> > > ARC-style approval then, in some cases deliverately and others accidently,
> >
On 7/16/05, Eric Boutilier <[EMAIL PROTECTED]> wrote:
> On Sat, 16 Jul 2005, Scott Howard wrote:
> > Unless every kernel/library change in every distro goes through an
> > ARC-style approval then, in some cases deliverately and others accidently,
> > we're eventually going to end up with an interfa
On Sat, 16 Jul 2005, Scott Howard wrote:
> On Fri, Jul 15, 2005 at 11:31:12AM -0700, John Plocher wrote:
> > Is it important (as an architectural goal...) that we could say
> > "runs on OpenSolaris[1]"
> > in the face of multiple "OpenSolaris based" distros?
>
> There is some mention of this at
On Fri, Jul 15, 2005 at 11:31:12AM -0700, John Plocher wrote:
> Is it important (as an architectural goal...) that we could say
> "runs on OpenSolaris[1]"
> in the face of multiple "OpenSolaris based" distros?
There is some mention of this at
http://www.opensolaris.org/os/about/faq/trademark
On Fri, 15 Jul 2005, John Plocher wrote:
> Is it important (as an architectural goal...) that we could say
> "runs on OpenSolaris[1]"
> in the face of multiple "OpenSolaris based" distros?
When Solaris and Solaris Express can fairly be be called OpenSolaris
based distros, then yes. But righ
On 7/15/05, John Plocher <[EMAIL PROTECTED]> wrote:
> Is it important (as an architectural goal...) that we could say
> "runs on OpenSolaris[1]"
> in the face of multiple "OpenSolaris based" distros?
>
> That is, if someone develops an application for "Sun's Nevada release",
> *should* we
Is it important (as an architectural goal...) that we could say
"runs on OpenSolaris[1]"
in the face of multiple "OpenSolaris based" distros?
That is, if someone develops an application for "Sun's Nevada release",
*should* we expect it to, at a binary compatable level, just run
correctly
On 7/15/05, Eric Boutilier <[EMAIL PROTECTED]> wrote:
> Because these forums are surely being read by many (probably thousands)
> of people who are far less familiar with Solaris/OpenSolaris than the
> people who post here, I'd like to strongly caution people about the use
> of the phrase "on OpenS
Because these forums are surely being read by many (probably thousands)
of people who are far less familiar with Solaris/OpenSolaris than the
people who post here, I'd like to strongly caution people about the use
of the phrase "on OpenSolaris" -- especially saying something resides
or runs "on Ope
28 matches
Mail list logo
