From: jpetts@operamail.com (James)
Subject: [TUHS] Solaris 10 source code
Date: Sat, 18 Jun 2005 20:08:02 +0000 GMT [thread overview]
Message-ID: <2054168344-1119125315-cardhu_blackberry.rim.net-22130-@engine93> (raw)
Groklaw (http://www.groklaw.net/) has some VERY good discussion of the 'openness' of this code...
-----Original Message-----
From: "Gregg C Levine" <hansolofalcon@worldnet.att.net>
Date: Sat, 18 Jun 2005 15:52:35
To:<tuhs at minnie.tuhs.org>
Subject: RE: [TUHS] Solaris 10 source code
Hello from Gregg C Levine
However, it happens that I spent some time talking with the folks at
the company in question, during the boot camp sessions that launched
Sol 10. It happens that the code is one hundred percent theirs. Now
there might be some lingering strangeness that follows from the BSD
evolved forms of Sol leading up to 10, that is all there will be.
Although I suspect a good hacker would be able to sort out the
differences and dummy up a working kit to support the assertions of
yours James Falknor, I myself do not have those talents.
However, Andrzej Popielewicz, I welcome your efforts.
----
Gregg C Levine hansolofalcon at worldnet.att.net
---
"The Force will be with you... Always." Obi-Wan Kenobi
> -----Original Message-----
> From: tuhs-bounces at minnie.tuhs.org
[mailto:tuhs-bounces at minnie.tuhs.org] On
> Behalf Of Andrzej Popielewicz
> Sent: Saturday, June 18, 2005 12:39 PM
> To: James Falknor
> Cc: tuhs at minnie.tuhs.org
> Subject: Re: [TUHS] Solaris 10 source code
>
> Uz.ytkownik James Falknor napisa?:
>
> > To all the Unix Officiando's,
> >
> > Have any of you checked out the recent release of Sun's Solaris 10
> > source code known as OpenSolaris?
> >
> > What are your thoughts on the subject?
> >
> > Is the source code still considered to be based on SVR4?
> >
> > Any likely chance of using Solaris source code to bring 32V or
Version
> > 7 of Unix into the modern world of x86 usage?
> >
> > Thank you,
> > James Falknor
> >
>
<<<SNIP!>>>
> I did not check sources of Solaris 10 yet, but as an owner of many
> Solaris 8/9 licenses I will certainly do it.
> As far as Unix Version 7 is concerned I see some chances . Let us
> consider such idea .
> For example Coherent is based on Unix version 7. It has also support
for
> DKI/DDI driver interface (but not complete implementation). Solaris
> drivers as far as I know use DKI/DDI. So there is some chance that
at
> least drivers could be in some way portable .
> Probably using NetBSD would be also an alternative.
>
> Andrzej
_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
http://minnie.tuhs.org/mailman/listinfo/tuhs
Sent wirelessly via BlackBerry from T-Mobile.
next reply other threads:[~2005-06-18 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 20:08 James [this message]
2005-06-18 22:35 ` Bryan Cantrill
2005-06-19 1:07 ` Greg 'groggy' Lehey
2005-06-19 13:17 ` Gunnar Ritter
2005-06-19 21:24 ` Greg 'groggy' Lehey
2005-06-19 2:10 ` Gregg C Levine
-- strict thread matches above, loose matches on Subject: below --
2005-06-18 5:36 James Falknor
2005-06-18 16:39 ` Andrzej Popielewicz
2005-06-18 19:52 ` Gregg C Levine
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=2054168344-1119125315-cardhu_blackberry.rim.net-22130-@engine93 \
--to=jpetts@operamail.com \
/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).