From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <60f350c375d4ee1b27b7a0459fbeb046@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "Can't read from nvram: /env/nvrof file does not exist"
From: rsc@plan9.bell-labs.com
In-Reply-To: <200304181833.h3IIXK520049@augusta.math.psu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Apr 2003 14:37:06 -0400
Topicbox-Message-UUID: 92bd3538-eacb-11e9-9e20-41e7f4b1d025

> I don't think so; why do you say that?  The environment variable you
> could use to force it would be to set nvram.  Eg, nvram=#S/sdD0/9fat
> will force it to look for plan9.nvr on the 9fat partition on sdD0.  If
> you set it to, e.g., #S/sdD0/9fat!foo.nvr, you can use a different
> filename.
>
> My guess is that plan9.nvr doesn't exist on the 9fat partition.  Did
> you `dd -if /dev/zero -of plan9.nvr -count 1'?

You could also set up an nvram partition and use #S/sdD0/nvram,
which I thought was what he did.

In any case, none of this is going to work unless 9load finds the
disk, parses the partition tables, and leaves the info for the kernel.
That's the real problem.