Red Hat Bugzilla – Bug 232529
In anaconda kickstart environment, printf does not pad output correctly
Last modified: 2007-11-16 20:14:55 EST
Description of problem: When installing (kickstart), the following command issues the wrong output: # printf "%02" 11 B It should return "0B" but it appears that padding doesn't work. This is only within the installation environment (EG %pre).
The printf being used in %pre scripts is the busybox printf, while one being used on the running system or in %post scripts is the real GNU one.
I'm not sure I know what is the problem - I just test the command /sbin/busybox.anaconda printf "%02X" 11 with busybox-anaconda-1.2.0-3 and the result is right "0B". Please what version of busybox do you have?
I'm sorry I mess the version number. In rhel4 version of busybox there is not implemented printf command.
Darren - A quick test here showed that it works fine for me. Could you please post your complete kickstart file so I can try a better test? You can delete passwords and other sensitive information, of course.
Created attachment 153226 [details] Example kickstart
I'm still unable to reproduce this problem with RHEL4u4. Can you think of any additional information that might help to diagnose what's going on?
I don't use this functionality in my kickstarts any more after I ran into this problem (I use a cgi to handle kickstart templating for %pre/%post scripts now). Testing in vmware with U3 and U4 under VMware, and I don't have a free box to PXE boot for testing this. My apologies since I can't reproduce the problem.
Closing this bug as WORKSFORME since I was unable to reproduce the problem and hardware is no longer available for testing. If you are able to reproduce it again at a later date, feel free to reopen this bug report. Thanks for your time.