The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: patv@monmouth.com (Pat Villani)
Subject: 32V update (was Re: [TUHS] While on the subject of 32V ...)
Date: Wed, 05 Nov 2003 07:53:25 -0500	[thread overview]
Message-ID: <3FA8F2C5.6040902@monmouth.com> (raw)
In-Reply-To: <20001104211501.GA820@adelaide.lemis.com>

I have my opinions about SCO, and what they're doing.  I don't think 
we'll see any problems because this activity is down in the noise.  They 
need to challenge Linux at the enterprise level.  It will be quite some 
time, if ever, that 32V reaches that level of complexity in order to be 
a threat.

For now, it's an exercise in nostalgia.  In 1980, a friend and I 
investigated licensing unix for sale on 68K and 8086 based computers. 
We couldn't raise the $68,000 source+binary license fee, so the project 
died.  That was more than double my salary as an engineer at that time.

Now, 23 years later, I'm going to do a port to see how close my original 
estimates are to reality.  After the initial port, who knows?

Pat

Greg Lehey wrote:

> On Thursday, 30 October 2003 at  7:56:41 -0500, Pat Villani wrote:
> 
>>I got corporate approval, well, as best as I could from corporate legal,
>>to proceed.  The only caveats are: beware of the SCO shenanigans as 32V
>>may encounter a similar wrath,
> 
> 
> I'm only just catching up with this thread, but I'm surprised that
> nobody else pointed out that SCO is the same company that released
> "ancient UNIX" under a free license in January 2002.  Given SCO's
> behaviour, that doesn't guarantee that they won't cause problems, but
> it should severely limit the scope.
> 
> Greg
> --
> Finger grog at lemis.com for PGP public key
> See complete headers for address and phone numbers
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
> 
> 




  reply	other threads:[~2003-11-05 12:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 13:35 [TUHS] While on the subject of 32V Pat Villani
2003-10-21  0:50 ` Wesley Parish
2003-10-21 14:00   ` Pat Villani
2003-10-22  8:10     ` Wesley Parish
2003-10-24 13:41       ` Pat Villani
2003-10-29  9:01         ` Wesley Parish
2003-10-30 12:56         ` 32V update (was Re: [TUHS] While on the subject of 32V ...) Pat Villani
2003-10-31 10:13           ` Wesley Parish
2003-10-31 14:26             ` Pat Villani
2003-11-05  2:22           ` Greg Lehey
2003-11-05 12:53             ` Pat Villani [this message]
     [not found] ` <200311022346.34747.wes.parish@paradise.net.nz>
     [not found]   ` <oprx0h6gtdrveh1e@smtp.borf.com>
2003-11-03 10:48     ` Wesley Parish
2003-11-03 15:34       ` Pat Villani
2003-11-04  9:56         ` Wesley Parish
2003-11-04 13:51           ` Pat Villani
2003-10-31 22:37 Robertdkeys
2003-10-31 23:53 ` Gregg C Levine
2003-11-04 18:18 macbiesz
2003-11-05 10:23 ` Wesley Parish

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=3FA8F2C5.6040902@monmouth.com \
    --to=patv@monmouth.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).