some more 110h4 clues...

[Torsten Scherer <itschere@TechFak.Uni-Bielefeld.DE>]

 To further specify my last comment:

 The child crashes when creating the basepage in load_region() in p_exec()
in dosmem.c when overlaying the parent immediately after a p_fork(). Calling
p_vfork() before seems to be ok as long as you can guarantee the text segment
or memory structures haven't been touched in between, say: There hasn't been
another program started in the meantime.

 That seems to be the reason why the first getty crashes: It was fired off
with p_vfork() and p_exec(200, "getty"), but when it finally calls login
with p_exec(200, "login") other programs have been started in the meantime.
If you try it again, you'll have a subsequent chain of non-interrupted
init:p_vfork(), init:p_exec(200, "getty"), getty: p_exec(200, "login") and
login:p_exec(200, "any-shell"), which therefore succeeds.

Am I still speaking Esperanto now? ;-)

ciao,
TeSche
-- 
Torsten Scherer (TeSche, Schiller...)
Faculty of Technology, University of Bielefeld, Germany, Europe, Earth...
| Use any of "finger itschere@129.70.131.2-15" for adresses and more.	|
| Last updated: 14. April 1994.						|