From: td@plan9.bell-labs.com td@plan9.bell-labs.com
Subject: Plan 9 for dual Pentium machine...
Date: Tue, 9 Apr 1996 08:46:01 -0400 [thread overview]
Message-ID: <19960409124601.lEYUdUk6pKAapRFDxuEDV8g4CPmHHIg7kwVPvdNNrDs@z> (raw)
Julian B Hilaire <dcfreenet.seflin.lib.fl.us!d025826c> asks:
>Has anyone out there actually managed to connect to either
><http://plan9.att.com/plan9/> or <ftp://plan9.att.com/plan9/> on or after
>April 7th?
I tried getting http://plan9.att.com/plan9/, and running ftp
to plan9.att.com from my courtesy account at Drew University &
both worked fine. What's the problem?
Note that with the AT&T corporate split-up our canonical
site-name has changed to plan9.bell-labs.com, and that
plan9.att.com might stop working later this year.
next reply other threads:[~1996-04-09 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-09 12:46 td [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-04-12 0:48 John
1996-04-10 21:59 Julian
1996-04-09 12:44 dhog
1996-04-09 12:00 Julian
1996-04-08 18:53 Dave
1996-04-08 16:57 de5
1996-04-08 3:42 jim
1996-04-06 9:31 Ta-Wei
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=19960409124601.lEYUdUk6pKAapRFDxuEDV8g4CPmHHIg7kwVPvdNNrDs@z \
--to=td@plan9.bell-labs.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).