From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <e35699b2ff8f880998eab2b6ce6656d5@plan9.bell-labs.com>
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot.c -> bad nvram key
In-Reply-To: <d9bb927d083025142cd90279eca5fd7d@proxima.alt.za>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-ikdstlvvpamksyyvrieypfhrzq"
Date: Mon,  8 Mar 2004 09:06:17 -0500
Topicbox-Message-UUID: 2366a366-eacd-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-ikdstlvvpamksyyvrieypfhrzq
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

My mistake, I missed the
	kfs...
and thought it was the kenrel complaining.  I'm an 
idiot, sorry for causing someone to go off and check
what kernel they where running.

Rename the nvram partition to something else and
the messages should go away.  Man 8 prep.
--upas-ikdstlvvpamksyyvrieypfhrzq
Content-Type: message/rfc822
Content-Disposition: inline

Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Mon Mar  8 07:18:33 EST 2004
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Mon Mar  8 07:18:30 EST 2004
Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001)
	id DC15619A01; Mon,  8 Mar 2004 07:18:18 -0500 (EST)
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id D36A719A0C; Mon,  8 Mar 2004 07:18:14 -0500 (EST)
X-Original-To: 9fans@cse.psu.edu
Delivered-To: 9fans@cse.psu.edu
Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001)
	id 84E6019A07; Mon,  8 Mar 2004 07:17:50 -0500 (EST)
Received: from sparkle.iba.co.za (beam.iba.co.za [196.30.44.140])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 185CB199F4
	for <9fans@cse.psu.edu>; Mon,  8 Mar 2004 07:17:48 -0500 (EST)
Received: from huddle.proxima.alt.za (prawn.iba.co.za [192.168.30.22])
	by sparkle.iba.co.za (8.11.7/8.11.5) with ESMTP id i28CHiD07955
	for <9fans@cse.psu.edu>; Mon, 8 Mar 2004 14:17:44 +0200 (SAST)
Message-ID: <d9bb927d083025142cd90279eca5fd7d@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot.c -> bad nvram key
Organization: Proxima Research & Development
From: lucio@proxima.alt.za
In-Reply-To: <20040308120540.GB2405@shire>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-RAVMilter-Version: 8.4.3(snapshot 20030221) (sparkle)
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.11
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
X-Reply-To: lucio@proxima.alt.za
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <https://lists.cse.psu.edu/archives/9fans/>
Date: Mon, 8 Mar 2004 14:17:24 +0200
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psuvax1.cse.psu.edu
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.63
X-Spam-Level: 

> I have tried with /386/9pcdisk and /386/9pcf but both kernels give me
> the same results:
> 
Don't worry about it, it is harmless.  You may even want to get rid of
the warning by executing auth/wrkey once the terminal is running.  I
suspect something has crept into the startup that always checks for
NVRAM and the installation seems always to create an NVRAM partition.
But, as I mentioned, it does no harm whatsoever.

>> root is from (il, tcp, local)[local!#S/sdC0/fs]:
>> user[none]: glenda
>> kfs...bad nvram key
>> bad authentication id
>> bad authentication domain
>> version...time...
> 
> Any advice?
> 
Of course, somebody may want to get to the bottom of this, but I'm not
sure it's worth the effort.

++L

--upas-ikdstlvvpamksyyvrieypfhrzq--