>>>>> Sean Dague wrote: > I am curious about the need for changing node name and hardware differences after install, as System Configurator already does that. If you have needs beyond what SC current supports, I'd like to hear about them on the [EMAIL PROTECTED] list.
I do it quite often. The usual case where you need to do it is when you have a multi-homed host. In my case, I'm PXE booting off of the network interface that is *not* coupled to the system hostname (e.g. myhost-eth1.localdomain). In those cases, systemimager's dhcp picks up the data from the internal interface, which is usually incorrect for the 'real interface'. For these hosts, I usually have to edit the master script generated by systemimager to morph the variables fed to systemconfigurator into the right values for the as-yet-unseen primary interface. It would be nice to be able to clone the systemconfigurator invocation from the master script into a new 'local' script. That way, I don't have to re-integrate my modifications into every new master script as I upgrade the various system* packages. On the hardware front, the only thing I've had to customize is to provide a local PCI map so that the right Ethernet driver gets chosen for the kernel revision. I'm not sure the script dir helps there. This seems more like an item that the overrides concept is designed to handle. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
