The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: neozeed@gmail.com (Jason Stevens)
Subject: [TUHS] Xenix
Date: Tue, 10 Feb 2009 13:01:03 -0500	[thread overview]
Message-ID: <46b366130902101001q36a1ca77o9527578b60b4a4f9@mail.gmail.com> (raw)
In-Reply-To: <f982c3820902100431t704dff7an45a952cdc5c9e946@mail.gmail.com>

I doubt SCO/Microsoft will release anything.. but then you never know.
 Do you have Xenix for the PDP-11?  I've seen the lisa & Tandy 68000
floating around, but both used some custom MMU so that cut out
emulators... lol I haven't even bothered asking for source, as I
figured these v6/v7 things are basically lost in the mists of time...
but then there is v6/v7 for the Pdp-11/Interdata 32b & the recent port
of v7 to the i386 http://nordier.com/v7x86/index.html



On Tue, Feb 10, 2009 at 7:31 AM, Lorenzo Gatti <gattilorenz at gmail.com> wrote:
> Hello from Italy!
>
> I'm interested in Xenix copyright. Do someone of you know who exactly
> owns Xenix? According to Wikipedia, Microsoft gave everything to SCO,
> but did they gave also the copyright for the non-x86 versions?
>
> I'm asking this because I'm interested in "saving" Xenix from fading
> into the digital night. If everything belongs to SCO, then maybe an
> "binary only, non-commercial hobbyst license" could *eventually* be
> released, at least for older or non-x86 products
>
> Best regards,
>
> Lorenzo
>
> PS: First mailing list post ever. I'm definitely a newbie, here :)
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>



  reply	other threads:[~2009-02-10 18:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 12:31 Lorenzo Gatti
2009-02-10 18:01 ` Jason Stevens [this message]
     [not found]   ` <f982c3820902101008i7a6f8f3cm2a3eed74d0993d6@mail.gmail.com>
2009-02-10 18:29     ` Jason Stevens
2009-02-10 18:36   ` Al Kossow
2009-02-10 18:43     ` Jason Stevens

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=46b366130902101001q36a1ca77o9527578b60b4a4f9@mail.gmail.com \
    --to=neozeed@gmail.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).