From: Dan Kegel <dank@kegel.com>
To: Dan Aloni <da-x@gmx.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: idea to enhance get_pid()
Date: Sat, 20 Apr 2002 10:50:20 -0700 [thread overview]
Message-ID: <3CC1AA5C.1DE5C69D@kegel.com> (raw)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Dan Aloni wrote:
> The last time I checked, the only thing that stops the move back to
> 32-bit pids is a bug in the bash shell, and just a few workable IPC
> interfaces and libc breakages.
I'd like to know more about that bash bug; do you have a URL for it?
(Is there even a bug tracking system for bash?)
I looked a bit on gnu.bash.bugs, and found two possibly related
patches; do these have anything to do with the bug?
http://groups.google.com/groups?selm=200104130734.AAA12931%40shade.twinsun.com
http://groups.google.com/groups?selm=200104130854.BAA18368%40shade.twinsun.com
Thanks,
Dan
next reply other threads:[~2002-04-20 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 17:50 Dan Kegel [this message]
2002-04-20 19:12 ` 32-bit process ids (was: Re: idea to enhance get_pid()) Dan Aloni
2002-04-20 20:00 ` Eric Brunner-Williams in Portland Maine
-- strict thread matches above, loose matches on Subject: below --
2002-04-20 9:15 idea to enhance get_pid() lenny lv
2002-04-20 9:59 ` Dan Aloni
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=3CC1AA5C.1DE5C69D@kegel.com \
--to=dank@kegel.com \
--cc=da-x@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/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