torvalds@transmeta.com (Linus Torvalds) said:
[...]
> Linux actually has well-defined semantics for "execve()" in a thread.
> They are very simple:
>
> - the thread executes the execve().
>
> Got it? I know it's a radical idea, but hey, it makes sense to me. I
> asked myself the question "What should execve() do inside a thread?",
> and the voices in my head told me that "It should execve() the program
> it asked for, stupid".
What about PIDs and TIDs? Can't just take over the PID of the (threaded)
parent program (which goes its merry own way), can't just keep the thread
ID (It's not a thread anymore). And a new PID goes against POSIX, isn't it?
> I always follow the voices in my head. They tend to be right, most of
> the time.
Be careful. People have been commited for believing what the voices in
their heads said. ;-)
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 21:00:21 EST