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 20:05:50 -0600	[thread overview]
Message-ID: <12B1C5E5-815A-40DD-BFB7-957B5BA1C37A@tinker.com> (raw)
In-Reply-To: <20070510201231.DDD891E8C3B@holo.morphisms.net>


On May 10, 2007, at 2:12 PM, Russ Cox wrote:
>
> It is correct that
>>      changeuser: can't open /adm/keys.who
> is unimportant.
>
> You should be able to run auth/wrkey on the console
> instead of echoing garbage into /dev/sdC0/nvram.
> Either way you do need to reboot in order to restart
> the machine's factotum.
>
> Russ

OK, that was not the problem.  I have done auth/wrkey
twice and taken care not to mistype the password and the
secstore key.  I have rebooted more times than I can count.
I have run auth/changeuser bootes and auth/changeuser kim
and made sure that I keyed the passwords in correctly.  I
have rebooted some more.  I still have the same problem.

I suspicion that the problem is somewhere else.

What components are involved in handling this remote login?

Do they log anything?

Can I make them log more?

Which piece of software is issuing the message:

     cpu: server lies got 39dd60dfe7adb072.1510726563 want  
9b3644fcb26b1a66.0: cs gave empty translation list


I would actually like to track this down myself but I seem
to keep hitting brick walls.

Kim



  reply	other threads:[~2007-05-11  2:05 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
2007-05-10 20:12     ` Russ Cox
2007-05-11  2:05       ` Kim Shrier [this message]
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=12B1C5E5-815A-40DD-BFB7-957B5BA1C37A@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).