From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <14ec7b180806301000w652e5bifac6c730ce2762b0@mail.gmail.com>
Date: Mon, 30 Jun 2008 11:00:40 -0600
From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
In-Reply-To: <20080630160650.D5AD31E8C22@holo.morphisms.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <140e7ec30806300832h11439366p14a39432c427680c@mail.gmail.com>
	<20080630160650.D5AD31E8C22@holo.morphisms.net>
Subject: Re: [9fans] 9vx
Topicbox-Message-UUID: cdf6eb64-ead3-11e9-9d60-3106f5b1d025

now that you've explained the cs issue things are much clearer. i can
confirm that I have successfully booted a 9vx terminal off a remote
plan9 server using a small modification to factotum.

the original boot process failed with:

password:
!
authentication failed (auth_proxy rpc write: bootes: Connection
refused), trying mount anyways
boot: mount /: fossil authCheck: auth protocol not finished
9vx panic: boot process died: unknown

and the change simply sidesteps factotum using cs to figure out
who/what to dial, instead just using IP addresses.

here's the hack:

9grid% yesterday -d util.c
diff /n/dump/2008/0630/sys/src/cmd/auth/factotum/util.c
/sys/src/cmd/auth/factotum/util.c
33c33
< 		return authdial(net, authdom);
---
> 		;//return authdial(net, authdom);
9grid%

now compile 8.factotum and copy it as 9vx/src/9vx/factotum.9 and recompile 9vx.

unfortunately with a terminal booted thusly i no longer have /mnt/term :)