From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] what means: cpu: waiting for FS: ?
Date: Thu, 5 Sep 2002 09:40:02 +0200 [thread overview]
Message-ID: <200209050740.g857e2P14575@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Wed, 04 Sep 2002 19:44:29 -0400." <0b04ed7e42106d18a29074d22a22aca6@plan9.bell-labs.com>
Yes, I'm using the same password.
Also, what I forgot to mention in my previous post:
Yesterday (well, by now the day before yesterday) It Worked!
and of course, I Did Not Change Anything!
However, I did add the tcp564 trampoline script to /rc/bin/service
on the (diskless) cpu server, to access the file server via tcp.
Could that be related?
I'm still at home, I tried to move the script 'out of the way'
on the file server, but that seems not to stop the listener
(or is it because I already have a connection open?)
I'll have a closer look at the cpu server at work later today.
> It means your terminal at home is unable to authenticate to
> your cpu server at work, and /bin/cpu is not kind enough to
> tell you what went wrong. It's weirder than that, though.
> The terminal thinks the auth worked, and the cpu server
> thinks it didn't. That shouldn't happen (the protocol
> is cpu server speaks last). I've seen this before but
> don't remember what the problem is. It seems likely
> there's a key mismatch somewhere. Are you using the
> same password in drawterm and on the terminal?
next prev parent reply other threads:[~2002-09-05 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 23:44 Russ Cox
2002-09-05 7:40 ` Axel Belinfante [this message]
2002-09-05 7:48 ` Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2002-09-05 22:21 Geoff Collyer
2002-09-05 19:08 Zoltan Jarai
2002-09-05 13:09 Russ Cox
2002-09-05 13:54 ` Axel Belinfante
2002-09-05 15:41 ` Axel Belinfante
2002-09-04 19:21 Axel Belinfante
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=200209050740.g857e2P14575@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).