rules.xml and merging
Hi, at the moment our auto installation does read a non-machine specific generic xml file (via autoyast=...) and a machine specific xml file determined by the following rules.xml: <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> <![CDATA[ #!/bin/sh # Try to determine value of boot parameter "sysname" sysname=$(cat /proc/cmdline | perl -ne 'print /sysname=(\w+)/') echo -n $sysname ]]> </script> <match>machine1</match> <match_type>exact</match_type> </custom1> <result> <profile>machine1.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> Without rules.xml (i.e. with the generic xml file alone) the installation works ok. With rules.xml (and thus with the machine specific machine1.xml) autoyast2 suddenly complains about wrong partition plans though there is no partition plan in the machine specific xml file. The partition plans are only in the generic xml file. Here's the machine specific xml file: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <hostname>machine1</hostname> </dns> </networking> </configure> </profile> So the merge of the generic xml file and the machine specific xml file is somehow wrong. How can the result of the merge be checked? Where is the result of the merge stored? Regards, Stefan Voss
participants (1)
-
Voss Stefan