From: john@csplan9.rit.edu
To: scaron@umich.edu, 9fans@9fans.net
Subject: Re: [9fans] authentication fails strangely after changing password
Date: Wed, 22 Apr 2009 20:21:39 -0400 [thread overview]
Message-ID: <d920918eba918dfa71e7b62ac634a293@csplan9.rit.edu> (raw)
In-Reply-To: <op.uss76hucq2apjt@butterfly.diablonet.net>
> hi again,
>
> sorry for asking without experimenting first. and doubly so for replying
> to my own message.
>
> for the archives' sake, just wanted to say: i just blew away the nvram
>
> echo blah > /dev/sdC0/nvram
>
> then rebooted the system; respecified auth information when prompted.
>
> then used auth/changeuser to reset passwords for bootes and myself
>
> i'd hate to do it for hundreds of users but it did the trick for me.
>
> best,
>
> -sean
>
You should only have to do this when you change the bootes password;
it is Bad News when the nvram password doesn't match the bootes password.
No need to do it if you change a different user's password.
John
next prev parent reply other threads:[~2009-04-23 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 22:24 Sean Caron
2009-04-22 22:45 ` Sean Caron
2009-04-23 0:21 ` john [this message]
2009-04-23 0:24 ` erik quanstrom
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=d920918eba918dfa71e7b62ac634a293@csplan9.rit.edu \
--to=john@csplan9.rit.edu \
--cc=9fans@9fans.net \
--cc=scaron@umich.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).