From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sun,  6 Sep 2009 17:23:33 -0600
Message-Id: <87ljkr4pze.fsf@marvin.902northland.adams.home>
From: madams@phantomware.ca (Matt Adams)
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
CC: 9fans@9fans.net
In-reply-to: <375dc1a56df7cd9a4cd8c040fa37dbeb@quanstro.net> (message from
	erik quanstrom on Sun, 6 Sep 2009 17:45:24 -0400)
References: <375dc1a56df7cd9a4cd8c040fa37dbeb@quanstro.net>
Subject: Re: [9fans] Installer error (not supposed to happen)
Topicbox-Message-UUID: 6727bc18-ead5-11e9-9d60-3106f5b1d025


 > if you can't get back on track by forcing the step
 > by just typing it at the prompt

I can't seem to do that; the installer doesn't give me a prompt after
the configfs step.

 > the easiest trick might be something like this at the installer
 > prompt:
 >
 > 	!rc
 > 	# cp /bin/test /tmp/builtintest
 > 	# {echo '#!/bin/rc'
 > 		echo '/tmp/builtintest $* ||
 > 		echo >[1=2] failed test args: $*}>/tmp/test
 > 	# chmod a+x /tmp/test
 > 	# bind /tmp/test /bin/test

I had to add a quote after ...failed test args: $* to get this to work
but it seems to have done the trick and gives me a little more info.

 > this will at the least tell us what the full arguments
 > to test were.  and maybe give you some ideas on what
 > to do next.

So instead of "unexpected operator/operand" I get the following:

failed test args: -f /dev/sd*/9fat
failed test args: -f /dev/sd*/fossil*
failed test args: -f /dev/sd*/arenas
failed test args: -f /dev/sd*/isect

I get the same results regardless of which file system types I select.


Thanks,

Matt