Sorry its taken me so long to respond - I'd like to keep it rolling so noone loses interest. Replies to various messages below:
On Wed, Feb 12, 2003 at 09:22:17AM -0500, Sean Dague wrote: > Not really an issue. Perl runs on every platfrom known to man (including > Palm Pilot and S/390 Native), and correctly written perl code will run on > all versions of Perl released since 1998. right, i was referring more to a j random embedded perl interpreter, as opposed to perl itself. > I'm going to give this one last college try.... > > KEEP IT SIMPLE > > The reason that BOEL is nice, and works, is because what it does it really > simple. There is a script, and the script goes from A -> B -> C, and its > really clear what it does. you know, that's a good point. > For a science project it would be neat to build this cool little engine that > connects to a couple different servers, figures out what it should do, and > makes sure it all happens. I think it makes sense to allow people to add their own complexity to do this, without having to worry about mkautoinstallscript overwriting stuff. I think this can be done easily enough. >From mchasal: > So, I think the first step down this road would be to change > mkautoinstallscript to create scripts per client using info from the SIS > db. We would additionally add the necessary attrs to the database to > achieve this. I agree with this as a first step - Brian: do you? >From Gary: > That sounds great, but I haven't had a lot of success in having the > auto-generated .master script get me the image I need. The scripts get > me a system that's close, but I always seem to need to edit something to > get something set up like I need. Unfortunately the changes I need to > make need to be made to each of the .master scripts. That's usually > only a handful, but it's a pain, especially when I miss one. > > I could code these changes into the normal generation code, but it seems > that in continuing to add special cases to the script generation code > Ill eventually end up with more command line options than gcc. I think this can be solved w/ SI using the SIS database, and being more flexible w/ script generation - e.g, having a skeleton script, that is populated using mkautoinstallscript and data from the SIS dbase, but also allows you to add your own code. Then, we should be able to take mkautoinstallscript down to something like this, in the simple case: # mkautoinstallscript --force --all which means, use all the information you already know about (ip assignment method, etc) from the database, and regenerate all my scripts. ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
