Uwe Gansert wrote
okay, I never tried something like that. I'm not so sure that this worked on
SUSE Linux 9.3 but anyway, please add:
1
in the <drive> section.
I hope I got you right, that you hava a primary partition nr. 1 that you
want to keep. If you don't have a primary partition 1 and you want to start
Well, no, this was just to demonstrate that the partition_nr is ignored :-)
with a primary partition 2, without any prim. part. 1 at all, I don't think
that's possible with autoyast but I really would be interested for what
kind of reason you need such a strange partitioning.
Indeed we used to have this for certain hosts, because we weren't
sure yet if the first partition was going to be a windows or linux
partition later, so we just left the space unused. Anyway, it does work
this way in 9.0 :-) Is it really difficult to make autoyast work this
way? I thought that's what the partition_nr parameter is for... Telling
autoyast "Shut up and do I want!" ;-))
then you can call me the partitioning wizard. Making the impossible
happen ;)
I surely will if you could also solve the other two problems for us :-)
Seriously, can you say sth. about the second and third problem? autoyast
used to auto-generate an extended partition as /dev/hda4 if only
/dev/hda1-3 and /dev/hda5 were specified. That's where the partition_nr
element helped a lot, because we generate the profiles from fstab files
by scripts, and we didn't have to think about the extended partition
ourselves, autoyast just determined it by itself.
Assuming that this was lost some time between 9.0 and 10.0 (wuah, bring
it back please :-)), what about this strange behaviour when specifying
the extended partition manually? To make sure it's not caused by the
missing first partition, I used the profile listed below. Note that
without specifying the extended partition no. 4, autoyast in SuSE 9.0
will create this (which is what we expect):
/dev/hda1 /dos fat32 defaults 4gb
/dev/hda2 swap swap defaults 1gb
/dev/hda3 / ext3 defaults 15gb
/dev/hda5 /local ext3 defaults 8gb
/dev/hda6 /home ext3 defaults 20gb
However, 10.0RC1 will create this (with defining partition 4 as
extended partition; failing without it):
/dev/hda1 /dos fat32 defaults 4gb
/dev/hda2 swap swap defaults 1gb
/dev/hda3 <extended>
/dev/hda5 / ext3 defaults 15gb
/dev/hda6
/dev/hda7 /local ext3 defaults 8gb
/dev/hda8 /home ext3 defaults 20gb
This can't make any sense... I specify an extended partition for no. 4,
but /dev/hda4 is not created at all, but therefore /dev/hda3 becomes
an extended partition, although I specified /dev/hda3 with mountpoint "/",
/dev/hda6 is created but not used at all,...
"Wizard, wizard, make it work!" ;-)
I feel the partition_nr element should have more weight like a
"force it to be /dev/hda if the user tells me, how
stupid this may look to me..." and should never be overridden by
autoyast's own decision.
Oh, btw, talking about old features: autoyast1 (SuSE 6.4) used to
have this feature "If I find an fstab, I reuse it and leave all
partitions untouched, unless I'm told to format some". This
fstab-feature was missing in 9.0 completely and came back in 9.1,
but now with the contrary behaviour: "format all partitions unless
I'm told to leave some untouched". This is somewhat dangerous because
you will accidentally format partitions if you forget to specify
them. Couldn't this be changed so that one can chose if the default
behaviour is either format-all or format-none?
cu,
Frank
<partitioning config:type="list">
<drive>
<device>/dev/hda</device>
<partitions config:type="list">
<partition>
<create config:type="boolean">false</create>
<filesystem config:type="symbol">fat32</filesystem>
<format config:type="boolean">false</format>
<fstopt>defaults</fstopt>
<mount>/dos</mount>
1
<size>4gb</size>
</partition>
<partition>
<create config:type="boolean">true</create>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
<fstopt>defaults</fstopt>
<mount>swap</mount>
2
<size>1gb</size>
</partition>
<partition>
<create config:type="boolean">true</create>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
<fstopt>defaults</fstopt>
<mount>/</mount>
3
<size>15gb</size>
</partition>
<partition>
<create config:type="boolean">true</create>
4
5
<size>max</size>
</partition>
<partition>
<create config:type="boolean">true</create>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
<fstopt>defaults</fstopt>
<mount>/local</mount>
5
<size>8gb</size>
</partition>
<partition>
<create config:type="boolean">true</create>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
<fstopt>defaults</fstopt>
<mount>/home</mount>
6
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
--
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. *