From: Robert Clausecker <fuz@fuz.su>
To: Dan Cross <crossd@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Open sourcing SunOS?
Date: Wed, 22 Feb 2023 17:23:46 +0100 [thread overview]
Message-ID: <Y/ZBkqBtXIgBRMT/@fuz.su> (raw)
In-Reply-To: <CAEoi9W7fiY4T=N2KzjpH0Rujp-tb-fX5dyS4rVgVPq4AGipuHQ@mail.gmail.com>
That's what OpenSolaris was. The bits that weren't open sourced
were the bits they weren't allowed to for licensing reasons, such
as the C compiler.
Yours,
Robert Clausecker
Am Wed, Feb 22, 2023 at 10:49:50AM -0500 schrieb Dan Cross:
> Has anyone tried talking to anyone at Oracle about possibly getting
> the SunOS code released under an open source license? There can't be
> any commercial value left in it.
>
> - Dan C.
--
() ascii ribbon campaign - for an 8-bit clean world
/\ - against html email - against proprietary attachments
next prev parent reply other threads:[~2023-02-22 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 15:49 [TUHS] " Dan Cross
2023-02-22 16:23 ` Robert Clausecker [this message]
2023-02-22 16:30 ` [TUHS] " Dan Cross
2023-02-22 19:52 ` Dave Horsfall
2023-02-22 20:04 ` Warner Losh
2023-02-22 20:12 ` Larry McVoy
2023-02-22 20:44 ` Brad Spencer
2023-02-22 20:46 ` Warner Losh
2023-02-22 20:54 ` Larry McVoy
2023-02-23 0:12 ` Rob Gingell
2023-02-23 2:14 ` Warner Losh
2023-02-23 7:22 ` Rob Gingell
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=Y/ZBkqBtXIgBRMT/@fuz.su \
--to=fuz@fuz.su \
--cc=crossd@gmail.com \
--cc=tuhs@tuhs.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).