Hello, are FEATURE_SH_STANDALONE and FEATURE_SH_NOFORK supposed to work correctly together? (I understand what NOFORK/NOEXEC applets are in general, but there is little information on the scope or conceptual overlap of these two config options.)
If a standard busybox is configured like this, strange things start to happen. CONFIG_FEATURE_PREFER_APPLETS=y CONFIG_FEATURE_SH_STANDALONE=y CONFIG_FEATURE_SH_NOFORK=y # ./busybox ash $ echo | hexdump 0000000 000a 0000001 $ rm -f foo $ echo | hexdump hexdump: invalid option -- u BusyBox v1.13.0.svn (2008-10-16 18:26:41 CEST) multi-call binary Usage: hexdump [-bcCdefnosvx] FILE... Regards, Andreas _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
