On Sat, Feb 14, 2004 at 10:52:42PM -0600, Brian Elliott Finley wrote: > This is actually one of the big questions on my plate right now. Some > ideas (in no particular order): > > - SI post-script that reads a text file (stored in the ./scripts > directory) and invokes System Configurator for each interface > specified. Such a text file might look something like: > > #<HOST> <IFACE> <IP> <MASK> <BCAST> <GATEWAY> > host1 eth0 192.1.1.1 255.255.255.0 - - > host1 eth1 192.2.2.1 255.255.255.0 - - > host1 tr1 192.3.3.1 255.255.255.0 - - > host1 eth0:1 192.4.4.1 255.255.255.0 192.4.4.255 192.4.4.254 > > - Maybe incorporate this info into the SystemInstaller database somehow. > Perhaps store it there, but generate this file from it? Dunno. Maybe > even have the client query the database directly over the net? Dunno.
Ultimately, putting everything in the SIS database seems best. I'd prefer adding this data in the autoinstallscript.conf file vs. a post-install script - we'd then be able to do it all in one call to SC, and without teaching users any new commands/hooks. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
