On Wed, 12 Jun 2002, Volkmar Glauche wrote:
I did not observe a wrong partition order, but for my setup yast did not
succeed in creating a file system on my logical volume (same configuration
as posted yesterday, but with previously missing <lv> </lv>-tags). The
mke2fs command stalled at 0% formatting for about 20 minutes (and ps/top
did not show any process time spent on mke2fs). No error messages and no
warnings occured during this time. I killed the process and
formatting of the other partitions went okay.
It seems, that yast2 does create the VolumeGroup, but does not attempt to
create the Logical volume in it.
The lvm section now looks like this:
<lvm config:type="list">
HomeVol
<pesize>4M</pesize>
<lv>
LHomeVol
28800mb
ext3
/export/home
</lv>
</lvm>
In addition, the -tag works for
creating the lilo.conf. However, they are also added for the "failsafe"
entry. I don't know if this should be the case by default or if it would
be a better idea to leave the failsafe parameters "as is" - because if I
would accidentally specify wrong parameters then also failsafe would not
boot.
Generally, it would be a good idea to have ALL standard decisions made by
yast driven by a config file (something like template.xml). This would
allow
- inspection of standard decisions
- change of standard behaviour without undocumented side-effects
For partitioning, the option to specify a more detailed partitioning plan
(ie assigning custom partition numbers) would be nice.
Yours,
Volkmar
--
Volkmar Glauche
Department of Neurology E-Mail glauche@uke.uni-hamburg.de
UKE Hamburg WWW http://glauche.home.pages.de/
Martinistr. 52 Phone 49(0)40-42803-5781
20246 Hamburg Fax 49(0)40-42803-9955