I believe putting a '\' infront of each '?' should do it.
if that doesn't, can you include the file you want in the kickstart file using the %include statement in the kickstart file ? PM shouldn't parse the additional file.
I'm not sure that \ is enough to escape it. The problem is in our %post section we issue commands configure various aspects of the system. There are a bunch of commands which contain ? in them. One which can't be esacped using \ is where we check a return code, by setting a variable to be the value of $?. If I escape that I just set the variable to be equal to '$?' literal.
Cheers - Lee
ah.. hmm - so try using the %include and include the %post section as a separate file. it would be like:
then in kickstart-post.cfg put your post section w/ the ? issues.
Since I am experiencing issues related to the way BMI does it's parsing, it seems to me that the best solution would be for PM to only check for propertys with the exact correct syntax (e.g. ??property_name??) and leave the rest up to the kickstart file author(eg ret=$?). We can find syntax errors if we introduce them, PM should just look for the one syntax it recognizes(??property_name??) and leave the rest as is.