From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <068514db3fdf8c5adc05aa0a9515a0ba@coraid.com> References: <4A8EAFED.7020708@maht0x0r.net> <068514db3fdf8c5adc05aa0a9515a0ba@coraid.com> Date: Fri, 21 Aug 2009 11:57:17 -0400 Message-ID: From: Akshat Kumar To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 via QEMU Topicbox-Message-UUID: 50597774-ead5-11e9-9d60-3106f5b1d025 Thank you for your input, Erik. I haven't yet gotten to replacing Ken FS proper with your version, though I soon hope to do so (I'd need to figure out how to boot it, as your version has problems with floppies - and I can only floppy boot). Preferably in a fashion that I can keep my current data. You have added a great deal of wonder- ful features, that I'd love to use. > > my best guess is an authentication problem. > I think you are right: so far I'd been skipping the secstore prompt, but here's what happens when I supply it: user[none]: akumar secstore password: factotum: secstorefetch: secstore: empty file chunk n=-1 nr=0 len=1727: !SC_read missing data Enter an empty password to quit. > flag authdebug > flag authdisable > > can be your friends. > I added allow to the above. Here's what I get now (on Ken FS - this is when I restart the QEMU instance and am now not asked for a password due to flag authdisable): il: allocating il!192.168.1.20!61378 permission granted by authdisable uid akumar = 2 permission granted by authdisable uid akumar = 2 hangup! connection timed out-3 61378/192.168.1.20.17008 Now, I think otherwise from the above: it seems not to be an authentication problem. Baffled. Ideas? Thanks, ak