From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <721abf91e7c486c1215a3ab62d0585da@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "Can't read from nvram: /env/nvrof file does not exist"
From: "Russ Cox" <rsc@plan9.bell-labs.com>
In-Reply-To: <200304180310.h3I3AX516789@augusta.math.psu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu, 17 Apr 2003 23:13:32 -0400
Topicbox-Message-UUID: 925b13e4-eacb-11e9-9e20-41e7f4b1d025

> Hmm, that's strange.  I doubt it's a bug in the readnvram code, but
> rather, something weird that's causing the read to fail, and when
> readnvram() prints out an error message, "%r" is being interpolated
> with the last error string (that the nvroff environment variable
> doesn't exist).  My guess is that the nvram file doesn't exist on the
> 9fat on the flash device.

No, it's definitely a bug.  In order to use $nvram,
the code requires $nvroff to be set too.  Read it,
you'll see.