On Sat, Mar 29, 2008 at 01:59:11PM -0400, Ward Vandewege wrote:
Most likely you're missing
CONFIG_ASH_READ_TIMEOUT=y
in your busybox config. It's necessary to make the '-t' flag work for the 'read' command. If you don't have CONFIG_ASH_READ_TIMEOUT set, 'read -t' will fail with an error message, which seems to match the failure mode you describe.
Hi Ward,
thanks for your hint, but a search for CONFIG_ASH_READ_TIMEOUT gives:
...buildrom-devel$ egrep -r CONFIG_ASH_READ_TIMEOUT * deploy/config/busybox/.config:CONFIG_ASH_READ_TIMEOUT=y packages/busybox/conf/.svn/text-base/defconfig.svn-base:CONFIG_ASH_READ_TIMEOUT=y packages/busybox/conf/.svn/text-base/defconfig-serengeti_cheetah-x86_64.svn-base:CONFIG_ASH_READ_TIMEOUT=y packages/busybox/conf/defconfig-serengeti_cheetah-x86_64:CONFIG_ASH_READ_TIMEOUT=y packages/busybox/conf/defconfig:CONFIG_ASH_READ_TIMEOUT=y work/busybox/busybox-1.1.3/.config:CONFIG_ASH_READ_TIMEOUT=y work/busybox/busybox-1.1.3/include/bb_config.h:#define CONFIG_ASH_READ_TIMEOUT 1 work/busybox/busybox-1.1.3/include/config/config/ash/read/timeout.h:#define CONFIG_ASH_READ_TIMEOUT 1 work/busybox/busybox-1.1.3/shell/ash.c:#if defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/ash.c:#if defined(CONFIG_ASH_READ_NCHARS) && defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/ash.c:#elif defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/ash.c:#if defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/ash.c:#if defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/Config.in:config CONFIG_ASH_READ_TIMEOUT work/busybox/busybox-1.1.3/.config.old:CONFIG_ASH_READ_TIMEOUT=y work/busybox/logs/build.log: Enable 'read -t S' support. (CONFIG_ASH_READ_TIMEOUT) [Y/n/?] y ....
so this seems not to be the reason.
Regards,
Andi