From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <7b4b5f4e3a1df214c975d7cd2d6dc38f@quanstro.net>
References: <ed05e2587e339f5d4eea7b54ce93419f@quanstro.net>
	<7b4b5f4e3a1df214c975d7cd2d6dc38f@quanstro.net>
Date: Wed, 29 Jul 2009 09:43:09 -0400
Message-ID: <aa7e41150907290643j75a902c0md2615fa2e1a25d92@mail.gmail.com>
From: Dan Cross <crossd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] nvram
Topicbox-Message-UUID: 313423bc-ead5-11e9-9d60-3106f5b1d025

On Tue, Jul 28, 2009 at 2:37 PM, erik quanstrom<quanstro@quanstro.net> wrot=
e:
> this change as worked well on my personal system and at coraid
> for the past 6 months. =C2=A0it just works. =C2=A0even on hitherto unknow=
n
> controllers like the orion.

Hmm.  A few years ago, I ran into a similar problem and added a
variable that could be set in plan9.ini to specify where the nvram
actually is.  It works reasonably well....