> 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
