Hi,
Tony Wyatt wrote:
Do we really need the "fork()"
functionality? Surely we don't need to
duplicate the entire volatile memory of the current shell in order to
run another - all we need to do is "run" another shell with the same
Env and local variables, right? We could send the daughter shell a
message containing the current variable settings.
What if the shell uses internal data structure to store state ?
Surely the use of "fork()" is an
overkill for a shell?
No, absoultely not. In fact, shells are one of two cases where fork is
actually not absolutely horrendously braindead (the other is demon
processes).
Personally, I prefer pthreads for daemon processes. But for shells...
Yeah, fork works there.
--
We'll jump off that bridge when we get there.