Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!vsi1!altos86!dtynan
From: bahman@nixtor (Bahman Koohestani)
Newsgroups: comp.unix
Subject: Re: QNX
Message-ID: <3505@altos86.Altos.COM>
Date: 10 Jul 89 21:48:38 GMT
References: <1046@altos86.UUCP> <1096@altos86.UUCP> <1226@altos86.UUCP> <3482@altos86.Altos.COM>
Sender: dtynan@altos86.Altos.COM
Reply-To: uunet!nixtor!bahman (Bahman Koohestani)
Organization: Nixdorf Computer Canada Ltd.
Lines: 13
Approved: dtynan@zorba.Tynan.COM


>QNX has a fork call and it works very efficiently.....

Yes, QNX does have a fork call; it also works very "efficiently", however,
it is brain damaged. Why???? Because it is nothing like the unix fork() call.
It does not let you pass file descriptors or file pointers to the son task. All
it does is that it allows you to create a son task and then you must re-open]
any files that you would have expected to inherit from the parent task.
QNX is a good system for real time (process control) applications, it is
not as open as unix is in a lot of different ways. fork () also has a lot
of other side effects (depending on the version of QNX you are working with).
At one point, one could not create a background task from another background
task..... SO WHAT?