From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: MAX_PID changes in 2.5.31
Date: 20 Aug 2002 00:29:11 +0100 [thread overview]
Message-ID: <1029799751.21212.0.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0208200033400.5253-100000@localhost.localdomain>
On Mon, 2002-08-19 at 23:34, Ingo Molnar wrote:
>
> On Mon, 19 Aug 2002, Richard Gooch wrote:
>
> > Are you saying that people running libc 5 or even glibc 2.1 will
> > suddenly have their code broken?
>
> nope. Only if they use the 16-bit PID stuff in SysV IPC semaphores and
> message queues.
libc5 is very much 16bit pid throughout. It would make sense that our
default (proc settable) pid max is 30000 still so that it only breaks
stuff if you increase it
next prev parent reply other threads:[~2002-08-19 23:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 19:55 Ingo Molnar
2002-08-19 20:06 ` Linus Torvalds
2002-08-19 20:33 ` Ingo Molnar
2002-08-19 22:31 ` Richard Gooch
2002-08-19 22:34 ` Ingo Molnar
2002-08-19 22:36 ` Richard Gooch
2002-08-19 22:41 ` Robert Love
2002-08-19 22:44 ` Ingo Molnar
2002-08-19 22:47 ` Richard Gooch
2002-08-19 23:01 ` Ingo Molnar
2002-08-20 13:44 ` Thunder from the hill
2002-08-19 22:41 ` Ingo Molnar
2002-08-19 22:42 ` Richard Gooch
2002-08-19 22:46 ` Ingo Molnar
2002-08-19 22:51 ` H. Peter Anvin
2002-08-19 23:51 ` Alan Cox
2002-08-19 23:29 ` Alan Cox [this message]
2002-08-19 23:34 ` Ingo Molnar
2002-08-20 0:33 ` Andries Brouwer
2002-08-20 0:41 ` Alan Cox
2002-08-22 22:11 ` Andries Brouwer
2002-08-22 22:27 ` Alan Cox
2002-08-22 22:59 ` Jan Harkes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1029799751.21212.0.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rgooch@ras.ucalgary.ca \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®