From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: CPU authentication...
Date: Wed, 27 Mar 1996 09:24:52 -0500 [thread overview]
Message-ID: <19960327142452.6Ft5pB9m1vKniaqm3ZgB5KjzXnz-8tdjlQl9MER1WC4@z> (raw)
> The cpu server comes up with
> boot: can't read nvram: unknown device in # filename
> boot: bad nvram key:
>
> It then comes out and asks for the password... I provide the password
> (The same as the server) - it prompts for the authid, and the domain
> I provide it. - And it seems to work.
> It then prompts:
> boot: can't write key to nvram: fd out of range or not open.
most PCs haven't got any usable NVRAM, so the CPU server
uses a special disc partition instead. if that doesn't exist, or
(as in this case) the appropriate SCSI or IDE device isn't configured,
you'll get the diagnostics you show above. in other words,
they are `normal' on a PC.
when it's convenient, you should apply the updates to auth/wrkey and /sys/src/9/boot,
if you haven't done already.
next reply other threads:[~1996-03-27 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-27 14:24 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-03-27 17:42 Steve
1996-03-26 1:45 Thomas
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=19960327142452.6Ft5pB9m1vKniaqm3ZgB5KjzXnz-8tdjlQl9MER1WC4@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).