From: neozeed@gmail.com (Jason Stevens)
Subject: [TUHS] UNIX turns forty
Date: Wed, 20 May 2009 01:16:18 -0400 [thread overview]
Message-ID: <46b366130905192216h6ec2a0a6s64357feab5a58b95@mail.gmail.com> (raw)
In-Reply-To: <20090519215610.A10612@eskimo.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
What more (well to me) is that interactive Unix was the first
commercial unix.... I suspect all versions of it's PDP-11 & VAX stuff
is lost forever?
Does anyone know why Kodak would have bought them? I suspect they had
some imaging stuff going....?
On Wed, May 20, 2009 at 12:56 AM, Derek Peschel <dpeschel at eskimo.com> wrote:
> On Fri, May 15, 2009 at 06:48:46AM -1000, Tim Newsham wrote:
>> So when do the official celebrations begin? What's a good estimate
>> of the month and date in 1969 when it all began?
>
> Interesting question! And related questions -- When did the current
> start of the epoch get chosen? Were there any false starts or early
> changes? (I seem to recall reading about one change, moving forward
> by a year.) And were there ever any dates in the system that couldn't
> be correctly recorded, because the epoch started too late?
>
> The other question is what the official celebrations should celebrate.
> Personally, I'd chip in on a big cake with one candle for each year
> that a reasonable amount of UNIX source code was available. No way was
> UNIX ever open source in the modern sense, but it did set a precedent
> and things could have been much worse. When you consider the Bell
> System's normal attitude toward proprietary information, the UNIX sources
> look even more valuable.
>
> -- Derek
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
next prev parent reply other threads:[~2009-05-20 5:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 16:48 Tim Newsham
2009-05-15 17:27 ` Jason Stevens
2009-05-15 18:09 ` Al Kossow
2009-05-19 2:20 ` Rafael R Obelheiro
2009-05-19 21:31 ` Warren Toomey
2009-05-19 21:49 ` John Cowan
2009-05-20 0:43 ` Jason Stevens
2009-05-20 4:56 ` Derek Peschel
2009-05-20 5:16 ` Jason Stevens [this message]
2009-05-20 8:21 ` Tim Bradshaw
2009-05-19 4:42 Aharon Robbins
2009-05-19 6:13 ` Jason Stevens
2009-05-19 15:12 ` M. Warner Losh
2009-05-19 15:28 ` Michael Kerpan
2009-05-19 15:21 ` John Cowan
2009-05-21 20:39 Brian S Walden
2009-06-05 3:48 Brian S Walden
2009-06-05 4:18 ` Larry McVoy
2009-06-05 11:42 ` Jim Capp
2009-06-05 14:40 ` John Cowan
2009-06-05 16:06 ` Ian King
2009-06-05 18:29 ` John Cowan
2009-06-06 5:20 ` Ian King
2009-06-05 18:40 ` 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=46b366130905192216h6ec2a0a6s64357feab5a58b95@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).