From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] Re: TUHS Digest, Vol 6, Issue 7
Date: Tue, 11 Nov 2003 18:09:25 -0800 [thread overview]
Message-ID: <20031112020925.GF3886@work.bitmover.com> (raw)
In-Reply-To: <20031112020007.248411FD1@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.
I removed all that stuff and booted up and ran on a complete free version of
SunOS long ago. Read about it here:
http://www.bitmover.com/lm/papers/srcos.html
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next parent reply other threads:[~2003-11-12 2:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031112020007.248411FD1@minnie.tuhs.org>
2003-11-12 2:09 ` Larry McVoy [this message]
2003-11-12 8:04 ` Wesley Parish
2003-11-12 3:08 ` Larry McVoy
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=20031112020925.GF3886@work.bitmover.com \
--to=lm@bitmover.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).