From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Cross Message-Id: <200108221719.NAA07318@augusta.math.psu.edu> To: 9fans@cse.psu.edu Subject: Re: [9fans] standalone cpu/auth server?? In-Reply-To: References: <20010822142211.79D831998A@mail.cse.psu.edu> Cc: Date: Wed, 22 Aug 2001 13:19:48 -0400 Topicbox-Message-UUID: e4cc0df6-eac9-11e9-9e20-41e7f4b1d025 In article you write: >On Wed, 22 Aug 2001, Russ Cox wrote: > >> Something about your nvram is hosed. Try doing >> echo asdfasdfasdf >/dev/sdC1/nvram >> and then reboot again. If it still >I have tried that. The boot messages change to >boot: bad nvram key: file does not exist >password: (for which user???) For bootes, of course. :-) >authid[no default]: At this point, enter ``bootes'' or whatever auth user you're using. >authdom[bootes]: I'm not sure why the default is bootes here; normally, one enters one's Internet domain. >boot: #c/hostowner: bad arg in system >call > >cpu# who > >none >cpu# It looks like the authid is a blank string here (ie, ""). >Also, I put print statments in /sys/src/9/boot/key.c after >fd = open("#S/sdC1/nvram", ORDWR); >and open is successful (fd is 3). > >Is it possible to have nvram on a disk other than sdC0? >Can I use another cpu/auth server to boot this one (how)?? It looks like everything's okay, but you've got to enter the auth user's password and ID after zeroing out the nvram (I guess you're not really zeroing it, but you know what I mean). - Dan C.