I am running System Imager version 4.0.2. I am using UYOK (or at least that is
what I am trying to do). But in the snippet I sent it looks like the SI
scripts still try to look for the BOEL binaries.
-Original Message-
From: [EMAIL PROTECTED] on behalf of Andrea Righi
Sent: Sun 5/4/2
Thomas Krause wrote:
> I still think that having to specify the methods for every command in the
> cluster.txt is too verbose and unnecessary in the general case.
>
> My idea of specifying multiple methods was not trying multiple methods on
> the same client, but trying the first method that exist
I will be out of the office starting 02/05/2008 and will not return until
20/05/2008.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100
I still think that having to specify the methods for every command in the
cluster.txt is too verbose and unnecessary in the general case.
My idea of specifying multiple methods was not trying multiple methods on
the same client, but trying the first method that exist for a given command.
So if you
Thomas Krause wrote:
> Ok, first of all the syntax of the si_power tool should be the same
> regardless of the method used IME.
>
> There should also be a good default that works in most cases (probably the
> ssh way).
>
> Maybe the best way would be to create a separate si_power configuration fi
Fulda, Paul (Mission Systems) wrote:
[snip]
> Floating point exception
Which version of systemimager are you using?
Are you using BOEL or UYOK
(http://wiki.systemimager.org/index.php/UYOK)?
-Andrea
-
This SF.net email is sp
Stas Oskin wrote:
> Hi.
>
>> In SystemImager 4.1.x the hardware.lst is always re-generated at end of
>> imaging, so this problem should be already fixed in recent versions
>> (i.e. 4.1.6).
>
> I guess, time to update to latest unstable :).
>
Or better time for us to release a new stable versi