Regarding the configuration options that are available through XML: I've been using the DTD files that you can find in /usr/share/autoinstall/dtd/
These are the files that are used by the autoinstaller to verify the XML script. That, of course, presupposes that the DTD files themselves are complete -- i.e., that they have all the available options.
I agree that a documented list of these things and what they mean (some are obvious, others perhaps not) would be useful. I'm intending to read the source soon to get a handle for how autoyast actually uses this stuff to control installation.
-----Original Message----- From: Andreas Octav [mailto:Andreas.Octav@anykey.de] Sent: Wednesday, December 22, 2004 6:26 PM To: email@example.com Subject: [suse-autoinstall] NIC module confusion
I´m having some trouble autoinstalling SLES9 on a HP Proliant DL 360. The box has a Broadcom GBit NIC onboard and I want to use it with the bcm5700 module. But autoyast doesn´t seem to care about the module information i entered in the xml control file. After finishing the installation my NIC uses the tg3 module. I configured the bcm5700 module for eth0 (and eth1) in the xml control file but it does not seem to work the way it should (i think). There is a module entry in the /etc/sysconfig/network/ifcfg-ethxxx files mentioning bcm5700. Also modifying the modprobe.conf (alias eth0 bcm5700) doesn´t do the job :-(
By the way, i did not find any documentation about how to configure a finish-script when installing SLES9. Is there any information about this i overlooked? A complete list of all availlable xml tags would also be very helpful. The documentation at www.suse.com/~nashif doesn´t seem to reveal all the magic that lies in this product...
Kind regards, Andreas Octav