dynamic partitioning
Does anyone know how to create dynamic on-the-fly partitioning? (on SuSE Linux Professional 9.1) I have a heterogenous machine park with disk layout ranging from 1 to 4 disks and various requirements, i.e. raid on some, LVM on some, raid and LVM on some. I would like to create the partitioning scheme as part of the (lovely) automated installation process using autoyast. However, I've played around with the rules mechanism and as far as I can see, there's gonna be a lot of extra coding to cover every possible scenario as opposed to creating the partitioning on-the-fly. Also, does anyone have the XML XInclude feature working on SuSE Pro 9.1? I've tried and I just can't get it to work for me. Any hints? R -- stava@jonitec.se
On Thursday 12 August 2004 20:04, Lars Stavholm wrote:
Also, does anyone have the XML XInclude feature working on SuSE Pro 9.1? I've tried and I just can't get it to work for me.
Here is a stripped down file that worked for me. Also note: If you load this
in the 'yast autoyast' module, then the file to be included actually will be
included by YaST *upon opening* of the file. You probably will discover that.
----8<----8<----
<?xml version="1.0"?>
<!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns"
xmlns:xinclude="http://www.w3.org/2001/XInclude">
<configure>
<scripts>
<post-scripts config:type="list">
Lars Stavholm wrote:
Does anyone know how to create dynamic on-the-fly partitioning?
(on SuSE Linux Professional 9.1)
I have a heterogenous machine park with disk layout ranging from 1 to 4 disks and various requirements, i.e. raid on some, LVM on some, raid and LVM on some. I would like to create the partitioning scheme as part of the (lovely) automated installation process using autoyast. However, I've played around with the rules mechanism and as far as I can see, there's gonna be a lot of extra coding to cover every possible scenario as opposed to creating the partitioning on-the-fly.
Maybe using a custom script in the rules might work. Use a shell script to figure out what machine you are on (using fdisk, /proc etc.) and return e.g. an integer. Dependant on the return value you could then choose a profile in rules.xml that matches the partition behaviour. 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. *
participants (3)
-
Frank Steiner -
Lars Stavholm -
Leendert Meyer