Hi -- I'm working on setting up an autoinstall infrastructure that will be used to convert around 750 machines from a customized Slackware distribution to SLES9SP3. Obviously, automation of as much as possible is key. We'd also like to borrow a page from the ROCKS folks and make re-installs as painless as possible, because it's something that comes up in our environment a fair bit. The general idea is to have two "standard" partitions, / and /var, on /dev/md0 (sd[ab]1) and /dev/md1 (sd[ab]2), respectively, and then have some more specific RAID partitions on the remaining parts of the disk (with different sorts of machines having different sorts of partitioning schemes). During an initial install (which can be assumed to mean "an install onto disks that don't have a partition table yet"), all of these partitions would need to be created and initialized, the RAIDs set up, and the filesystems created. During a reinstall, we would only want to reformat '/' and '/var' -- any other partitions/RAID devices/filesystems should be left alone. The /etc/fstab file will be managed with our configuration management system, so having that maintained properly across reinstalls isn't a concern -- as long as the reinstall can get to the point where it will boot and mount / and /var, everything will converge to the desired state once the tool runs. The goal is to do this with only a single install.xml config file. It's not clear from the AutoYaST PDF whether or not this is possible -- can anybody here shed some light on whether this particular windmill is a good tilting target or not? thanks, john. -- It's easy to get the *wrong* answer in O(1) time. Mark Jason Dominus's Good Advice #11963