From: Jim Bennett jwb@almaren.org
Subject: [9fans] AT&T
Date: Sat, 13 May 2000 20:36:01 -0500 [thread overview]
Message-ID: <20000514013601.ZVl7gMBUmYpLy2Po1S2nM4BWfi1-ujXlH4DOSMlx2pE@z> (raw)
jhs@labrea.research.att.com wrote:
>
> |I'd certainly be interested in a Open Source clone of Plan 9 to point of
> |spending my own time and money to that end. The less that goes to ATT (for
> |their non-action/support) the better.
>
> Since Bell Labs hasn't been part of AT&T since 1995, I don't think you
> need worry yourself overmuch about this.
I'm sorry to but in, but AT&T doesn't quite deserve this kind of
scorn. They might be poked fun at, for not really knowing how to
market anything that is NOT "telephone" related (UNIX, "BellMac32",
Hobbit, the list is quite long). But they're NOT an "evil empire".
[No matter what "TPC" did in "The President's Analyst". :>D :>D]
JB
--
----------------------------------------
"The future is not what it used to be."
-Anonymous
next reply other threads:[~2000-05-14 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-14 1:36 Jim [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-14 9:57 Lucio
2000-05-14 9:25 Lucio
2000-05-14 0:59 Jim
2000-05-14 0:58 jhs
2000-05-14 0:33 Jim
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=20000514013601.ZVl7gMBUmYpLy2Po1S2nM4BWfi1-ujXlH4DOSMlx2pE@z \
--to=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).