From: William Gunnells <thecount12@yahoo.com>
To: 9fans@cse.psu.edu
Subject: [9fans] cpu/auth auth/changeuser problems
Date: Tue, 17 Sep 2002 12:10:07 -0700 [thread overview]
Message-ID: <20020917191007.2197.qmail@web21403.mail.yahoo.com> (raw)
In-Reply-To: <20020917160005.28078.60230.Mailman@psuvax1.cse.psu.edu>
Sorry to bug you with newbie questions. As I progress
I'm finding out that most of my problems result in
either having a bad bootes password and or improper
usage of auth/changeuser.
After following the wiki documentation for cpu/auth I
try to auth/changeuser to add bootes and william. I
have noticed that my /mnt/keys directory is all wacked
up. So I'm going in an endless circle of manual
running
auth/keyfs -wp -m /mnt/keys /adm/keys >/dev/null
>[2=1]
and auth/changeuser.
So What's the proper order. How do I correct this. I
receive a bad character in file name under /mnt/keys.
Do I have to also run auth/enable whatever_user also.
__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com
next parent reply other threads:[~2002-09-17 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020917160005.28078.60230.Mailman@psuvax1.cse.psu.edu>
2002-09-17 19:10 ` William Gunnells [this message]
2002-09-21 20:22 Russ Cox
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=20020917191007.2197.qmail@web21403.mail.yahoo.com \
--to=thecount12@yahoo.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).