Hi out there Q1: I have tried numerous setups for trying to get the right setup in the control file for the following setup. Currently trying on SLES8 s390x SP3. /dev/dasda1 mountet on / with reiserfs. It should use all diskspace available. /dev/dasdb1 mountet on /boot with ext2. It should use all diskspace. /dev/dasdc1 swap For some reason it always creates a second partition on each drive. Is it possible to solve this this? The following section from the control file is just the latest example of what I have tried. <partitioning config:type="list"> <drive> <device>/dev/dasdc</device> <partitions config:type="list"> <partition> <mount>swap</mount> <partition_nr config:type="integer">1</partition_nr> <create config:type="boolean">false</create> </partition> </partitions> </drive> <drive> <device>/dev/dasdb</device> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <filesystem config:type="symbol">ext2</filesystem> <mount>/boot</mount> <format config:type="boolean">true</format> <size>34mb</size> </partition> </partitions> </drive> <drive> <device>/dev/dasda</device> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <size>6800mb</size> </partition> </partitions> </drive> </partitioning> Q2: Is it possible to run yast unattended during installation? I currently always accepts a few times. Example, after load off dasd module? I am using the SSH network installation method. The part of installation in z/VM now works unattended, so it would be nice that the part in SSH install also was unattended. Regards Steen Bank Johnsen JN DATA A/S