From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] upgrading a 3rd edition network -- fairly long message
Date: Thu, 2 May 2002 17:31:54 -0400 [thread overview]
Message-ID: <2739ced0121abf9e0f76123d4e1be728@plan9.bell-labs.com> (raw)
I hope you would have gotten a different message than
"bad message in devmnt" if the problem was not being
able to contact the auth server, but maybe.
Russ
next reply other threads:[~2002-05-02 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 21:31 Russ Cox [this message]
2002-05-02 21:47 ` Axel Belinfante
2002-05-02 22:25 ` John Packer
-- strict thread matches above, loose matches on Subject: below --
2002-05-02 22:28 Russ Cox
2002-05-02 21:18 dpx
2002-05-02 21:26 ` Axel Belinfante
2002-05-02 21:16 Russ Cox
2002-05-02 2:38 dpx
2002-05-02 20:56 ` Axel Belinfante
2002-04-30 10:10 forsyth
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=2739ced0121abf9e0f76123d4e1be728@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).