Anaconda vs YaST -- install on mdadm RAID volumes

Recently i had a possibility to compare both.
One of my clients depends on RHEL, so I installed CentOS 5.2 for them. There were usual 2xquad-core-Xeon servers, with a cheap SATA controller, so the only option for me was creating mdadm RAID volumes. Another of my clients had similar server, but they had no preferences, so i installed OpenSuSE 11.1 there.

both installers (i mean, both YaST and Anaconda) could not present me GUI to allow me to do things that i wanted to. But, frankly speaking, YaST allows more fine tuning of RAID volumes being created. For example, in YaST i could manually specify size of chunk. However, YaST did not allow me to create RAID10 volume. I did the following: I rebooted from OpenSuSE 11.1 install disk in rescue mode, and made myself a needed configuration with sfdisk and mdadm commands. Then i rebooted into installer, YaST found all volumes that i created, and pointed which filesystems to create there, and was successfull. In Anaconda, i could not do such a trick. For some reason, it did not allow me to use existing RAID volumes. I always resulted in "/dev/sdd4 device or resource busy" error. The only option that helped was:
deleting whole partition table with parted mklabel command, and then re-create them in installer.

Another feature that made me a complete YaST zealot is possibility to create YaST modules myself. Once upon a time i used it to fix user management routines on LDAP+KOLAB+SAMBA PDC machine. I cant imagine a good way to do it for Anaconda.

as a result: Anaconda sucks!