| very simple partitioning | [click] |
| encrypted /tmp partition | [click] |
| resize a partition | [click] |
| LVM | [click] |
| encrypted LVM | [click] |
| RAID | [click] |
| LVM on RAID | [click] |
| complex LVM on RAID | [click] |
| root on NFS (since openSUSE 11.4) | [click] |
The rules.xml will merge the main profile (autoinst.xml) with two XML files containing partitioning information.
part1.xml and part2.xml will get merged into the empty partitioning section of autoinst.xml.
Because of the "dont_merge" settings in the rules.xml file, we will end up with 4 partitions. If you remove
the dont_merge sections from the rules.xml file, you'll get two partitions that are a mix of part1.xml and part2.xml.
The <ask> option in the profile lets you do some decissions during the autoinstallation. For example you can set the
root password by an ask-dialog instead of using a pre defined password in the profile.
Since 10.3 you can even run scripts, which makes it possible to choose an autoyast profile via ask-dialog. Sounds weird?
The trick is to refetch another profile with a first profile that only contains an ask-section and store the new profile
as modified.xml, so autoyast will reread it.
here it is
Example for static network interface config
Example for dhcp network interface config with a udev rule
Keep networking config from the installation
Use ask-dialogs to ask for network settings, incl. checks for sanity
Example for a slp.reg when you use autoyast=slp