Greetings, I presently have an autoyast set up to deliver Novell OES1 (SLES9 i386 based). I wish to build some servers with just the SLES9 x64 distribution and was hoping to use the same rules.xml file to kick things off. Here is the rules.xml that is presently working for OES1: <?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> <product> <match>*</match> <match_type>exact</match_type> </product> <result> <profile>profiles/templates/base.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <mac> <match>*</match> <match_type>exact</match_type> </mac> <result> <profile>profiles/mac/@mac@/eth0.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <script> <![CDATA[ #!/bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin if [ -n "`grep build= /proc/cmdline`" ] then echo -n `cat /proc/cmdline | sed -e 's/.*build=\(.*\)/\1/' -e 's/^\(.*\) BOOT.*/\1/'` else echo -n "hse9-32" fi ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>profiles/software/@custom1@.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> The SLES9 x64 autoyast attempts using the same rules.xml file but seems to not match any of the rules and prompts for the location of a proper rules file. On inspecting the /var/log/YaST2/y2log file, it appears that the bit of shell scripting being kicked off to compare the product/mac strings to the * character are failing and returning 1 instead of 0 as they do with the OES1 installation. ie the scripts are treating the wildcard (*) character literally. Does the SLES9 x64 autoyast support the use of wildcards in the match? If not, what can I use instead Thanks for any help...