Hi, I already have working xml files (for SuSE 9.3) that installs ok for two types of machines: - machines with one disk: partitioning consists of a small /boot partition and a big LVM type partition containing logical volumes for /, swap, /usr, etc. - machines with two disks: partioning of these disks each consists of a small raid type partition and a big raid type partition. A RAID1 device is created from the two small partitions which holds /boot and another RAID1 device is created from the two big partions to hold an LVM volume group with logical volumes for /, swap, /usr, etc. Apart from the partitioning the machine setups are the same. I want to consolidate these files into the following: - one_disk.xml: Contains partitioning for 1-disk machines - two_disk.xml: Contains partitioning for 2-disk machines - common.xml: Contains everything else including LVM configuration. So a machine with one disk would be the merge of one_disk.xml + common.xml and a machine with two disks would be the merge of two_disk.xml + common.xml. I tried using rules but ran into problems because the LVM configuration is done inside <partitioning> section. A volume group is defined as another <drive> inside the <partitioning> section. When e.g. one_disk.xml and common.xml are selected via rules the merge produces a result that autoyast cannot understand. Merging works best if the files to merge don't intersect like in the rules example by Frank Steiner (http://www.bio.ifi.lmu.de/~steiner/ayex.tgz ). In Frank's example lmu.xml contains <profile> -> <configure> sections, lilo-i386.xml contains <profile> -> <install> -> <bootloader> sections and part_zassenhaus_keep.xml contains <profile> -> <install> -> <partitioning> sections. Merging them produces a valid autoyast xml file. Does somebody have a working classes example? Is merging classes different to merging profiles? Gruss, Stefan Voss -- Stefan Voss