9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Kim Shrier <kim@tinker.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Hopefully, one last problem
Date: Thu, 10 May 2007 12:04:09 -0600	[thread overview]
Message-ID: <DBAC59CD-D054-4BE7-8B90-11B03097CCDE@tinker.com> (raw)
In-Reply-To: <32d987d50705100857l3a83a9d3r2841ef729adf649f@mail.gmail.com>

On May 10, 2007, at 9:57 AM, Federico Benavento wrote:

> yes, you didn't pay enough attention to my last mail, did you? ; )
>

Well, I thought I did but the evidence is against me.

> If I'm not mistaken, the pass you entered afer you did echo fsdajl >
> /dev/sdC0/ctl
> doesn't match the one you entered when you did auth/changeuser
>
>

Actually, do you mean echo fsdajl > /dev/sdC0/nvram ?

Here is what I typed in:

     term% echo blahblahblah >/dev/sdC0/nvram
     term% fshalt
        ...
        boot with 9pccpuf kernel
        ...
     root is from (tcp, il, local)[local!#S/sdC0/fossil]: hit enter
     bad nvram key
     bad authentication id
     bad authentication domain
     authid: bootes
     authdom: tinker.com
     secstore key: password_number_one
     password: password_number_two
     time...
     venti...fossil(#S/sdC0/fossil)...version...time...

     init: starting /bin/rc
     vh# auth/changeuser bootes
     Password: password_number_two
     Confirm password: password_number_two
     assign Inferno/POP secret? (y/n) n
     Expiration date (YYYYMMDD or never)[return = never]: hit enter
     Post id: hit enter
     User's full name: bootes on vh
     Department #: hit enter
     User's email address: hit enter
     Sponsor's email address: hit enter
     changeuser: can't open /adm/keys.who
     vh#

I believe someone told me that the error message from changeuser
was not important.  Sometime after I did this, I added bootes to
both the sys and adm groups.  It is possible that I fat-fingered
password_number_two so I will go through this again the next time
I go down to the machine room.

Kim

> On 5/10/07, Kim Shrier <kim@tinker.com> wrote:
>> I have a cpu/auth/file server configured and running.  When I
>> try to log in using drawterm, I see the following:
>>
>>      kim@tinker.com password:
>>      ?you and auth server agree about password.
>>      ?server is confused.
>>      cpu: server lies got 39dd60dfe7adb072.1510726563 want
>> 9b3644fcb26b1a66.0: cs gave empty translation list
>>
>>      goodbye
>>
>> I assume I have missed something obvious but I don't seem to be
>> able to track it down.
>>
>> Thanks for any assistance.
>> Kim
>>
>
>
> -- 
> Federico G. Benavento
>




  reply	other threads:[~2007-05-10 18:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 15:53 Kim Shrier
2007-05-10 15:57 ` Federico Benavento
2007-05-10 18:04   ` Kim Shrier [this message]
2007-05-10 20:12     ` Russ Cox
2007-05-11  2:05       ` Kim Shrier
2007-05-11 11:58         ` Russ Cox
2007-05-12 23:28           ` Kim Shrier
2007-05-10 20:23     ` erik quanstrom
2007-05-10 21:04       ` Russ Cox
2007-05-10 15:58 ` Russ Cox
2007-05-10 18:04   ` Kim Shrier

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=DBAC59CD-D054-4BE7-8B90-11B03097CCDE@tinker.com \
    --to=kim@tinker.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).