You can use classes, so that your software config is abstracted out of the main file, into
a common "software only"
Or you can use rules to detect the hardware and include different HD configurations
depending on what system spec it
If disk sizes aren't vastly different, you could specify one partition as size MAX so
that it takes all available
And don't forget you don't have to specify which HD device is the first disk
(i.e. the target of the partitioning).
YaST will by default pick up the first one it finds if you don't specify a device.
You only really need to specify in the autoyast profile anything that you want that
isn't default. I've never tried to
get the profile down to bare minimum, but I'd have though that package selection and
partitioning would be enough.
>> On 28/02/2006 at 17:34, in message
I'm wondering if an autoyast.xml file could be
used solely for
designating software packages to be installed. In other words, for a
minimal server install, I want the same packages installed on those
servers regardless of the hardware present (one may be a Proliant
server and another an Optiplex). But I *do* want packages X, Y, and Z
installed on both. Is this possible?
Partitioning wouldn't appear to work because the disk sizes might be
different in the machines, but I want to update the process a much as