9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: your mail
Date: Tue,  1 Aug 2000 16:53:42 +0200	[thread overview]
Message-ID: <20000801165341.F4605@cackle.proxima.alt.za> (raw)
In-Reply-To: <Pine.LNX.4.10.10008010934030.3794-100000@linux.borf.com>; from sah@borf.com on Tue, Aug 01, 2000 at 09:37:52AM -0400

On Tue, Aug 01, 2000 at 09:37:52AM -0400, sah@borf.com wrote:
> 
> Now I need to connect to the V2 fs to transfer important files over to
> V3 so we can complete the 'upgrade.'  Attempts of 9fs to our V2 fs via a
> V3 term return "mount: mount bootes: attach -- authentication failed."
> Also, the V2 fs states "bad AuthTs num."  The passwords and usernames are
> identical on both systems.
> 
I'm running very successfully with 2ed AUTH and FS.  CPUs are somewhat
confused, and I can't quite get the 2ed AUTH to execute the mail stuff
on a 3ed CPU :-(

On the other hand, I'm not sure how a 2ed FS would handle 3ed AUTH,
which may be your problem.  Between a rock and a hard place, like me.
It may of course be merely a question of making sure AUTH and FS are
in the right type of sync, which presumably means the same password
for the FS and the AUTH uid.

I'll enable AUTH on the 3ed CPU server a little later, see what
confusion I can create.  In the meantime...

> So close I can taste it,
> 
... I think you just need a slightly longer tongue, that's all :-)

++L


  reply	other threads:[~2000-08-01 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-01 13:37 sah
2000-08-01 14:53 ` Lucio De Re [this message]
2000-08-01 15:13 [9fans] Re: your mail forsyth
2000-08-02  1:24 presotto
2003-10-20 10:33 [9fans] porting from vs. porting to Plan 9 Douglas A. Gwyn
2003-10-21  0:10 ` [9fans] Re: your mail Roman Shaposhnick

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=20000801165341.F4605@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).