Re: Cfengine as Jumpstart "finish" script?

[Elmar Kurgpold]

Not exactly.  I put the cfengine binary and emergency (I call it
bootstrap) script in the jumpstart tree where the begin and finish scripts
are.  I just point each system to a common finish script which calls
cfengine from the appropriate directory, using the ${SI_CONFIG_DIR}
variable.

It hardly seems worth the trouble to mess with the Solaris distribution,
since you'll have to redo it whenever you put in a new release.  

        ++Elmar

On Mon, 5 Feb 2001, David Carmean wrote:

> 
> Has anybody done anything like the following:
> 
> Place a copy of the cfengine binary and an "emergency" config file in 
> the jumpstart miniroot to be copied into memory on the install client, 
> and transfer control to cfengine directly from the "finish" script?
> 
> 
> 
> --                                                         _    .    _    .   
>  _
> David Carmean                                           <address@hidden>
>   PGP fingerprint =  B1 57 EB A8 1D B9 87 86  5F 5C 51 A4 F2 5E ED FD
> 
>       I don't want the world, I just want your half.
>                               -- They Might Be Giants
> 
> _______________________________________________
> Bug-cfengine mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-cfengine
> 

|  Elmar Kurgpold
|  Email: address@hidden