See patch for genkernel: http://pastie.org/2293085 printf is called here: $ grep -n printf genkernel-3.4.18/defaults/initrd.scripts 662: printf "%b\n" "${lvm_commands}" | /bin/lvm /proc/self/fd/0 printf behaves correctly in busybox-1.18.4 but both busybox 1.7.4 and 1.18.4 behaves the same when adding the space in front of \n Reproducible: Always Steps to Reproduce: 1. create initrd 2. boot Actual Results: 1. printf: not found 2. No such command. Try 'help'. Expected Results: boot
Created attachment 281633 [details, diff] Eduardo's patch proposal A paste site is no good place to point to from a bug tracker as it may go away anytime. So I'm re-adding your patch as an attachment.
An alternative to the workaround (adding a space) we could also deny working with any broken version from genkernel. If this http://git.busybox.net/busybox/commit/coreutils/printf.c?id=a48656b441224a53d2bb3face920ba5487eaae09 is the fixing commit that would probably be anything before busybox 1.12.0. I don't really like either approach as of the moment. Any other routes we could take? Xake/Peter?
@genkernel team Please check comment #2.
I was using the genkernel.conf from 3.4.16 which was pulling in busybox-1.7.4. The printf bug shouldn't be an issue anymore on busybox-1.18.1. It looks like newer genkernel still use the 1.7.4 busybox-config. I can't reboot anytime soon to check if 1.18.1 really needs CONFIG_PRINTF=y Sorry for the trouble.
Ah yes genkernel-3.4.16 is currently stable. Might need to bump that to a newer version that picks up a newer busybox version.
my bad ignore comment #5 genkernel-3.4.10.908 was the last version to use 1.7.4
Argh sorry guys. Looks like a non-issue: ... bin # ./busybox ash BusyBox v1.18.1 (2011-07-31 10:44:48 UTC) built-in shell (ash) Enter 'help' for a list of built-in commands. # printf ash: usage: printf FORMAT [ARGUMENT...] ...
I took the occasion to end support for busybox 1.7.4 in genkernel: http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commitdiff;h=7296be47b869ef3d86b1a1b6622092a925ae0faf Without the patches, busybox 1.7.4 will not compile anyway.
