2009/7/29 erik quanstrom <quans...@quanstro.net>: >> 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.... > > 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
