Thanks for the rules help. I've been studying the online documentation and was very confused about the directory structure needed for the rules.xml. Your rules.xml example worked flawlessly. I'd recommend adding your example as it is written to the documentation. I've now progressed to getting the system imaged and booting (Whoo Hoo!) Now to get my post install script running again (I yanked it to simplify debugging the partitioning issues). Next question, is there a setting to allow installing without the "Licensing" prompt, or does the timeout automaticly assume acceptance? Tobin Hans-Joachim Ehlers wrote: My partitioning section is directly AFTER . 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 xmlns:config="http://www.suse.com/1.0/configns"> if grep hda /proc/partitions > /dev/null; then echo -n "hda" else echo -n "sda" fi; ]]> * exact classes/@custom1@.xml true * exact classes/autoinst.xml false ---------------------------------------------------------- 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. xmlns:config="http://www.suse.com/1.0/configns"> /dev/sda all hth Hajo

...

...

GrueMaster 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 /dev/sda 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? --------------------------------- Start your day with Yahoo! - make it your home page