Hi Dave.
Thanks for your feedback. I see how my original email could have led
one to think: "Why 13 steps and 3 scripts? Seems like a step backward
from a usability standpoint." From your response as well as a few others
(which were verbal) I can see I need to clarify the intent (a specific
use) and general level of need (low) of these scripts, in order to
clarify the ease-of-use level of AI commands.
The scripts were prepared for quick setup and error-proof running of a
demo. The install server is a foreign computer in a new lab containing
a SPARC system to install. One script configures this system to work
with the lab network; it has nothing to do with AI proper. If
installadm is run on a system already configured on a lab network, this
script is not needed.
The other two scripts are so I won't make typos while giving a demo.
One of them runs the installadm commands, the other: dhcp commands.
Both sets of commands can take some lengthy pathnames as arguments.
Thirteen steps are many. However, some of them are basic, like
downloading the iso or booting the client. Three deal with setting up
networking on a laptop foreign to the lab network. The steps can be
consolidated if needed. I'll put a small amount of time into this; not
sure that there is a lot of bang for the buck for doing this.
Thanks for pointing out the name clash of "setup_install_server." I'll
find another name.
As for general usability of AI, there is room for improvement, and Ethan
and others have been working on that. That said, it is much better than
my original email may have led some to believe. Hopefully, after this
email, the credibility of AI's commandline interface is restored.
I'll repost with updated scripts when they are ready.
Thanks,
Jack
On 02/02/09 13:19, Dave Miner wrote:
> Jack Schwartz wrote:
>> Hi everyone.
>>
>> In an effort to help you sanity test our images, here are some
>> scripts I prepared (for a demo) which can be used for quick setup of
>> an install server laptop and install environment in a lab. These can
>> aid you in testing...
>>
>
> Two things:
>
> - The need for these scripts (and 13 steps of instructions to go with
> them) indicates unfulfilled requirements in the standard tools.
> Please file appropriate bugs if they aren't there already.
>
> - Using the "setup_install_server" name creates an exceptionally bad
> collision with the existing Solaris command of the same name.
>
> Dave
>
>
