From: sah@borf.com
To: 9fans@cse.psu.edu
Date: Tue, 1 Aug 2000 09:37:52 -0400 [thread overview]
Message-ID: <Pine.LNX.4.10.10008010934030.3794-100000@linux.borf.com> (raw)
Thanks to forsyth, the terms are up and running. Three cheers.
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.
So close I can taste it,
Sam
--------------------------------------------------------------
Sam Hopkins
sah@borf.com
"... let us tame the savageness of man, and make
gentle the life of this world."
next reply other threads:[~2000-08-01 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 13:37 sah [this message]
2000-08-01 14:53 ` [9fans] Re: your mail Lucio De Re
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=Pine.LNX.4.10.10008010934030.3794-100000@linux.borf.com \
--to=sah@borf.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).