The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lyricalnanoha@dosius.ath.cx (Lyrical Nanoha)
Subject: [TUHS] TUHS Digest, Vol 31, Issue 9
Date: Fri, 19 May 2006 00:28:54 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0605190024550.19301@localhost.localdomain> (raw)
In-Reply-To: <20060519023529.GD17801@bitmover.com>

On Thu, 18 May 2006, Larry McVoy wrote:

> Tim wrote:
>> A good example would probably be SunOS 4 - we already know that Sun are
>> quite interested in open sourcing stuff given OpenSolaris, but SunOS 4
>> hasn't been, presumably because it is full of stuff-they-don't-own and has
>> no commercial value at all.
>
> I'm the guy who took SunOS 4.1.3 and removed all the non-free stuff from it
> (which was 90% STREAMS) and demo-ed it to McNealy in effort to set it free.
> A lot went into this: http://www.bitmover.com/lm/papers/srcos.html

The idea is not unlike what I am hoping to be able to do, that is, make a 
system as close to "real" Unix as possible, and fully open-source / 
copyleft, where Linux really isn't "it", BSD is closer to this goal, and 
indeed NetBSD + Heirloom Toolchest is where I would start.  I'd like to 
see a system, and hell, if I could I'd implement it myself.  One that felt 
so like commercial Unix that you couldn't tell the difference unless you 
ran uname.  And had needed functionality without being uber-bloated like 
GNU.

-uso.



  reply	other threads:[~2006-05-19  4:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3.1148004001.45222.tuhs@minnie.tuhs.org>
2006-05-19  2:35 ` Larry McVoy
2006-05-19  4:28   ` Lyrical Nanoha [this message]
2006-05-23  2:26   ` Greg 'groggy' Lehey
2006-05-23  2:38     ` Larry McVoy
2006-05-19 14:33 patv
2006-05-19 14:42 ` Larry McVoy
2006-05-19 14:44 ` John Cowan
2006-05-24 21:35 Berny 'Scouser' Goodheart

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=Pine.LNX.4.64.0605190024550.19301@localhost.localdomain \
    --to=lyricalnanoha@dosius.ath.cx \
    /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).