[Info-vax] Anyone interested in another public access system

[yyyc186]

On Apr 6, 4:08 pm, "Bob Eager" <rd... at spamcop.net> wrote:
>
> If you're going to conduct a hate campaign, at least be accurate. Please
> explain why UNIX processes are not processes. They have their own locus
> of execution, their own virtual memory, their own context.
>

They aren't processes, they are threads.  Processes have birth
certificates, death certificates and  unique IDs no matter what OS you
are talking about.  The registrar assigns the ID while recording the
genetic lineage of the process.  The registrar also periodically
checks for the continued existence of the process once it has been
created.  It handles the cases of untimely death which occurred
without notification.

Threads are not required to have these.  When you dig into the tales
of trouble shooting dangling threads you will find that these missing
requirements are exactly what causes dangling threads to happen in the
first place.  A PID can have a massive number of threads.  A thread
can exist without a PID (on most flavors).

fork() really does fork() while lib$spawn() routes through the
registrars office.