From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: mpakovic@fdn.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Adam J. Richter" <adam@yggdrasil.com>
Subject: Re: 2.4.4 fork.c changes cause linuxconf to fail
Date: Sun, 29 Apr 2001 11:40:33 -0400 [thread overview]
Message-ID: <3AEC35F1.189C72F2@mandrakesoft.com> (raw)
In-Reply-To: <3AEC32D6.EC179FCB@fdn.com>
Michael Pakovic wrote:
> The changes to kernel/fork.c from 2.4.4-pre1 to 2.4.4-pre3 (and in
> 2.4.4) cause the RedHat 6.2 linuxconf utility to fail with the message
> "broken pipe". The linuxconf utility will run the first time, but all
> subsequent runs give the "broken pipe" error. The error message is
> generated as a result of a fflush command in linuxconf. I can provide
> more information upon request.
This patch is definitely breaking things, but AFAIK the fork.c change
only breaks buggy applications... Adam would you say that assertion is
correct?
Looking at the fork info in SuS v2[1], it doesn't seem to imply any
execution order...
http://www.opengroup.org/onlinepubs/007908799/xsh/fork.html
Jeff
--
Jeff Garzik | Game called on account of naked chick
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-04-29 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-29 15:27 2.4.4 fork.c changes cause linuxconf to fail Michael Pakovic
2001-04-29 15:40 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 8:00 Adam J. Richter
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=3AEC35F1.189C72F2@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpakovic@fdn.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