My partitioning section is directly AFTER </general> . I have been told that the order shall not matter but who knows. So give it a try. If the order change will help then there is no need for a rules.xml At least at my site i have no problems with SATA and IDE drive. About SCSI i can not tell. If you need a rules.xml 1) Get the documentation about autoyast ( Mentioned in a previous post to this list by me ) 2) Below your autoinstallation source directory ( Example: MyServer:/export/suse/autoinstall/ ) create the following subdirectories: ./rules ( Will hold only the rules.xml ) ./classes ( Will hold the autoinstall.xml and sda.xml and hda.xml ) A few importent hints: A) The autoyast entry MUST end with an "/" . Example: autoyast=nfs://MyServer:/export/suse/autoinstall/ otherwise the rules.cml will NOT be parsed. B) The rules.xml MUST include a rule to include your standard "installation.xml" because it will be parsed only what has a MATCH in the rules.xml C) You must use " echo -n" in your script section to get rid of the NEWLINE. Otherwise the match will not work. The following is an example of a "rules.xml" to determine the disk type <?xml version="1.0"?> <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[ if grep hda /proc/partitions > /dev/null; then echo -n "hda" else echo -n "sda" fi; ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/@custom1@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/autoinst.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> ---------------------------------------------------------- The first rule will parse your ( sda.xml or hda.xml ) and continue to the next rule The second rule will match everything so it does include the classes/autoinst.xml File. Now further rules will be parsed afterwards. The sda.xml is just a stript down version from your autoinst.xml containing a Section like down below ( NOT tested ) . For the hda.xml you must just change the device section. To get these Section i would use "yast2 autoyast " and create a new xml file where only the paritioning section has been configured with yast2. Afterwards take everthing out of the file what is not related to the partitioning . Run "xmllint" to verify the file and you should be happy. <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <install> <partitioning config:type="list"> <device>/dev/sda</device> <drive> <use>all</use> </drive> </partitioning> </install> </profile> hth Hajo

...

...

GrueMaster <gruemaster@yahoo.com> 08/26/05 5:49 pm >>> I fixed the boot loader section, but that isn't where the problem is. Yast fails at "Create partition plans".

Hey, I think I figured it out (somewhat). I added <device>/dev/sda</device> to the partitioning section and it now blows past that and installs. Now I need to figure out how to use rules, as we have IDE, SCSI, and SATA systems. SATA and SCSI will work with this config, but IDE needs /dev/hda. Any suggestions?