standalone/nofork oddity

[Denys Vlasenko]

On Friday 17 October 2008 05:54:46 pm Andreas Bühmann wrote:
> 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.)

Yes, it is supposed to work. And, unfortunately, yes,
it is not reliable enough for general use, I recommend
enabling it for rescue shells only, where you want
to have more commands to be available without
having to create symlinks.

Of course, this is a bad situation, it can be improved if more people
will start to more actively work on shell's code in busybox.

We need more developers in this area, pure and simple.

> 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...
--
vda