Hi Uwe, Yes, this is much more interesting! Thank you for answer! Seems like exactly what I need :) I may describe, why rules are not suitable. Only one reason - because these need directory structure for work, and fixed filename. I use automatic OS provisioning system, which generates configuration file (from template) and uses parameters from database - like NIS server, Install path, packages, etc. So, the only thing I passing to SuSE installer kernel is "autoyast=http://.../gettemplate.cgi install="nfs://..." This script generates RH KickStart, Debian, FreeBSD or autoYast - whatever you want - configuration file automatically - depending on which OS should be deployed. This is why it's not possible to use directory structure for making rules.xml and related fles. BTW, I can use XInclude to get more files from same generator, but some options about system configuration need to be passed back to it, to generate correct content. Hope, that way, you proposed, will work :) Really, nice to see it more "oficially" documented, or see some way to force second pass of processing XML control file after pre-scripts. Can I just add XInclude to /tmp/profile/modified.xml ? Will it be processes again? Or I should add already prepared XML code? BTW - will see it in next hour ;) Thanks a lot! -- Regards, Alexander Dubinin