On Wed, 12 Jun 2002, Volkmar Glauche wrote:
I did not observe a wrong partition order, Ok, the wrong order was a result of my forcing lvm to be a primary partition, but / and /boot not.
but for my setup yast did not succeed in creating a file system on my logical volume (same configuration same for me. If I change to a console while running the setup I observe that there is no active vg. pvscan shows, that the partition is a pv. vgscan shows, that there are no active vg. But I can see /dev/system/group (I can remove /dev/system and recreate a vg system. After that the installation will continue)
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. I wish you could have classes (or templates) which you could easily combine not only in the yast2-config-tool. (which is awful to use if you have to run it in textmode)
The classes should not only be reserved for normal config, but also
for software-selections.
Btw. Why is it that attribute-type entries are saved as tag-entries
in the xml format. like