From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4575B46A.6070501@gmail.com> Date: Tue, 5 Dec 2006 19:03:22 +0100 From: Rodolfo Garcia User-Agent: Icedove 1.5.0.8 (X11/20061116) MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] auth stuff: never saw this one before: References: <13426df10612041415m2d9b01eboc10c7ede52187aa5@mail.gmail.com> <676c3c4f0612041425s14be0a3s6fb3e68fe3b7ee95@mail.gmail.com> <13426df10612041925u60b9bf2dl435d5ced8362695d@mail.gmail.com> <7d3530220612041953q3efbf402y22722525d20b164b@mail.gmail.com> <4575B345.3030706@gmail.com> In-Reply-To: <4575B345.3030706@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: eb53a294-ead1-11e9-9d60-3106f5b1d025 When I have this problem, I set up the Set up the "fossil admin's PASSWORD" (the user bootes usually), and this password must be the same that the nvram. Problem ended. Why? I dont know. slds. Rodolfo Garcia wrote: > When I have this problem, > > I set up the fossil's admin (bootes), and this password must be the > same that the nvram. Problem ended. > > Why? I dont know. > > slds. > > John Floren wrote: >> On 12/4/06, ron minnich wrote: >>> On 12/4/06, Richard Bilson wrote: >>> >>> > Both times it worked after I nuked the nvram. >>> > >>> >>> Tried that too, but no joy. >>> >>> ron >>> >> >> Unfortunately, I've hit the same problem several times, and I've fixed >> it a few times, but I always forget to write down what I did. >> Argh >> >> >> John > >