you can write "scripts" and
run them in sash, but it does not support input/output redirection nor
parameters, which limits their usefulness significantly.
OK I do understand now.
I usually use busybox msh, since that does support all of that, but it has
less integrated commands so you need more in your bindir. But yes, those
can also be busybox commands if you like.
OK, as with my project, I am not tight with RAM or flash resources thus
I can use msh.
Is sash a (or the only) shell that does not need link files (and thus
reloading of the "busybox" executable) when calling a command ?
What it does have going for it is simplified
functionality of a lot of bintools built directly into it, so they're
internal commands rather than external ones.
I see. "Internal commands" is why there are no symlinks for the commands
and that is why no executable needs to be loaded (which is beneficial
with those non-MMU architectures that can't share code pages between
multiple "loaded" processes).
Bash requires an MMU, last time I checked (because it requires full glibc,
which requires an MMU). And again it's unrelated to busybox.
I see, Thus supposedly msh is the way to go :)
Now finally back to the original question: can you explain what is
required to activate DHCP ?
Thanks a lot
-Michael
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
