From: Enrique Zanardi <[EMAIL PROTECTED]>
> Memory penalty. As busybox and dinstall are linked together in this
> implementation, forking implies doubling the already big memory
> requirements.
No, sorry, that's not right. Busybox is actually much more efficient
than you think.
The text of the busybox executable is shared between all processes that are
running it, just as if it were a shared library. The data is partially
shared in that all processes inherit copy-on-write data pages after a fork().
These are kernel features that apply to all of our executables. Thus,
running multiple instances of busybox should be more economical than running
its components as separate executables.
Why did you think I linked all of those programs together? It was to save
memory.
Thanks
Bruce
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
