From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "bad authentication domain"
Date: Thu, 24 Apr 2003 08:20:29 -0400 [thread overview]
Message-ID: <5d5595f34c16e7ab40b6280d93076553@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304231511030.30929-100000@maxroach.lanl.gov>
Readnvram is printing the message.
If there is an nvram file in 9fat, we usually
make it 512 bytes, just to be one sector.
I think the structure itself is 109 bytes.
Rather than rebuild whatever prints that
(/boot/boot), you could just boot the system
and then use auth/wrkey to reset the nvram.
It's much easier to deal with the user programs
that recompile your kernel unnecessarily.
next prev parent reply other threads:[~2003-04-24 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 21:13 ron minnich
2003-04-24 12:20 ` Russ Cox [this message]
2003-04-24 15:08 ` ron minnich
2003-04-24 17:15 ` Russ Cox
2003-04-24 17:45 ` 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=5d5595f34c16e7ab40b6280d93076553@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).