qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michele Denber <mdenber@gmx.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU on Solaris
Date: Mon, 13 Aug 2018 15:13:28 -0400	[thread overview]
Message-ID: <5B71D858.2080907@gmx.com> (raw)
In-Reply-To: <20180813083408.GG22904@redhat.com>

On 08-13-2018 4:34 AM, Daniel P. Berrangé wrote:
> Copying Peter, as he would need access to a Solaris host to do GIT pre-merge
> build testing.
>
> Then there's the question of what ordinary developers would use for their own
> testing if they needed to work on some portability issue. We've got support
> in tree for running builds against VM images for the various *BSDs, and have
> mingw cross build toolchain for Windows. Is it possible to provide free-to-use
> VM disk images for Solaris build testing, or are software licensing requirements
> going to get in the way of developers using them ?
Correct me if I'm wrong but I assume you're referring to the use of the 
Solaris OS itself.  Solaris 10 and 11 are both available for free 
download from Oracle.  I read the license agreement 
(http://www.oracle.com/technetwork/licenses/solaris-cluster-express-license-167852.html) 
and while I'm not a lawyer and do not even play one on the Internet, the 
relevant part seems to be:

*"LICENSE RIGHTS *
Except for any included software package or file that is licensed to you 
by Oracle under different license terms, we grant you a perpetual 
(unless terminated as provided in this agreement), nonexclusive, 
nontransferable, limited License to use the Programs only for the 
purpose of developing, testing, prototyping and demonstrating your 
applications, and not for any other purpose. If You are an educational 
institution vested with the power to confer official high school, 
associate, bachelor, master and/or doctorate degrees, or local 
equivalent, (“Degree(s)”), You may also use the Programs as part of Your 
educational curriculum for students enrolled in Your Degree program(s) 
solely as required for the conferral of such Degree (collectively 
“Educational Use”)."

I /think /that means it's OK to use it.  ???
>
> There is OpenIndiana that forked off OpenSolaris, but I'm unclear how far
> OpenIndiana and commercial Solaris have diverged since then ?
One problem with OpenIndiana is that it's not available for SPARC. 
However, they refer to Dilos, OpenSXCE and Tribblix, though I know 
nothing of any of those.

             - Michele

  parent reply	other threads:[~2018-08-13 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-12 15:40 [Qemu-devel] QEMU on Solaris Michele Denber
2018-08-13  8:34 ` Daniel P. Berrangé
2018-08-13 10:08   ` Peter Tribble
2018-08-13 10:20     ` Peter Maydell
2018-08-13 19:23     ` Michele Denber
2018-08-13 19:13   ` Michele Denber [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-04  2:24 [Qemu-devel] qemu " Seth G
2010-03-04  6:22 ` Jonathan Kalbfeld
2010-03-04  6:39   ` Seth Goldberg
2010-03-06  7:11 ` Blue Swirl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5B71D858.2080907@gmx.com \
    --to=mdenber@gmx.com \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).