From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9fd55876f7b5da278df39bade7f1ac99@proxima.alt.za>
To: 9fans@9fans.net
Date: Wed,  1 May 2013 07:37:29 +0200
From: lucio@proxima.alt.za
In-Reply-To: <20130430201309.43d0e9b5@zinc.9fans.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Subject Sheevaplug and NVRAM
Topicbox-Message-UUID: 4dc7c7d8-ead8-11e9-9d60-3106f5b1d025

> However, if you don't want to spread your passwords over
> your network, you would prefer to use the flash, simply
> by adding, for example, the following to your /cfg/*/cpurc:
>
> echo add nvram 0x100000 0x120000 >'#'F/flashctl

That's too late for wrkey.

There's a lot about the Sheeva that doesn't make any sense to me:
/cfg/pxe/example-kw does not set the bootfile, nor does the
documentation state what loader should be specified as bootf in
/lib/ndb.

So I put the actual kernel name in /lib/ndb (/arm/9plug), which gets
loaded four times before actually activating.

But by then there is no suggestion of an nvram, no such entry exists
in /env.

I'm a little lost.

++L