Hi, I'm installing SLES 9 on IBM pSeries (power4 cpus). I first installed it manually and grepped the xml files from cloning the machine to build a general installation. Two proplems arise: 1) That's what cloning the machine and saving the profile gives me for the bootloader: <bootloader> <activate config:type="boolean">true</activate> <board_type>chrp</board_type> <default>linux</default> <loader_device>/dev/sda1</loader_device> <loader_type>ppc</loader_type> <location>custom</location> <of_defaultdevice config:type="boolean">true</of_defaultdevice> <prep_boot_partition>/dev/sda1</prep_boot_partition> </bootloader> However, checking the file with nsgml and the dtd files from the autoyast2-installation.rpm tells me: nsgmls:profiles/part_hal_keep.xml:7:28:E: there is no attribute "config:type" nsgmls:profiles/part_hal_keep.xml:7:37:E: element "activate" undefined nsgmls:profiles/part_hal_keep.xml:8:17:E: element "board_type" undefined nsgmls:profiles/part_hal_keep.xml:9:14:E: document type does not allow element "default" here nsgmls:profiles/part_hal_keep.xml:13:36:E: there is no attribute "config:type" nsgmls:profiles/part_hal_keep.xml:13:45:E: element "of_defaultdevice" undefined nsgmls:profiles/part_hal_keep.xml:14:26:E: element "prep_boot_partition" undefined I ignore it because the xml file works for installing further machines, but I guess the dtd files should be corrected. 2) For checking the profiles while writing them, I copied the dtd files to a path relative to my profiles. My autoyast dir that I pass to autoyast has the structure rules/ profiles/ dtd/ where rules/ contains rules.xml. All my manually written profiles as well as the rules.xml start with <!DOCTYPE profile SYSTEM "../dtd/profile.dtd"> which works well when I check my files with nsgml. For installing, I use a rules.xml with: <rule> <arch> <match>ppc64</match> <match_type>exact</match_type> </arch> <result> <profile>profiles/lmuppc.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <hostaddress> <match>141.84.1.134</match> <match_type>exact</match_type> </hostaddress> <result> <profile>profiles/part_hal_keep.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> where both of the profiles containt the "../dtd.." stuff. When I run the installation with this rules.xml, I get an error message /tmp/YaST2-.../rules/profiles/lmuppc.xml:2: warning: failed to load external entity "/tmp/YaST2-.../rules/dtd/profile.dtd" <!DOCTYPE profile SYSTEM "../dtd/profile.dtd"> Likely, the dtd file were not copied over to the /tmp/YaST2-.../rules/ dir. But, this error does not occur if I put the contents of part_hal_keep.xml into lmuppc.xml and work with only one profile in rules.xml! Then the whole installation runs through. Thus, only when using more than one profile in rules.xml, it fails. Any thoughts? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *