9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] factotum.hack -> factotum and ... no more CMOS as nvram
Date: Mon,  3 Nov 2003 22:17:16 -0700	[thread overview]
Message-ID: <Pine.LNX.4.44.0311032210060.28164-100000@maxroach.lanl.gov> (raw)


OK, on the older kernel I built for the geodes, I got it to the point that
I could use #r/nvram (i.e. CMOS) as the nvram for the key. On the newer
kernels, I can't get this to work. I've checked the data in CMOS (a.k.a.
nvram) and it is correct - - checksum is right, data is right, etc.

But I keep getting this 'bad authentication id' message. It's as though
the factotum is not looking the desired nvram, or not reading it
correctly. I have hardwired these variables in the kernel:

nvram is #r/nvram
nvroff is 0
nvrlen is 112

One thing that has changed is that the line:
factotum.hack factotum
in my old pccpu has changed to:
/386/bin/auth/factotum factotum
in the new pccpu. Could this have any bearing on my problem? What was
factotum.hack?

Is there some other nvram or other variable I should set? Will factotum
pick up these environment variables and "do the right thing", or is
something else needed?

thanks

ron



             reply	other threads:[~2003-11-04  5:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04  5:17 ron minnich [this message]
     [not found] <Pine.LNX.4.44.0311040939110.32465-100000@maxroach.lanl.gov>
2003-11-04 15:30 ` Russ Cox
2003-11-04 18:14   ` ron minnich
     [not found] <b5fc626be2e3710701ce3d07f98cfbd0@plan9.bell-labs.com>
2003-11-04 18:03 ` ron minnich

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.44.0311032210060.28164-100000@maxroach.lanl.gov \
    --to=rminnich@lanl.gov \
    --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).