From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] install terminal
Date: Wed, 14 Aug 2002 05:56:35 +0100 [thread overview]
Message-ID: <0398f305ad52300ffa546e565470ae1c@caldo.demon.co.uk> (raw)
flag attach and flag authdebug typed on the file server console
might give a little more information about the reason it objected.
`might' is the key word there, because the
messages do not separate all cases.
next reply other threads:[~2002-08-14 4:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 4:56 Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-14 6:56 okamoto
[not found] <20020813055402.18697.40853.Mailman@psuvax1.cse.psu.edu>
2002-08-13 16:57 ` William Gunnells
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=0398f305ad52300ffa546e565470ae1c@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).