From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Jonathan Kalbfeld <jonathan.kalbfeld@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Where do we stand for Solaris 10/SPARC hosts?
Date: Wed, 26 Aug 2009 11:41:53 +0200 [thread overview]
Message-ID: <fb8d4f70908260241h5fb0a9abg9bb0379ab2f2916a@mail.gmail.com> (raw)
In-Reply-To: <db7b3ca90908251341m469ba184w315735b23f59e188@mail.gmail.com>
2009/8/25 Jonathan Kalbfeld <jonathan.kalbfeld@gmail.com>:
> If anyone needs access to a Solaris 10 sparc development environment I can
> provide it and give you root access.
Solaris 10/sparc is currently a bad choice, unless you've got a
really old non-public release of Solaris 10 which still had support
for 32 bit machines. Solaris 10 doesn't support 32 bit sparcs since
the very first public release. And qemu support of 64 bit CPUs is not
good enough to launch an OS yet.
Solaris 9/sparc and prior are also not bootable yet, but there are
chances it is going to change.
next prev parent reply other threads:[~2009-08-26 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 20:41 [Qemu-devel] Where do we stand for Solaris 10/SPARC hosts? Jonathan Kalbfeld
2009-08-26 9:41 ` Artyom Tarasenko [this message]
2009-08-26 13:35 ` Artyom Tarasenko
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=fb8d4f70908260241h5fb0a9abg9bb0379ab2f2916a@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=jonathan.kalbfeld@gmail.com \
--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).