From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <1b22a776b517fda4fa544d326d8d7d0a@quanstro.net> References: <1b22a776b517fda4fa544d326d8d7d0a@quanstro.net> Date: Fri, 31 Jul 2009 00:05:03 +0800 Message-ID: <140e7ec30907300905p387e3403me05bd8168279a723@mail.gmail.com> From: sqweek 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: 327b4fb6-ead5-11e9-9d60-3106f5b1d025 2009/7/29 erik quanstrom : >> Hmm. =C2=A0A 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. =C2=A0It works reasonably well.... > > difficult to maintain in a pretty active environment; > one more reason for boot failure. Speaking of, I had a disk in my server die recently, and eventually it affected the nvram partition. So of course, when I booted up it couldn't read it and prompted me for the auth credentials, then tried to write back to nvram, got an i/o error and rebooted. The reboot could have been caused by some other problem shortly after (the motherboard seems to have given up on me also), but it raised the question - does an unsuccesful write to nvram halt the boot process? -sqweek