Path: ...!weretis.net!feeder9.news.weretis.net!xmission!nnrp.xmission!.POSTED.shell.xmission.com!not-for-mail From: gazelle@shell.xmission.com (Kenny McCormack) Newsgroups: comp.unix.shell Subject: Re: [OT] PIDs for Linux threads (was Re: pid ranges) Date: Mon, 7 Oct 2024 16:41:49 -0000 (UTC) Organization: The official candy of the new Millennium Message-ID: References: Injection-Date: Mon, 7 Oct 2024 16:41:49 -0000 (UTC) Injection-Info: news.xmission.com; posting-host="shell.xmission.com:166.70.8.4"; logging-data="3079136"; mail-complaints-to="abuse@xmission.com" X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Originator: gazelle@shell.xmission.com (Kenny McCormack) Bytes: 1887 Lines: 26 In article , Janis Papanagnou wrote: >[ This is getting off-topic, sorry. ] > >On 07.10.2024 15:31, Richard Kettlewell wrote: >> >> _On Linux_ process IDs and thread IDs share the same number space which >> changes the picture quite a bit: [...] > >This is interesting. >Since processes are handled by the OS kernel what does that imply...? >A common process/thread interface in Linux? >Is that defined by POSIX threads, or is it something specific? > >Is there any good link to read more about that? "man clone" is a good starting place. In Linux, threads are almost the same thing as processes. Obviously, there are differences, but basically, that is true. Both are created via clone(2). (fork() is implemented on top of clone()). -- > No, I haven't, that's why I'm asking questions. If you won't help me, > why don't you just go find your lost manhood elsewhere. CLC in a nutshell.