From: arnold@skeeve.com (Aharon Robbins)
Subject: Heritage X (was Re: [TUHS] Lauch Gui using remote xterm!!)
Date: Tue, 11 Nov 2003 18:58:36 +0200 [thread overview]
Message-ID: <200311111658.hABGwa5t025453@skeeve.com> (raw)
> Date: Tue, 11 Nov 2003 21:13:16 +1300
> From: Wesley Parish <wes.parish at paradise.net.nz>
> Subject: Re: Heritage X (was Re: [TUHS] Lauch Gui using remote xterm!!)
> To: tuhs at minnie.tuhs.org
>
> I've personally thought that Sun should release the source trees of its old
> BSD-based SunOS with the idea of getting back onside with all the Linux and
> Unix people it pissed off by its "buying" a "Unix" license from SCO, the
> Societe Commercial du On-Dit, the Commercial Society of Rumourmongers.
Don't hold your breath. Even SunOS 4.1.x had large chunks of System V Release 3
code in it: all the STREAMS stuff and RFS worked in that environment (not that
anyone ever used it). Also all of /usr/5bin, /usr/5lib etc.
Arnold
next reply other threads:[~2003-11-11 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 16:58 Aharon Robbins [this message]
2003-11-11 18:18 ` Free SunOS (was Re: Heritage X (was Re: [TUHS] Lauch Gui using remote xterm!!)) Kenneth Stailey
2003-11-11 18:31 ` [TUHS] Re: Free SunOS M. Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2003-11-11 21:08 Heritage X (was Re: [TUHS] Lauch Gui using remote xterm!!) macbiesz
2003-11-17 10:05 ` Tim Bradshaw
2003-11-09 0:27 Michael Sokolov
2003-11-08 12:49 [TUHS] Lauch Gui using remote xterm!! Warren Toomey
2003-11-08 21:30 ` Heritage X (was Re: [TUHS] Lauch Gui using remote xterm!!) Kenneth Stailey
2003-11-09 19:22 ` Jochen Kunz
2003-11-11 8:13 ` Wesley Parish
2003-11-11 12:15 ` Tim Bradshaw
2003-11-11 15:09 ` Derrik Walker v2.0
2003-11-11 18:15 ` Kenneth Stailey
2003-11-14 4:43 ` Kenneth Stailey
2003-11-14 16:12 ` Brad Spencer
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=200311111658.hABGwa5t025453@skeeve.com \
--to=arnold@skeeve.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).