From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Help for home user discovering Plan 9
Date: Fri, 17 Apr 2009 09:35:46 -0400 [thread overview]
Message-ID: <3754477e974a1c0f3b4875d046b3249f@quanstro.net> (raw)
In-Reply-To: <p76hb6x9uc.ln2@news.homelinux.net>
> The Plan9 project started in 1980, took around 9 years to be solid
> enough to be usable and that too by the internal and, or lab people
> [http://plan9.bell-labs.com/sys/doc/9.html] only.
unless one is speaking in geologic terms, there's a significant difference
between the "mid-1980s" and 1980.
in fact the quote is "Plan 9 began in the late 1980's...". and "... by
1989 the system had become solid enough that some of us begain
using it as our exclusive computing environment."
i'd encourage you to read your source material.
- erik
next prev parent reply other threads:[~2009-04-17 13:35 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 6:05 Jim Habegger
2009-04-14 11:09 ` Sergey Zhilkin
2009-04-14 12:36 ` Pietro Gagliardi
2009-04-14 12:38 ` Devon H. O'Dell
2009-04-14 12:46 ` Pietro Gagliardi
2009-04-14 12:37 ` Devon H. O'Dell
2009-04-14 13:17 ` Andrés Domínguez
2009-04-15 8:26 ` Eris Discordia
2009-04-15 11:48 ` Pietro Gagliardi
2009-04-17 13:14 ` Balwinder S Dheeman
2009-04-17 13:00 ` Eris Discordia
2009-04-17 13:35 ` erik quanstrom [this message]
[not found] ` <F1194F3CF3ADD35D3B0DF261@192.168.1.2>
2009-04-17 14:03 ` Devon H. O'Dell
2009-04-18 16:23 ` ron minnich
2009-04-18 16:29 ` lucio
2009-04-17 14:08 ` Steve Simon
2009-04-17 16:08 ` hiro
2009-04-17 19:26 ` Gorka Guardiola
2009-04-20 10:41 ` Balwinder S Dheeman
2009-04-20 11:52 ` Federico G. Benavento
2009-04-20 15:02 ` Uriel
2009-04-20 16:21 ` erik quanstrom
2009-04-20 18:57 ` Steve Simon
2009-04-20 20:22 ` David Leimbach
2009-04-18 0:13 ` Robert Raschke
2009-04-18 5:47 ` lucio
2009-04-18 6:03 ` J.R. Mauro
2009-04-18 6:11 ` lucio
2009-04-18 6:08 ` Eris Discordia
2009-04-18 16:15 ` J.R. Mauro
2009-04-18 16:20 ` erik quanstrom
2009-04-18 16:34 ` J.R. Mauro
[not found] ` <87DD0DBADB1647F789D9EB63@192.168.1.2>
2009-04-18 16:19 ` J.R. Mauro
2009-04-18 18:29 ` Eris Discordia
[not found] ` <0AE52A74098A8B999540233C@192.168.1.2>
2009-04-18 19:43 ` J.R. Mauro
2009-04-18 19:34 ` Eris Discordia
[not found] ` <B6FF436789F29A3B7977687E@192.168.1.2>
2009-04-18 20:44 ` J.R. Mauro
2009-04-20 10:41 ` Balwinder S Dheeman
2009-04-20 18:13 ` J.R. Mauro
2009-04-22 12:19 ` Balwinder S Dheeman
2009-04-22 13:09 ` Skip Tavakkolian
2009-04-20 10:41 ` Balwinder S Dheeman
2009-04-20 10:41 ` Balwinder S Dheeman
2009-04-15 13:52 ` lucio
2009-04-15 13:32 ` Eris Discordia
2009-04-15 16:00 ` Steve Simon
2009-04-15 16:09 ` ron minnich
[not found] ` <69CBEA1CA346E38D7A5C7507@192.168.1.2>
2009-04-15 13:02 ` hiro
2009-04-15 13:05 ` Jim Habegger
2009-04-15 12:50 ` Eris Discordia
2009-04-15 14:00 ` Navin Johnson
2009-04-15 14:39 ` hugo rivera
2009-04-16 14:07 ` Jim Habegger
2009-04-17 13:14 ` Jim
2009-04-14 14:46 Jim Habegger
2009-04-14 15:41 ` maht
2009-04-14 19:43 ` Sergey Zhilkin
2009-04-14 23:28 ` Jim Habegger
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=3754477e974a1c0f3b4875d046b3249f@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).