RE: [suse-autoinstall] Problems with <use> and <partition_type>
Hi,
I found that if I made my partitions sections look like the following, it
would grab the first disk (be it /dev/sda or /dev/hda) and autopartition it.
See if it works for you:
<partitioning config:type="list">
<drive>
<use>all</use>
</drive>
</partitioning>
Christopher R. Slater
ITO Specialist
MSDD/SSO
Hewlett Packard Company, Roseville Site
(916) tn785-1802
http://ecardfile.com/id/chris_slater
-----Original Message-----
From: Fermín Galán [mailto:fermin.galan@agora-2000.com]
Sent: Friday, October 03, 2003 5:37 AM
To: suse-autoinstall@suse.com
Subject: [suse-autoinstall] Problems with <use> and
I found that if I made my partitions sections look like the following, it would grab the first disk (be it /dev/sda or /dev/hda) and autopartition it. See if it works for you:
<partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning>
This solution destroys all partitions, but I only want to delete /dev/hda1 and preserve the others. For example, if I have: /dev/hda1 whatever /dev/hda5 data /dev/hda6 more data I want to get after installation: /dev/hda1 boot /dev/hda2 swap /dev/hda3 root partition /dev/hda5 data (preserved) /dev/hda6 more data (preserved) But your example leads to: /dev/hda5 boot /dev/hda6 swap /dev/hda7 more data -------- Fermín
Fermín Galán wrote:
I found that if I made my partitions sections look like the following, it would grab the first disk (be it /dev/sda or /dev/hda) and autopartition it. See if it works for you:
<partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning>
This solution destroys all partitions, but I only want to delete /dev/hda1 and preserve the others. For example, if I have:
/dev/hda1 whatever /dev/hda5 data /dev/hda6 more data
I want to get after installation:
/dev/hda1 boot /dev/hda2 swap /dev/hda3 root partition /dev/hda5 data (preserved) /dev/hda6 more data (preserved)
This will never work for the simple reason that the extended partition has to be destroyed in order to be able to add additional primary partitions.
But your example leads to:
/dev/hda5 boot /dev/hda6 swap /dev/hda7 more data
Manipulating partitions at the beginning of the device is still not supported unfortunatly. You can only manipulate partitions at the end. Anas
-------- Fermín
Manipulating partitions at the beginning of the device is still not supported unfortunatly. You can only manipulate partitions at the end.
What do you exactly mean with *manipulate partitions*? Only to create partitions or also to format already created partitions? Is possible to have the partition plan already done (not only desired partitions created, but also formatted) before run autoinstaller and just tell in the XML the target partitions for the installation (the autoinstaller wouldn't need to manipulate anything, just install)? ------ Fermín
Fermín Galán wrote:
I found that if I made my partitions sections look like the following, it would grab the first disk (be it /dev/sda or /dev/hda) and autopartition it. See if it works for you:
<partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning>
This solution destroys all partitions, but I only want to delete /dev/hda1 and preserve the others. For example, if I have:
/dev/hda1 whatever /dev/hda5 data /dev/hda6 more data
I want to get after installation:
/dev/hda1 boot /dev/hda2 swap /dev/hda3 root partition /dev/hda5 data (preserved) /dev/hda6 more data (preserved)
This will never work for the simple reason that the extended partition has to be destroyed in order to be able to add additional primary partitions.
But your example leads to:
/dev/hda5 boot /dev/hda6 swap /dev/hda7 more data
Manipulating partitions at the beginning of the device is still not supported unfortunatly. You can only manipulate partitions at the end. Anas
-------- Fermín
participants (3)
-
Anas Nashif -
Fermín Galán -
SLATER,CHRIS (HP-Roseville,ex1)