More bbsh design notes.

[Ian Oliver]

In article <37c712e0609140223p4af8c119t2ff5c54d5c24de06 at mail.gmail.com>, 
Allan Clark wrote:
> winxksh is a shell that has a "call" function: toss the arguments onto
> a stack (strings?) and call the dlsym() of the entrypoint.  Kinda
> risky, but that basic connection has been done before in UNIX, would
> give you access to a BB variant of hton() et al, and opens up the
> shell to dlopen() all sorts of DLLs, without a whole lot of hacking.
> You could dlopen() a different DLL (of course, I mean .so) if the
> shell works out not-quite-complex-enough, but most of your coding can
> continue to be interpreted.

I must admit that I'm not even sure what problem or part thereof this is 
a solution to! No shared libraries on this box as it's uclinux on an 
Arm, and AFAIK this is still a no-go.

I was really just observing what lame stuff people can want udhcpc to do 
when a lease is acquired.

Ian